Just recently installed LSPDFR. Everytime I try loading LSPDFR through the F4 menu it crashes my game. I have NVE on if that means anything. Here's the log file: 

RagePluginHook_26092023_233226.log

4 hours ago, ovy said:

Just recently installed LSPDFR. Everytime I try loading LSPDFR through the F4 menu it crashes my game. I have NVE on if that means anything. Here's the log file: 

RagePluginHook_26092023_233226.log 10.96 kB · 3 downloads

Go to \Grand Theft Auto V\lspdfr\lspdfr.ini 

Set this to true Main.DisableGameBlipHiding = true

 

Next, in the main gta directory open ragepluginhook.ini

Set the threshold from 10,000 to 60,000

PluginTimeoutThreshold=60000

 

Lastly make sure ragenativeui is up to date, download the latest here

https://github.com/alexguirre/RAGENativeUI/releases

5 hours ago, Pavy said:

Go to \Grand Theft Auto V\lspdfr\lspdfr.ini 

Set this to true Main.DisableGameBlipHiding = true

 

Next, in the main gta directory open ragepluginhook.ini

Set the threshold from 10,000 to 60,000

PluginTimeoutThreshold=60000

 

Lastly make sure ragenativeui is up to date, download the latest here

https://github.com/alexguirre/RAGENativeUI/releases

 

I can't see how any of this (see quote above) is related to the log they attached and the behavior they described.

1. There's no error about AmbientGameBlipHiding in the log.
2. The plugin was not terminated because it caused the game to freeze (low timeout threshold).
3. Rage.Native.NativeFunction is not the same as RAGENativeUI.
   Rage.Native.NativeFunction is something a RPH plugin calls when trying to access native features/functions of the RAGE game engine (Rockstar's Advanced Game Engine). In simple terms, I guess you could also say RPH is trying to access the base game files (like .rpf packages).
   If there are errors about it in the log, it's usually caused by someone's mods folder.

 

10 hours ago, ovy said:

Just recently installed LSPDFR. Everytime I try loading LSPDFR through the F4 menu it crashes my game. I have NVE on if that means anything. Here's the log file: 

RagePluginHook_26092023_233226.log 10.96 kB · 3 downloads

The log you attached is an archived, older log. It doesn't show what happened in your most recent game session. The "RagePluginHook.log" file in your main GTA V folder is the one you should attach (without a date at the end of the file name).

But assuming the log shows a recent previous attempt to load LSPDFR that failed for the same reason as the latest attempt, try the following:
Rename the mods folder to "_mods", then try launching the game again. If your game works without crashes after you renamed it, it would mean that something in your mods folder caused the crash earlier. Possibly the NVE installation.

 

Edited September 27, 20232 yr by Hendrik3812

On 9/27/2023 at 5:37 AM, Hendrik3812 said:

 

I can't see how any of this (see quote above) is related to the log they attached and the behavior they described.

1. There's no error about AmbientGameBlipHiding in the log.
2. The plugin was not terminated because it caused the game to freeze (low timeout threshold).
3. And Rage.Native.NativeFunction is not the same as RAGENativeUI.
   Rage.Native.NativeFunction is a RPH plugin trying to access native features/functions of the RAGE game engine (Rockstar's Advanced Game Engine). In simple terms, I guess you could also say RPH is trying to access the base game files (like .rpf packages).
   If there are errors about it in the log, it's usually caused by someone's mods folder.

 

The log you attached is an archived, older log. It doesn't show what happened in your most recent game session. The "RagePluginHook.log" file in your main GTA V folder is the one you should attach (without a date at the end of the file name).

But assuming the log shows a recent previous attempt to load LSPDFR that failed for the same reason as the latest attempt, try the following:
Rename the mods folder to "_mods", then try launching the game again. If your game works without crashes after you renamed it, it would mean that something in your mods folder caused the crash earlier. Possibly the NVE installation.

 

Lol....All I did was try and remember what the solution to the error code was, I couldn't remember which of the 3 so I just bundled them in a rush and had to go rather than leave the thread unanswered. It may be mods too but the things I mentioned first should be applied before the mods folder is looked at. Regardless, some people require that parameter to be changed in lspdfr to run the game and doesn't hurt to check if ragenativeui is up to date(since a lot of people have older versions in support). As well as the 60k timeout threshold, majority of people if not all should have that. Rather than going back and forth with the author troubleshooting at a late hour.

Edited November 5, 20232 yr by Pavy

2 minutes ago, Pavy said:

when you yourself apply the same fixes many times

Correct, I did. But under totally different circumstances.