After using the Diagnostics tool to find out why my LCPDFR wasn't working, the tool brought up two problems, and after looking through the forums and googling I failed to find a solution.

 

Under the System Dependencies module, it says "Failed to resolve MSVCP110.ddl from C:\Program Files (x86)\Steam\steamapps\common\Grand Theft Auto IV Episodes from Liberty City\EFLC\ADVANCEDHOOKINIT.ASI."

 

Under log checks it says to check the reports.

 

I have no mods installed apart from LCPDFR, and this is a fresh install of LCPDFR I am using.

 

Attached are "LCPDFR.log", "ScriptHook.log", "ScriptHookDotNet.log", "Diagnostics_31.7.2017_10_12_21.log", and a screencap of my EFLC folder. Unfortunately there was no "AdvancedHook.log"

 

I am using the steam copy of EFLC if it helps.

 

 

Please get back so, Rcwarfare

LCPDFR.log

ScriptHook.log

ScriptHookDotNet.log

Diagnostics_31.7.2017_10_12_21.log

Wasn't there an Update on GTA4 a while ago that broke all mods?

1 minute ago, A Stranger said:

Wasn't there an Update on GTA4 a while ago that broke all mods?

I presume that he's on 1.0.7.0.

28 minutes ago, rcwarfare said:

-snip-

Install the Visual Studio Redistributables, 2010 (x64 and x86)

Your thread has been moved to LCPDFR Support Requests as it isn't a LSPDFR Support Request. 

5 hours ago, Starmix said:

I presume that he's on 1.0.7.0.

I did follow the downgrade guide, yes.

5 hours ago, Starmix said:

Install the Visual Studio Redistributables, 2010 (x64 and x86)

I just did, and the problem persists.

Here is the diagnostics log. The other logs have not changed.

Diagnostics_31.7.2017_16_54_2.log

Ah, sorry, you need to install both of the 2012 ones.

Alright. I installed the 2012(x64) and (x86), and that has resolved my problems with the System Dependencies module, however, I am still having problems with the Log Check module.

The Diagnostics tool says "Log files checked, see report for more details."

Nothing else has changed, but here is the newest diagnostics report.

Diagnostics_31.7.2017_17_18_0.log

That's just general, and isn't indicative of a problem.

If it works fine now, you can disregard it.

It appears to be working. Thanks for the help.