LMS

Looking into it, thanks. Nothing you can do at this point to fix it.

Only because it's christmas...

You have to type "forceduty" into the console.

forceduty still works. MP is not changed.

You are still using an old version of ScriptHookDotNet.asi. Please use the one provided with LCPDFR 1.0.

Then your asi loader must be broken/wrong.

The root folder where you installed the game and where either GTAIV.exe or EFLC.exe resides.

The modifications you made probably interfere with the option to cycle through all cop components LCPDFR offers.

Any chance you have modded your cop peds?

AdvancedHook.log and LCPDFR.log please.

ScriptHookDotNet.log please and LCPDFR.log (if any).

AdvancedHook.log and LCPDFR.log please.

Use the manual installation.

Please post both, LCPDFR log and AdvancedHook.log You can also try mapping the "Arrest" action to another button in your .INI.

Hey guys, please find a reference for all API functions below. It's available as both, help file and browsable html site. The general API documentation can be found here: '?do=embed' frameborder='0' data-embedContent>> Online reference: http://lms-dev.com/lcpdfr-doc/ (In case it's down, thanks to ejerald for hosting one as well: http://haxx.me/lcpdfr/) Also check out my GitHub page which contains the latest API Example: https://github.com/LMSDev/LCPDFR-API Happy coding!

It also depends on where you live, fast internet is not available in every region.

ELS uses "TURN_OFF_VEHICLE_EXTRA" to toggle a single extra's visibility. But that's all you can do. Moving it around is not possible. That's also why the vehicle is repaired, because the extra is added to the car components and to re-render all components, it is reset.

No there is not, but that is the evidence for a PSU problem, since any other kind of problem probably would have been logged. Well, in fact, there is, I would try to avoid playing games for now. Otherwise you might end up having to buy a new GFX too...

Ah yes, I missed that due to the short timespan. Well, you could post the Applications event log, maybe that reveals something (the nvidia driver especially). But it's really weird Windows doesn't show any information. I suspect it's either the PSU or the GFX then. Edit: Yeah, that makes sense then. Try changing the PSU.

Well, it still says "Unexpected shutdown before", so to me it still looks like it's the log from after the restart.

What I mean is, you said the logs are from "the moment the PC was fired up till the problem occured, and then the events that occured once I powered up again to retrieve the logs." To me it looks like you only included the last part, but forgot to include the part from starting to the problem occuring.

I can only see events for like 1 minute after you started your PC. Is that really all?

Hello gangrenn, accessing individual car components/parts is not possible on native level (scripting, that is). You are trying something rather advanced which the natives don't support, because R* doesn't need to adjust the models in their scripts. It might, or should, be possible via memory hacking, but that will require a lot of RE in order to achieve that. If you happen to know x86 assembler, you can try starting your research at the COMPONENT natives, since they access model parts too. Maybe you find the right things to modify the car components directly from this. If you don't, without sounding rude, better drop the idea, too hard to do then. When you are making progress on your own, but are stuck at some points, feel free to PM me for assistance, I might be able to help. LMS

If it was a hardware issue, windows would probably know about it. The log you gave is too short to tell anything, please include all sections (Applications, System, etc.) for about 30 minutes before the shutdown too.

Does eventvwr.exe show anything under System events?