Everything posted by Lennyy
-
Crashing Upon ForceDuty
-
i need help with force duty
Upload your latest RagePluginHOok.log. It's a text document found in your main directory.
-
crashing was fine yesterday not changed any apart from game updated
- finally here!
- XML Parsing Error
-
Help with lspdfr
Hello kenzin, Down below you'll find some resources on how to install LSPDFR. For installing LSPDFR-Plugins, you will find instructions on the download page of each plugin. Make sure to read those thoroughly! https://www.lcpdfr.com/lspdfr/how-to-install/. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.
-
LSPD First Response has crashed error
Redownload the latest version here. That build should fix the log spam issue.
-
XML Parsing Error
Can you attach a screenshot of the error.
-
XML Parsing Error
Which car did you add right before this issue came up?
-
delete
I'm afraid not. You can try to install ClearTheWayV and see if that makes it any better.
-
what is the best thing to make lights brighter
Either your visual mod has it's own brighter lights option (I use VisualVanilla which comes with the option to brighten the lights). Or you install something like BetterRadiance.
-
LSPDFR Has Been Terminated
Navigate to .\lspdfr\lspdfr.ini and set "AmbientSpawn.DisableRandomUnits = true". Report back once you've tried that. Also, you have TrafficPolicer installed which is heavily outdated. You might want to try StopThePed instead.
-
irgendwas geht nicht
Das heißt, dass eine deiner Mods aus dem mods Ordner das Problem verursacht. Dagegen kannst du leider nichts machen außer die problematische Mod nicht zu installieren.
-
got a mod called Deadly weapons and now my lspdfr keeps crashing when i go
You're missing the PyroCommon.dll. Move that file from the DeadlyWeapons download archive to your main game directory. Move CalloutInterfaceAPI.dll from ./PluginsLSPDFR/ to your main directory. Update GrammarPolice Kuchera Callouts Super Callouts
-
got a mod called Deadly weapons and now my lspdfr keeps crashing when i go
Please upload your latest RagePluginHook.log. It's a text document found in your main game directory. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.
-
LSPD First Response has crashed error
The car you are trying to use is not compatible with PoliceMenu since it's missing a certain vehicle bone. Other than that you have no issues really. Did removing S136Callouts from your game help with the immense log size?
-
Open IV won't let me drag and drop vehicle mods
Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.
-
LSPD First Response has crashed error
Can you remove Section136callouts from your plugins folder and start the game again? It might generate a smaller log.
-
LSPDFR forever loading screen "Loading LSPDFR"
You’re welcome!
-
LSPDFR forever loading screen "Loading LSPDFR"
There’s nothing that can be lost since your are missing the outfits.xml entirely. Redownload the manual LSPDFR install, open the lspdfr\data folder and drag the outfits.xml into the same path within your GTA installation.
-
Switching to GTA Online
You’re welcome!
-
LSPDFR forever loading screen "Loading LSPDFR"
You download the LSPDFR archive again and drop the outfits.xml in .\lspdfr\data\
-
Switching to GTA Online
Rename your original modded copy of gta to something else than its current name. Create a second copy of the game and whichever version you want to run, you’ll rename accordingly.
-
LSPD First Response has crashed error
Interestingly your log file contains 117mb of data which is indeed too much for the site. Can you upload the contents of the file to pastebin.com and post the link to the file here? Alternatively, remove the Section136Callouts plugin from your directory and retry. See if that generates a smaller log that you can upload here.
-
Problem during installation "Not enough system resources..."
Make an exception for the entire GTA folder and put it there. After that create another exception just for the specific file.