LCPDFR Common Errors and Quick Fixes

[LukeD 1830]

Hello LCPDFR users, and welcome to my quick fixes and common errors guide on how to get your LCPDFR up and running. The guide will contain help on how to correctly use the diagnostics tool with version 1.0b as well as some of the more trivial errors which occur and how to fix them, so let’s get started. Below you will find a contents table of “Chapters” in this guide, each chapter can be found by it's title, the content of that chapter will be in a spoiler tag.

 

So without further adieu...

Common Errors and Quick Fixes for LCPDFR

 

 

Chapter 1 - How to use the Diagnostics Tool (1.0b +)

So, you have started using 1.0b but the game won’t seem to run LCPDFR at all? No problem, the genius mind of LMS has created the diagnostics tool to help solve the most major of problems with LCPDFR. Isn't he nice to us?

But how do you use it correctly? Well this chapter will show you in simple steps how to get the most out of it.

 

So, step 1 would be a good place to start, load up the diagnostics too. You then want to click the option “Check your installation”, from here the diagnostics tool will seek out your LCPDFR install and scan it for anything missing.

But I get error 0x1, no worries, if you click the “Advanced Mode” button in the bottom left corner, and then click check your installation, you will be prompted to browse for your GTA IV .exe file.

Find your GTAIV.exe and the diagnostics tool will scan that directory instead.

 

Error! Wonderful, the diagnostics tool has found a problem for you! But how do we know what the issue is? Well that depends on what is causing the problem, so let’s have a look at an example of a perfect directory shall we?

So what does each one mean if it happens to be red?

Well let’s have a look shall we,

ASI Loader determines if you are using dsound.dll or xlive.dll, if this has an error it is because you are missing dsound.dll OR xlive.dll. Or you might be using both by mistake, you only need one or the other so make sure it is in your GTAIV folder.

 

ScriptHookDotNet determines if this file is present and correct, you could be missing this file if it has a problem, but if it has half a red bar you are missing a thing called ‘DirectX’.

 

System Dependencies checks to make sure you have the microsoft redistributables, if this produces an error you are missing the Microsoft Redist 2010 or 2012

 

LCPD first Response checks the entire install of LCPDFR to make sure it is correct, if this produces an error you installed it wrong, check to make sure it isn’t in any incorrect folders like “LCPD First Response”, everything should be in your GTAIV directory.

 

Log Check will scan the various error logs to see if there are any problems, if it produces a problem, you will need to post that log file to the forum and see what is up (or check it against Chapter 2 of this guide)

 

You'll notice though that if any particular module causes an error, you will get a pop up window saying the check failed with “one or more issues have been detected in your setup.”

The great part is that you can use this to find solutions to your problems as well by simply clicking on the failed component, but for your benefit I will provide a list of download links and extras in Chapter 3 for some of these issues.

 

Chapter 2 - Common Errors and Quick Fixes

Welcome to chapter 2, here you can find a list of the common errors which occur with LCPDFR, some of these errors might even carry over to GTA IV support but I can’t promise that. Don’t worry though, if you still need help after this chapter I will still be floating around the support threads.

So what are the common errors? Well there are quite a few, but hopefully I will be able to get through most of them with a simple fix. I will pull all of these errors from the LCPDFR.log files I have received during my time providing forum help, but most of them are for 1.0 or higher.

 

Invalid call to an object that doesn't exist anymore!

This is a very simple error but easily the most common, it means that the script tried to call an object which no longer exists for some reason, usually because it despawned.

To fix this error quickly, open your LCPDFR.ini file, find the line “PreloadAllModels = False” and change the value to “True”.

 

If that line is missing from the .ini file, add it underneath [Main] (it will only be missing if you are using LCPDFR version 1.0 or 1.0a, the line was correctly added in 1.0b)

 

Could not load type ‘System.Runtime.CompilerServices.ExtentionAttribute’ from assembly ‘mscorlib, Version=4.0.0.0,

This is a nice little error, kind of. In fact the diagnostics tool will pick up on this if you follow it from Chapter 1. This error means that you are missing the .net framework version 4.5 which is quite a crucial part, I’ll link a download to it in chapter 3. Or you can easily google it and download it yourself.

This error is actually the the most common reason (since there are others as well) of the Error in script LCPDFR_Loader.Loader.

 

I have no Log Files!!!

You know what that means don’t you? No? Oh…

Well it means that none of your scripts actually initiated. That’s a technical term for, started. Yep, you read that correctly, if you run the game, and pressing Alt+P and nothing happens, and you have no log files in your GTA IV directory, the scripts never even got looked at.

To fix this, you need to make sure that all the script loaders (dsound.dll OR xlive.dll, ScriptHook.dll, ScriptHookDotNet.asi, AdvancedHook.dll and AdvancedHookInit.asi) are all inside your GTAIV folder. NOT inside another folder within this.

For example, grand theft auto iv > GTAIV > ScriptHook.dll

Not grand theft auto iv > GTAIV > LCPD First Response > ScriptHook.dll

 

Error Message - Error in Module DSOUND.dll

Usually followed by a path like this: Program Files (86x) > Rockstar Games > GTA IV > asilog.txt

The problem here is that dsound is trying to write it's log file but is being denied access to create it. What you need to do is one of these three things, and that will fix it.

1) Disable the need for UAC in your control panel (google it, I will not write a guide on how to do that)

2) Always run your GTAIV.exe and LaunchGTA.exe as an administrator

3) Set the GTA IV directory to not be in read-only mode.

 

Chapter 3 - Downloads and Extras

