Alright I am fed up. I don't care what happens to me or my profile at this point this is fucking ridiculous. I know others in the same boat and they are as mad if not madder than I am with this. 

 

After installing the LSPDFR 0.4.1 update, even hitting the left DPAD button on my controller just straight up crashes my game, and hitting go on duty has some issue where it just freezes and closes the menus, but unfortunately because of this left DPAD issue I have no logs from that. 

I do use ELS, like any normal LSPDFR player should, like this fact matters. 

 

ANYWAYS

The issue I am having is this: whether I am in the car, walking to my car, walking to the station it does not fucking matter, hitting the left DPAD button on xbox controllers AT LEAST 3 times (80% of the time though it's once, I did some experimenting) just crashes lspdfr, and my log found down below doesn't say fuckall except for something I can't translate. I've dug through ALL of my plugins and lspdfr specific keybindings and NOTHING uses the left dpad to open or close anything because of the simple fact I use ELS, and even outside of the vehicle like I said NOTHING uses the left DPAD button for any menu or animation or whatever. It just crashes. 

 

As for the going on duty thing, the list of plugins I use are below in no specific order.

LSPDFR+ and Traffic Policer (since STP and UB came out I avoid anything from Albo not required by these two mods like the fucking plague)

Stop the Ped (STP)

Ultimate Backup (UB)

United Callouts

Common Callouts

Callout Manager

Computer+

It crashes usually 2-5 seconds after hitting "go on duty" and all plguins have already loaded, and previously it tried to blame PoliceSmartRadio as the culprit, unfortunately that's as far as I got with this stupid left DPAD issue. I have seen others reporting this issue and I will report it again until it is fixed. 

 

EDIT: Add this to the list of bugs

LSPDFR isn't saving keybindings as I did find a loophole to the on duty crash, and despite not having "DPADLeft" to open police computer, the police computer opens anyways. You can see why this is an issue. 

 

And now for my rant, buckle up you easily offended reader...

Granted I've only been doing LSPDFR for going on a year n a half, but I know how buggy stuff can be and I've witnessed other buggy launches both LSPDFR related and otherwise, and with this ever growing list of bugs fixed or not, LSPDFR 0.4 and LSPDFR 0.4.1 is now the most buggiest mod, program, whatever I have ever used, and I'm only a few seconds away from calling it pure wasteful bloatware. And given how the "community" if it can even be called that anymore is really turning out, what with modders leaving and rogue moderators, I just gotta ask - what the fuck happened here? This is making Fallout 76 and its corresponding subreddit look like a palace. At least in LSPDFR 0.3 there was still a toxic community but LSPDFR itself worked, save for a few plugin incompatibilities but at least those were fixable and had work arounds. This... this is a fucking dumpster fire. And with that I post this thread with my log as promised.

 

RagePluginHook.log

Edited March 17, 20197 yr by SamuelOlson1701

2 hours ago, SamuelOlson1701 said:

Alright I am fed up. I don't care what happens to me or my profile at this point this is fucking ridiculous. I know others in the same boat and they are as mad if not madder than I am with this. 

 

After installing the LSPDFR 0.4.1 update, even hitting the left DPAD button on my controller just straight up crashes my game, and hitting go on duty has some issue where it just freezes and closes the menus, but unfortunately because of this left DPAD issue I have no logs from that. 

I do use ELS, like any normal LSPDFR player should, like this fact matters. 

 

ANYWAYS

The issue I am having is this: whether I am in the car, walking to my car, walking to the station it does not fucking matter, hitting the left DPAD button on xbox controllers AT LEAST 3 times (80% of the time though it's once, I did some experimenting) just crashes lspdfr, and my log found down below doesn't say fuckall except for something I can't translate. I've dug through ALL of my plugins and lspdfr specific keybindings and NOTHING uses the left dpad to open or close anything because of the simple fact I use ELS, and even outside of the vehicle like I said NOTHING uses the left DPAD button for any menu or animation or whatever. It just crashes. 

 

As for the going on duty thing, the list of plugins I use are below in no specific order.

LSPDFR+ and Traffic Policer (since STP and UB came out I avoid anything from Albo not required by these two mods like the fucking plague)

Stop the Ped (STP)

Ultimate Backup (UB)

United Callouts

Common Callouts

Callout Manager

Computer+

It crashes usually 2-5 seconds after hitting "go on duty" and all plguins have already loaded, and previously it tried to blame PoliceSmartRadio as the culprit, unfortunately that's as far as I got with this stupid left DPAD issue. I have seen others reporting this issue and I will report it again until it is fixed. 

 

EDIT: Add this to the list of bugs

LSPDFR isn't saving keybindings as I did find a loophole to the on duty crash, and despite not having "DPADLeft" to open police computer, the police computer opens anyways. You can see why this is an issue. 

 

And now for my rant, buckle up you easily offended reader...

Granted I've only been doing LSPDFR for going on a year n a half, but I know how buggy stuff can be and I've witnessed other buggy launches both LSPDFR related and otherwise, and with this ever growing list of bugs fixed or not, LSPDFR 0.4 and LSPDFR 0.4.1 is now the most buggiest mod, program, whatever I have ever used, and I'm only a few seconds away from calling it pure wasteful bloatware. And given how the "community" if it can even be called that anymore is really turning out, what with modders leaving and rogue moderators, I just gotta ask - what the fuck happened here? This is making Fallout 76 and its corresponding subreddit look like a palace. At least in LSPDFR 0.3 there was still a toxic community but LSPDFR itself worked, save for a few plugin incompatibilities but at least those were fixable and had work arounds. This... this is a fucking dumpster fire. And with that I post this thread with my log as promised.

 

RagePluginHook.log 53.56 kB · 1 download

I know i gave up my lspdfr wants to do nothing but stutter and loose frames. I even play with a vanilla folder and still same thing. unfortunately i just have to check out. 0.3 and 0.4 there is a difference 0.4 is just broken.    

36 minutes ago, tony said:

I know i gave up my lspdfr wants to do nothing but stutter and loose frames. I even play with a vanilla folder and still same thing. unfortunately i just have to check out. 0.3 and 0.4 there is a difference 0.4 is just broken.    

I'm gonna do some digging in my download archives for GTA V and if i find 0.3 im goin back in a heartbeat, fuck lspdfr 0.4 at this point its just unplayable.

4 minutes ago, SamuelOlson1701 said:

I'm gonna do some digging in my download archives for GTA V and if i find 0.3 im goin back in a heartbeat, fuck lspdfr 0.4 at this point its just unplayable.

I hear you man its a shame. i still dont understand how others have no issues and people like us have these issues.

 

Um Your using RageShowMyLocation. Using 2 year old outdated mods is exactly the reason your having problems and will continue to have them. I didn't bother to check the rest but im sure your just plopped in there whatever you wanted. Even if its updated and you download it, there could be an issue. LSPDFR works fine.

 

Fact of the matter is no matter how much your helped, your obviously going to do what you want, download what you want, and if it don't work then it is LSPDFR's fault. Fact is lspdfr works fine until you try to add other creators content in, and they have not had very long to fix for 0.4.

 

Heres the solution, don't be a dumbass.

5 hours ago, SamuelOlson1701 said:

Alright I am fed up. I don't care what happens to me or my profile at this point this is fucking ridiculous. I know others in the same boat and they are as mad if not madder than I am with this. 

 

After installing the LSPDFR 0.4.1 update, even hitting the left DPAD button on my controller just straight up crashes my game, and hitting go on duty has some issue where it just freezes and closes the menus, but unfortunately because of this left DPAD issue I have no logs from that. 

I do use ELS, like any normal LSPDFR player should, like this fact matters. 

 

ANYWAYS

The issue I am having is this: whether I am in the car, walking to my car, walking to the station it does not fucking matter, hitting the left DPAD button on xbox controllers AT LEAST 3 times (80% of the time though it's once, I did some experimenting) just crashes lspdfr, and my log found down below doesn't say fuckall except for something I can't translate. I've dug through ALL of my plugins and lspdfr specific keybindings and NOTHING uses the left dpad to open or close anything because of the simple fact I use ELS, and even outside of the vehicle like I said NOTHING uses the left DPAD button for any menu or animation or whatever. It just crashes. 

 

As for the going on duty thing, the list of plugins I use are below in no specific order.

LSPDFR+ and Traffic Policer (since STP and UB came out I avoid anything from Albo not required by these two mods like the fucking plague)

Stop the Ped (STP)

Ultimate Backup (UB)

United Callouts

Common Callouts

Callout Manager

Computer+

It crashes usually 2-5 seconds after hitting "go on duty" and all plguins have already loaded, and previously it tried to blame PoliceSmartRadio as the culprit, unfortunately that's as far as I got with this stupid left DPAD issue. I have seen others reporting this issue and I will report it again until it is fixed. 

 

EDIT: Add this to the list of bugs

LSPDFR isn't saving keybindings as I did find a loophole to the on duty crash, and despite not having "DPADLeft" to open police computer, the police computer opens anyways. You can see why this is an issue. 

 

And now for my rant, buckle up you easily offended reader...

Granted I've only been doing LSPDFR for going on a year n a half, but I know how buggy stuff can be and I've witnessed other buggy launches both LSPDFR related and otherwise, and with this ever growing list of bugs fixed or not, LSPDFR 0.4 and LSPDFR 0.4.1 is now the most buggiest mod, program, whatever I have ever used, and I'm only a few seconds away from calling it pure wasteful bloatware. And given how the "community" if it can even be called that anymore is really turning out, what with modders leaving and rogue moderators, I just gotta ask - what the fuck happened here? This is making Fallout 76 and its corresponding subreddit look like a palace. At least in LSPDFR 0.3 there was still a toxic community but LSPDFR itself worked, save for a few plugin incompatibilities but at least those were fixable and had work arounds. This... this is a fucking dumpster fire. And with that I post this thread with my log as promised.

 

RagePluginHook.log 53.56 kB · 1 download

 

15 hours ago, tony said:

I hear you man its a shame. i still dont understand how others have no issues and people like us have these issues.

 

 

Generally the issue boils down to user error during installation, or a bad mixture of other mods with LSPDFR.

 

The trick is, other people may also have these issues, but through some simple troubleshooting (Starting with re-installing LSPDFR, making sure that works, and then adding other mods one at a time), they can usually find what particular mod is causing the issue, and correct it through it's removal.

 

Even the OP admitted to having a litany of extra modifications, yet without noting any testing, is blaming only LSPDFR when the culprit is likely the combination with another mod. The fact that they load is irrelevant to them being the cause.

 

 

Edited March 17, 20197 yr by zach016

As for DPadLeft crashing LSPDFR with the new version, that is an oversight on our end. You need to be on duty for it not to crash. You could also rebind the Secondary Context key to a different key (as that is what is being used here) if you want to access ELS even off duty.

Once agian i play with a vanilla folder and still continue to get frame drops and stuttering. 

If it ain’t Broke don’t fix it lol. I wish they could find away to revert back to 0.3. Or update it to have two files to choose from. Either you want 0.4 and all it’s bugs included or do you want a stable and better game play with 0.3 I bet they can make it happen. 

Question guys I am currently using 0.4 at the moment which is working fine, I use a controller which again is working fine with the plugins I have installed. Can still carry on using 0.4 or do I have to up date to 0.41

I gave 0.4.1 a try and granite it fixed a few things, i'm still having loss of frames. I've loaded just LSPDFR by itself and noticed a loss of textures still. I don't have the best rig in the community but I can assure that when I run 0.3 i'm not having near the loss of frames that i'm having with 0.4.1. I agree with the "if it aint broke don't fix it. I get that the crew is trying to make LSPDFR more epic in terms of game play and I appreciate the efforts and hard work that I'm sure they're doing, but I really believe that 0.4 is still a work in progress typically with the texture and frame issues. It took a toll on my computer for just LSPDFR plugin itself to run. I'm not so sure what kind of coding they're using. I do like the improvements game play wise, so if they could focus on what makes the computers drop frames like a boeing 737 max 8. That would be great. Until then I'm back at 0.3 and I'm having fun just playing that until they clear out the bugs. If memory serves me correct, LCPDFR was the exact same way when they updated it. It's just going to take some more time and testing before it becomes fully compatible for everyone's computer.

On 3/16/2019 at 8:29 PM, SamuelOlson1701 said:

Alright I am fed up. I don't care what happens to me or my profile at this point this is fucking ridiculous. I know others in the same boat and they are as mad if not madder than I am with this. 

 

After installing the LSPDFR 0.4.1 update, even hitting the left DPAD button on my controller just straight up crashes my game, and hitting go on duty has some issue where it just freezes and closes the menus, but unfortunately because of this left DPAD issue I have no logs from that. 

I do use ELS, like any normal LSPDFR player should, like this fact matters. 

 

ANYWAYS

The issue I am having is this: whether I am in the car, walking to my car, walking to the station it does not fucking matter, hitting the left DPAD button on xbox controllers AT LEAST 3 times (80% of the time though it's once, I did some experimenting) just crashes lspdfr, and my log found down below doesn't say fuckall except for something I can't translate. I've dug through ALL of my plugins and lspdfr specific keybindings and NOTHING uses the left dpad to open or close anything because of the simple fact I use ELS, and even outside of the vehicle like I said NOTHING uses the left DPAD button for any menu or animation or whatever. It just crashes. 

 

As for the going on duty thing, the list of plugins I use are below in no specific order.

LSPDFR+ and Traffic Policer (since STP and UB came out I avoid anything from Albo not required by these two mods like the fucking plague)

Stop the Ped (STP)

Ultimate Backup (UB)

United Callouts

Common Callouts

Callout Manager

Computer+

It crashes usually 2-5 seconds after hitting "go on duty" and all plguins have already loaded, and previously it tried to blame PoliceSmartRadio as the culprit, unfortunately that's as far as I got with this stupid left DPAD issue. I have seen others reporting this issue and I will report it again until it is fixed. 

 

EDIT: Add this to the list of bugs

LSPDFR isn't saving keybindings as I did find a loophole to the on duty crash, and despite not having "DPADLeft" to open police computer, the police computer opens anyways. You can see why this is an issue. 

 

And now for my rant, buckle up you easily offended reader...

Granted I've only been doing LSPDFR for going on a year n a half, but I know how buggy stuff can be and I've witnessed other buggy launches both LSPDFR related and otherwise, and with this ever growing list of bugs fixed or not, LSPDFR 0.4 and LSPDFR 0.4.1 is now the most buggiest mod, program, whatever I have ever used, and I'm only a few seconds away from calling it pure wasteful bloatware. And given how the "community" if it can even be called that anymore is really turning out, what with modders leaving and rogue moderators, I just gotta ask - what the fuck happened here? This is making Fallout 76 and its corresponding subreddit look like a palace. At least in LSPDFR 0.3 there was still a toxic community but LSPDFR itself worked, save for a few plugin incompatibilities but at least those were fixable and had work arounds. This... this is a fucking dumpster fire. And with that I post this thread with my log as promised.

 

RagePluginHook.log 53.56 kB · 6 downloads

Damn, bro. That’s harsh. Though not much of a commenter, I’ve been around since lcpdfr and let me tell you, you don’t know unstable until you e played that. Revert to .4, only play with callouts and major plugins (arrest manager, stop that ped, ultimate backup, police smart radio, etc.) that specifically say they use .4’s api. I play with els, entity persistence, eup, all the approved plugins and a racing wheel. If I can make that work, you’ll be all good.