LSPDFR Crash on launch

[grizzbear 7]

8 minutes ago, Boone4796 said:

and can you load up everything that you had in your old mods folder when you have it named _mods?

yep... just loaded into the game. Everything loaded, went on duty, got calls. I guess i'll have to create another thread to see if anyone else here knows about renaming the mods folder to _mods and having it work  

[ericpolowski 54]

my guy i'm trying to work with you lmao..  ………….  renaming it _mods disables the folder basically to check if your mods folder is the issue loading.   IT obviously is,   all your scripts and the lspdfr will obviously work without mods folder but the contents installed to the old mods folder wont be there,  that would be things such as vehicles, weapon, clothing, sound, graphic mods   not stand alone scripts.....    so we are back to square 1 -  recheck my initial reply to you regarding putting  the new update.rpf in the mods folder.   YOUR OLD  MODS FOLDER WILL NOT WORK ONCE A NEW UPDATE IS RELEASED    does this make sense?  

 

[grizzbear 7]

1 minute ago, Boone4796 said:

my guy i'm trying to work with you lmao..  ………….  renaming it _mods disables the folder basically to check if your mods folder is the issue loading.   IT obviously is,   all your scripts and the lspdfr will obviously work without mods folder but the contents installed to the old mods folder wont be there,  that would be things such as vehicles, weapon, clothing, sound, graphic mods   not stand alone scripts.....    so we are back to square 1 -  recheck my initial reply to you regarding putting  the new update.rpf in the mods folder.   YOUR OLD  MODS FOLDER WILL NOT WORK ONCE A NEW UPDATE IS RELEASED    does this make sense?  

 

Ok ok I get what you're saying now. Ill try that and get back to you.

4 minutes ago, Boone4796 said:

my guy i'm trying to work with you lmao..  ………….  renaming it _mods disables the folder basically to check if your mods folder is the issue loading.   IT obviously is,   all your scripts and the lspdfr will obviously work without mods folder but the contents installed to the old mods folder wont be there,  that would be things such as vehicles, weapon, clothing, sound, graphic mods   not stand alone scripts.....    so we are back to square 1 -  recheck my initial reply to you regarding putting  the new update.rpf in the mods folder.   YOUR OLD  MODS FOLDER WILL NOT WORK ONCE A NEW UPDATE IS RELEASED    does this make sense?  

 

Yep, I got what you're saying now. I'm just going to create a totally fresh mods folder and reinstall my gun sounds, sirens, and vehicles. Thanks for your help.

[ericpolowski 54]

good deal bud,  perhaps I should have referenced albos videos      I didn't think I had to       but now you know for next time!   all the best!

 

[grizzbear 7]

Just now, Boone4796 said:

good deal bud,  perhaps I should have referenced albos videos      I didn't think I had to       but now you know for next time!   all the best!

 

Thank you! You taught me quite a bit; I appreciate your patience  

[ericpolowski 54]

I'm truly happy to help, I may not have all the answers ( far from it)   but I was in your shoes too MANY times.  the key is trying a lot and failing often haha    but that's how you learn    and the people on this forum are truly awesome

[JBin818 157]

Umm, I tried all that and still have a problem with Rage not loading it.  Now when I just opened OpenIV it said there is an update for it so I DL and installed it, well did that automatically.  After the OIV update it confirmed that the file path is still good and then it says that I have an old version of update.rpf and would I like to transfer the new stuff to the mods folder (check pic).  I did.  Rage still won't load BUT GTAV.exe will load the game.  So that is a half way improvement.  Before Rage nor GTAV.exe would load, I would get that same exited unexpectedly message.  So there is something with Rage I think.  I unchecked all plugins in Rage, that didn't help.  I unchecked "forced window mode", that didn't work.  I had to have forced windowed mode checked before or Rage wouldn't load it right.  So I get that message when Rage tries to bring up the game screen.  Right when Rage tried to bring up the game it closes out.  If nothing else works then I'll just have to load LSPDFR and RAGE in my vanilla backup and see if it happens again.   If all else fails then I just have to load all my mods again.  The update before last, when we were waiting for scripthook to update I was able to revert and play.  Then I updated scripthook and it was fine.  With this update Rage and Scripthook had to be updated but this is the first time I get this error message.  Stinkin' Rockstar....quit updated so often. 

[ericpolowski 54]

You need to start over with a new mods folder. Delete your mod folder and start a new one then start adding your stuff back in

[JBin818 157]

On 1/6/2019 at 12:01 AM, Boone4796 said:

You need to start over with a new mods folder. Delete your mod folder and start a new one then start adding your stuff back in

Ok, I'll do that. 

[JBin818 157]

Well apparently my AntiVirus was blocking Rage all of a sudden.  Didn't do that before.  I tried the make the new mods folder like every you all explained and that wasn't it.  I even completely took out the mods folder and it still had the same error message (exited unexpectedly).  I tried to remove other stuff which screwed up the game all together so I just had to reinstall everything......AGAIN!  Ugh.  Well at least I have a vanilla back up of the game so I saved a couple hours from having to reinstall the whole game.  The game loaded fine with GTAV.exe but not through Rage.  So I turned off AVG and Rage loads the game.  The previous version of Rage I didn't have a problem but for some reason this last Rage update triggers AVG to block it.  Wish it would say that it was being blocked.  Could have saved me a lot of time.  Now I have to see how to Whitelist Rage so i don't have to disable AVG each time.   Just thought I would let you all know.