Charlie686

No problem, take care!

I believe it would be Dynamic LSPDFR.

Interesting! Please attach your RagePluginHook log, a text document found in your main directory. Thank you.

Hey there, 1. Not related to LSPDFR - maybe download a realistic blood / gore mod. 2. That's not how you use the plugin. Please read the README file which explains how to use it.

Glad to hear, enjoy!

Load GTAV first then RPH.

Hey there, Please upload your RagePluginHook log - this is a text document found in your main directory. Thank you! 🙂

Hey there, To my memory, this is from ForceACallout. Please check your ForceACallout ini configuration file & hopefully you are able to disable it! Alternatively, I would recommend Callout Interface which can offer similar functionality, as it is updated for recent LSPDFR versions. Hope this helps! 😄

Hey there, Here are a couple of things: You have installed SpeedRadar but it requires ScriptHookVDotNet. Are you sure it should be installed into GTAV/Plugins/LSPDFR? Most ScriptHookVDotNet-dependent scripts go into your GTAV/scripts folder. There is no LSPDFR crash in your log & nothing to suggest a plugin is causing it. Please disable your mods folder to _mods & retry. This will disable your mods folder temporarily; it is a diagnostic step, not a solution. If you are still experiencing issues, please upload your RagePluginHook log - a text document found in your main directory, not your logs folder. Hope this helps. 🙂

Hey there, Please load GTAV without RPH. Are you able to enter story mode?

Hey there, Please attach a screenshot of your main directory. Thank you

Could you please clarify which keybind you are referring to, and in what situation you are trying to use it?

This issue has nothing to do with 686 Callouts. Though, thank you @Scythexx for using it! The plugin causing this crash is PoliceBackup, as shown in the stack trace below. [3/9/2023 7:37:48 PM.970] at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase) [3/9/2023 7:37:48 PM.970] at PoliceBackup.Main.Functions_OnOnDutyStateChanged(Boolean onDuty) [3/9/2023 7:37:48 PM.970] at LSPD_First_Response.Mod.API.Functions.OnDutyStateChangedEventHandler.Invoke(Boolean onDuty) While I am unsure what plugin this is, though it is located in GTAV/Plugins/LSPDFR, it is finding a keybind which doesn't exist. You may've set Keys.NumPad0 instead of NumPad0. All keybinds must follow the format here. I hope this provides some clarity.

Hey there, Please ensure that within your GTAV Graphic Settings, PostFX & Shader Quality are set to high or above. Hope this helps! 🙂

They said "the game didn't crash" so probably not! 😄 dinput8.dll is your ASI Loader, and is responsible for loading your .asi files. This means an issue lies with one of your .asi scripts. To test this, re-enable dinput8.dll by renaming it back, & removing your .asi files. Then re-add them individually and test your game again to determine which is causing the issue. I would start with ScriptHookVDotNet related files, as ScriptHookVDotNet has known conflicts with RAGEPluginHook. 🙂

Hey there, Please install the vehicles into GTAV/mods/update/x64/dlcpacks/patchday28g9ecng/dlc.rpf/x64/levels/gta5/vehicles.rpf/ and retry. Thanks!

Please try installing a custom gameconfig & trying again.

Update Lore Callouts.

Glad to hear, enjoy!

Hey there, In your log you are experiencing a crash interrupting LSPDFR (and LSPDFR plugins) from loading. You are missing DamageTrackerLib which is required for Deadly Weapons, and found within the download. Hope this helps! 🙂

Glad the bot got you up & running! 😄

Please rename your mods folder to _mods & try again.

Sweet! OpenIV.asi is responsible for loading your mods folder. This means the issue is in your mods folder. If you wish to test that, you can re-add OpenIV.asi and rename your mods folder to _mods & retrying. What recent changes have you made in regards to it?

Hey there, Please attach an updated log. Your log folder contains old logs. Latest logs are found within your GTAV folder, and it should be called 'RagePluginHook.log' or similar. That way, I can take a look into your issue. 🙂 Note: your log does contain an exception from my callout pack. This does not cause any problems and will be amended in the next update.

Hey there, If the issue is only occurring with dinput8.dll, this means the issue resides with one of your .asi files. To diagnose this, please remove all your .asi files from your main directory (save them in a folder somewhere), and drag each one in individually, then load up your game. Using this, you can pinpoint which .asi script is specifically causing your problem. Once you've identified which one is causing you problems, let me know. 🙂