Welcome to chapter 3, the home of a large number of download links and other useful little snippets that will help you out.

Ok so if you recall in Chapter 1, the diagnostics tool will spill out errors depending on what is missing. Here you can find a download link for those dependencies, so let’s start the list.

 

Missing DirectX

DirectX usually comes with the latest windows patch but if you do happen to be missing it you can get it from here. http://support.microsoft.com/kb/179113

 

Missing .net Framework 4.5

One of the most important dependencies, why? Because LCPDFR runs on it.

You can get that here http://www.microsoft.com/en-gb/download/details.aspx?id=30653

 

Missing System Dependencies

These are the microsoft redistributables, bothe 2010 and 2012 are required.

You can get 2010 here http://www.microsoft.com/en-gb/download/details.aspx?id=5555

And 2012 here http://www.microsoft.com/en-gb/download/details.aspx?id=30679

When it prompts you to select a file, always make sure to use the x86 one, even when you’re running a 64-bit OS.

 

But what about the extras? Well don’t worry I haven’t forgotten. The extras, mostly, are just the different commandline commands you can execute on your GTA IV as well as a couple of little windows tips for diagnosing problems.

The main commands used are the following:

-novblank -norestrictions -percentvidmem 100 -novsync -frameLimit 0 -nomemrestrict

 

Put them into a “commandline.txt” file inside your GTA IV directory and it should run using those commands.

 

You can also run the game as an administrator by right clicking on the GTAIV.exe (and LaunchGTA.exe), going to “Properties” and then clicking the “Compatability” tab at the top. At the bottom of that new menu is a checkbox saying “Run this program as an administrator” click it and then click apply.

Yes you can also just right click and then click “Run as administrator” but this will only run it as an administrator once.

 

Chapter 4 - The Best Way to Get Support

Welcome to chapter 4, the best way to get support. Why have I included this chapter in my guide you might be asking? Well the truth is some people don’t really know how to get the best from support. Some people don’t really know how to ask for it either.

For example, saying “help my game broke please help me fix it” says nothing to people who give support about why your game is broken. And let’s be honest, we may be smart with computers, but we are not psychic.

So, here is my tips for how to get support in the best possible way.

 

Tip 1

Follow a format, many people know from the support guidelines that they need to give some information and most importantly their error logs but not a description of their problem or what mods they have. So lets get a format going.

 

Description of Crash/Problem:

What Version of LCPDFR:

What Version of GTA IV/EFLC:

What Extra Mods are Installed:

Attached Error Logs (lcpdfr.log, AdvancedHook.log)

 

Tip 2

Post a screenshot of your GTA IV directory along with your error logs, why? Because it allows us to see what you see. You might not have realised you have a formatting problem (some file is in the wrong folder for example).

 

Tip 3

Be patient. Screaming “you guys suck this gay message came up I’m p****d off” will get you absolutely nowhere. In fact people are less likely to want to help you if you shout at them. Stay calm, we will get to help you eventually.

 

Tip 4

You probably don’t have the EXACT same problem as someone else, so please make your own thread about it so we can deal with each problem individually. Replying to 4 threads is much easier for us to keep track of who is having what problem than it is if 4 people reply to one thread saying “same problem here help”. Though, if you are really sure you have the exact same error line, replying to a topic is allowed as long as you provide useful information (e.g. your advice worked for me).

 

Chapter 5 - Appendix, Credits and a Thank You

Chapter 5, the resting point of this guide.

If you bothered to read the entire guide, a huge thank you from me to you. I spent a lot of time writing this guide in order to aid people with their LCPDFR problems, I didn’t do it for any other reason. so thanks if you took the time as well to go through it, I hope it helped.

I owe a huge amount of thanks to the kind people on the forum as well, without you guys saying “thank you for the help” and so on I would not still be here providing my support.

 

I also owe a huge amount of thanks, and possibly the most thanks, to LMS. Why? Well why not? No seriously though LMS has coded an entire mod for us, and then gone one step further to make a diagnostics tool so we can fix our problems a lot faster. I also personally owe it to him for the extra information he’s given and insight into how the diagnostics tool works.

My remaining thanks goes to those who have dedicated their time on the forum to helping others, purely because that’s just an amazing thing to do.

 

So, to close off my guide, once again thanks for reading it. I truly hope it was of use to you and remains to be of use in the future.

 

Happy Policing.

Luke

 

 

My final Words

To begin with it is probably best to start with Chapter 1, skipping to chapters is possible if you're in a hurry to get it working again but you might miss out useful information from a previous chapter. Seriously it is worth the read if it helps you fix your game.

I highly recommend everyone reads chapter 4 at the very least. It will explain the best way to get support on the forum should this guide not work for you. If people could use this format it would be great as it means I and other forum members can quickly read through your problems and help you out.

 

Note: If you need support, create yourself a new thread rather than spam this with "help me please" messages, I will respond to a new thread more.

Thanks :)

 

Changelog

23/03/2014 - Updated to include the "Error in module dsound.dll" fix, chapter 2

Edited March 26, 2014 by LukeD

[ineseri 5113]

Nice work, looks nice from where I am sitting. I'm sure it'll be appreciated :)

Edited March 19, 2014 by ineseri

[LMS 1820]

Looks good indeed, I'll pin it as a replacement to our pretty much outdated stickies. Thank you!

[Iconography 1383]

This thread isn't meant for support.  Please follow this guide and make your own thread if you still have an issue not covered here.  Support posts were hidden.

Nothing to see here!

---

This topic has been closed by LCPDFR.com staff.
If you feel that this topic has been closed in error, please report this post.