Saints Row 2 Juiced Patch

dunn.wayne396 said:
I am getting this error every time I play. It comes up after hours of play. It also has happened at this location often ( coming off the highway from the NW (suburbs) as you turn onto the road running the south side of the coliseum). I would turn right at the bottom and then go 2 or 3 roads and turn right to go up into the college district through the tunnel. I hope that helps to identify the area. As you see in the pic I crash into the wall there on the left turn to the bottom of the ramp. I am running Juiced with CGOTR and vehicle mod.
Click to expand...
what vehicle mod? and are you on Windows 11? to be more specific past 24H2?
 
Last edited:
Clippy95 said:
The game would've always exceeded memory either ways before or after the Juiced update, or even without Juiced it just never printed them out and you could always see them if the game opened a console also it's AddBindToggles to have the binds working
Click to expand...
Yeah, I'm aware of all that. What I'm saying is AddBindToggles does nothing. Even with juiced.ini otherwise stock. It still works for me on v7.6.0. I know other people aren't having this issue.
 
-SeaboundSaint- said:
Yeah, I'm aware of all that. What I'm saying is AddBindToggles does nothing. Even with juiced.ini otherwise stock. It still works for me on v7.6.0. I know other people aren't having this issue.
Click to expand...
Newer juiced should rewrite out the ini, as theres been alot of changes since 7.6.0. But just incase, delete your old ini entirely and throw in the new one from 8.1.0, and on the topic make sure you turn it to 1 and save it while the game is not running. Otherwise weird because it does work fine for me on 8.1.0 and nightly builds.
 
Caboose said:
Newer juiced should rewrite out the ini, as theres been alot of changes since 7.6.0. But just incase, delete your old ini entirely and throw in the new one from 8.1.0, and on the topic make sure you turn it to 1 and save it while the game is not running. Otherwise weird because it does work fine for me on 8.1.0 and nightly builds.
Click to expand...
I installed everything correctly. The .ini is v8.1.0. I tried the recent Nightly and got the same issue.

The only thing I can possibly think of is that my current lua project heavily relies on the player_button_just_pressed() function. Maybe that could be interfering? But then if that were the case, how come v7.6.0 still works?...

Edit: Just tried removing my project with v8.1.0 installed, but no change.
 
Last edited:
-SeaboundSaint- said:
I installed everything correctly. The .ini is v8.1.0. I tried the recent Nightly and got the same issue.

The only thing I can possibly think of is that my current lua project heavily relies on the player_button_just_pressed() function. Maybe that could be interfering? But then if that were the case, how come v7.6.0 still works?...

Edit: Just tried removing my project with v8.1.0 installed, but no change.
Click to expand...
My hunch is to try reinstalling Juiced Patch on a fresh exe (especially if you are using Steam version, which does xdelta stuff).
A farfetched guess is maybe disabling ASLR from Windows Defender if it's enabled?
 
reina3 said:
My hunch is to try reinstalling Juiced Patch on a fresh exe (especially if you are using Steam version, which does xdelta stuff).
A farfetched guess is maybe disabling ASLR from Windows Defender if it's enabled?
Click to expand...
I'm on GOG. I could try reinstalling as a last resort when I'm not busy. Other Juiced features are working in v8.1.0, just not AddBindToggles.
 
Hello. Is there any way to please disable the warnings when a crash is prevented? I've gotten both the one that says it's for something of the game itself and the one that says the culprit may be a modded install, but then I have been able to keep playing for A LONG time with zero issue (think 8 hours, lol).

Thing is, the warnings make my window go out of focus while the game is still running, so they're not only distracting but can mess gameplay if they come at the wrong time.

I have the habit of frequently saving on different slots anyway, so I'd rather disable them (no the crash logs, though).
 
Clippy95 said:
It was already possible but I've clamped it to 1.0 because people kept pressing it and having their screens flipped
Click to expand...
I see. Can you consider clamping it to a reasonably low value like 0.25 which still avoids that problem?
 
You must log in or register to reply here.
Back
Top