LukeD

Right ok, let's go through this in as basic as we can just to be absolutely sure. Downloaded 2012 redist (86x, not the 64x we don't need that) Installed the 2012 redist. Ran the diagnostics tool again. Your diag tool report said 2012 was missing, not 2010 so I assume you have that already. But if you want to be doubly sure, Downloaded the 2010 (86x) Installed the 2010 redist. Ran the diag tool again.

Anything I can do to help I will :) Did you make sure you installed them? They should be .msi files which need installing? (stupid question I know but I've seen stupid things so I have to check) Run the diag tool again and see what it says now you have those installed.

Perfect, you're problem is you're missing the necessary microsoft redists. If you go back to my guide, in chapter 3 you will see a list of different "missing" dependencies, the third one I believe is for the files you need.

Hi, sorry for the delayed reply been doing some research. Could you upload a screenshot of your GTA IV directory for me please, and also check inside your LCPDFR folder that you have a a file with a silly long name (something like microsoftAPIPack.dll, I have no idea what it's called off the top of my head)

Go to this guide and read it, it will answer most of your problems '?do=embed' frameborder='0' data-embedContent>> As for the error message you get regarding dsound.dll, it's being denied access to write it's log file. You need to run the game as an administrator or turn off read-only mode for the GTA IV directory.

You're welcome, glad I could help :)

Right click it and run it as administrator.

Hi Rob, I suggest you go to this guide here '?do=embed' frameborder='0' data-embedContent>> It will help you through a lot of problems to get your game up and running. If after going through that guide, nothing works still, feel free to quote me with a reply and I will figure it out for you :)

Weird, I am utterly convinced it should be there lol. Just add that line underneath [Main], that is where it belongs.

xlive.dll is just like dsound.dll, they are both what we call an ASI Loader. This means if you have an ASI script or you use scripthookdotnet you can run most scripts on your GTA IV. The only difference between dsound and xlive is that xlive prevents Games For Windows Live from working, so it effectively disables multiplayer. If you want gameplay, use xlive. If you want multiplayer and are prepared not to run any other scripts, use dsound. Running more than LCPDFR in multiplayer will cause problems, multiplayer does not like scripts very much.

There should be if you're using 1.0b You need to add it underneath [Main] if it isn't there.

You're welcome, glad I could help :)

You need to set the Diagnostics tool to "Advanced mode" by clicking the check box in the bottom left corner. I cover all that in Chapter 1 of my guide here '?do=embed' frameborder='0' data-embedContent>>

Try setting "PreloadAllModels" to "True" in the LCPDFR.ini file.

"Cannot create file" means that it is trying to write the asilog.txt file to your GTA IV directory and being denied access. What you need to do is right click on your GTA IV directory and set it to not be in read-only mode (the same for sub-folders) That way the asi loader will be allowed to write it's log file.

There have been a few reports of issues with the RGSC logins and playing with GFWL. To be honest with you I would recommend using xlive.dll if that works, yes ok that means not being able to play LCPDFR online, but if you intend to use other mods at all playing online will cause you more problems than it's worth.

Any error logs you have post them please. Also, try running the game without the LAPD vehicle pack because vehicle models are quite often the cause for instant crashes.

You have two errors in your log which seems to be a bit odd. The first is an Ambient manager not setting an object correctly, so try using "PreloadAllModels = True" and see if that helps. The second error (the one causing the crash) is an array index out of bounds exception. And to be perfectly honest I'm not sure why that will be occurring as I cannot see the default LCPDFR code. Hopefully LMS might know what this is, but if not thanks for reporting it :)

The game saying out of memory when you close it is normal just ignore it. Have you ran the diagnostics tool to make sure that your installation is correct now that you have the directory out of read-only mode? Chances are your installation will be slightly incorrect (missing a dependency) which means LCPDFR will never run in game, but your game will work fine.

You run the automatic installer, and when it asks you to locate your GTA IV directory (when it defaults to EFLC) you simply browse to your GTA IV folder instead.

Hello, Go to this guide '?do=embed' frameborder='0' data-embedContent>> Read Chapter 4 thoroughly and then come back with the extra information you can give us. Just saying "it crashes when I do this help" tells us nothing and thus we can't really help, even though we want to help. I would also recommend reading the rest of the guide as it may be of some use to you.

Cigarettes are legal, correct. But in the UK I know they are trying everything to make it as illegal as possible due to the research they have done. There are more chemicals in a cigarette than the average human even know exist. So much so they have even linked it to increasing the risks of lung and throat cancer. You inhale smoke it is going to cause some serious issues, you wouldn't sit in a burning house every day so why inhale smoke from a cigarette or cannabis? That is why I disagree with legalising it. It all seems far too stupid to me, having never smoked anything in my life, I intend to keep it that way.

No you're still installing wrong. If you're using the automatic installer the filepath should be Program Files (86x) > Rockstar Games > Grand Theft Auto IV > Install here Or if you're using steam Program Files (86x) > steamapps > common > grand theft auto iv > GTAIV > Install here Your "scripts" folder should only contain one .dll file for LCPDFR.

Did you even go through the guide? Have you used the diagnostics tool because that pulls up the main problems why the mod doesn't run.

Glad you have fixed the issue, enjoy :)