Everything posted by GTAbear
-
LSPDFR Keeps Crashing
But then its one of those NEW mods! Disable them and you should be fine Your log show nothing. < 8KB is to little You do crash when bodyCam is loaded -Is that one of those you installed today?
-
Crashing at random times while playing
That is a typical pattern for one or more plugins that need updating AssortedCallouts, AutomaticSirenCutout, CalloutManager, Corpse, CrazyCallouts, FBI, Interaction, maniacCallouts, NoMoreMelee, Immersive, SuperCallouts, Traffic Callouts, UnitedCallouts Are not up to date try and disable them
-
Callout manager and heli assist crash
AutomaticSirenCutout, CalloutManager, HeliAssistance, OfficerporciPlugin, UnitedCallouts Are not updated. Disable all
-
Plugin randomly crashing occasionally
Do you really need that many plugins? Very often that many plugins will lead to control conflicts These are not updated CountyCalls, FBIInteraction, RichsPoliceEnhancements, Section136Callouts, SimpleCallouts, SpeedyPursuit, SwatResponseCallouts, UnitedCallouts, UnsafeCallouts, WoutersCalloutsV And should be disabled
-
LSPDFR
If qaws easy fix just reinstalling lspdfr-audio did not work, then you need to go through the process i linked to, from the FAQ, and that is sadly complicated
-
LSPDFR crash on duty
AutomaticSirenCutout, BasicCallouts, BasicParkingTickets, Corpse, Emergency, FBI, Interaction, MoreRadioChatter, OfficerporciPlugin, Pragmatic, SwatResponseCallouts, TrafficCallouts, UnitedCallouts, XScanner reported as in need of updating. Try and disable it. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod also You have way to many plugins, conflicts are almost bound to happen
-
LSPDFR Crashing everytime
You have ultimateBackup, but do you have it is needed
-
LSPDFR Keeps crashing
afaik ok, and should not crash your game, though some has been writing that STP is a problem, for most its not, but you have so few plugins that you should just use The general method for troubleshooting and disable all mods, and then add them in sequence each with a new test-run Do you have any car-packs? Sometimes they are also crash-prone.. Just remembered that there is a config-file You need that afaik
-
LSPDFR.dll crash keeps happening every 5-10 minutes
betterPresence reported as in need of updating. Try and disable it. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod
-
Loading lspdfr taking forever
You never do that as a user, only as a dev if the plugin under dev. has crashed To open LSPDFR for gaming follow this https://www.lcpdfr.com/forums/topic/125624-rph-does-not-open-game/
-
GTA 5 on duty crashes.
You either removed -or it was never logged, the plugin-list Its ok to remove your pc-path/ user-name, but do not remove any lines of the actual log
-
LSPDFR
If that work, it would be amazing ! Do you happen to know what them reason is for the audio-folder being corrupted -If it is indeed corrupted(?)
-
LSPDFR
I am sorry but you have the most annoying issue known -at all SlimDX-fail It is very complicated to solve.. You do absolutely need a 100% updated windows installation! Your .NET may need to be reinstalled And and and.. There is a FAQ article https://docs.google.com/document/d/1Hp2Qco0qsgKfohkhjYWUxTr2OF7NSCkp8uSZwWz6rRQ/edit#heading=h.ga53kl28476 No info why some gets this fail, my guess is that it is fail in win-update, and in that context i wonder: Do you happen to have a LABTOP-computer?, because if so.. i think i know ...
-
lspdfr crashes mid game
At least AmbienTAiCallouts AutomaticSirenCutout CalloutsT CountyCalls FBI Callouts Fire Callouts HypersCallouts PeterUCallouts RegularCallouts Section136Callouts SimpleCallouts UnitedCallouts ..Or iow A LOT reported as in need of updating. Try and disable all. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod
-
Weird whosh sounds after accepting calls
Has to be 'some' mod -It really have to be the latest installed mod that introduced that artefact. Disable plugins/ installed mods from newest installed one by one, and test game in between each disabling..
-
Lspdfr crashing when I go on duty
But that only 11 KB.. You have no info in log. Do you have a Mods-folder? Rename it Mods_ and retry
-
LSPDFR crashed after selecting a character
You have a flawed file in your installation. A weapon cant be loaded Exception message: Cannot load an invalid weapon asset. Have you installed a new weapon?
-
LSPDFR Crashe when loading on duty or forcing on duty
T.y. I will remove it from the update-list
-
Game crashes couple seconds after duty
There are 'something' odd with one of these Plugins\EUPMenu.dll Plugins\RepairAndWash.dll Plugins\StickyWheels.dll Try and disable them one by one and run the game in between. There is also that car-pack Does that need heap-adjuster?? That should be in the documentation for the pack If it does need heap-adjuster, you need to find that and install. The actual LSPDFR plugins does not report broken, but several has written about issues with STP, so for the 'full picture', you may need to try disabling of STP too..
-
LSPDFR Keeps crashing
You need to find the 'leftovers' from your failed update, and remove it. That can be a drag The success way is to uninstall LSPDFR completely, disable mods, and then reinstall what you had before you made that botched install, but if you had a lot installed, then that would be really annoying.. Instead try and make a file-search between dates, and then move those files out in Recycle-bin Do not delete them, just move them -and most important do not touch anything in your default GTAV install! If you succeed making it run, then you can delete the files you moved, otherwise use the Recreation-feature in Recycle-bin one by one until you have success. That type of file-juggling is way easier if you use an empty Recycle-bin
-
LSPDFR Crashe when loading on duty or forcing on duty
SuperCallouts UnitedCallouts reported as in need of updating. Try and disable it. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod
-
LSPDFR Keeps crashing upon launch, already at 60000
You got an asset issue It looks like the flashlight is being forced in inventory, and that it is causing an issue If i am correct the best option would be to redownload LSPDFR, remove all you have installed and then install the new pack. That should give you a new asset including a flashlight
-
Crashing
At least AutomaticSirenCutout HeliCallouts Narcos ProtectionSquad SimpleCallouts SuperCallouts SwatResponseCallouts Traffic Policer TypicalCallouts; ...Or iow MOST of your callouts.. is reported as in need of updating. Try and disable all. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod
-
Crash
AmbientAICallouts BetterPresence Narcos RegularCallouts SuperCallouts; -Are all in need of update. Disable them all. If you have issues with calloutInterfase uninstall, get a new pack, and then reinstall
-
siren keep ringing
My guess is that you got a conflict in key-binding. Default you can turn off siren-sound with key-J. Does that work? 'J' will not turn alert-state off. Default will key-E toggle that state. But you also have siren-sound after you leave the car, thats why i believe you got a binding-conflict. The general method for troubleshooting is to disable all mods, and then add them in sequence each with a new test-run But if you know when the fail was introduced and also know you added a MOD just before, then testrun without that newly added mod