Saints Row 2 Juiced Patch
- Thread starter Soaa
- Start date
RemovePixelationShader=1
And now we wait for the DLC vehicles
Hey everyone. So a few updates to what ended up working for me. Radmin came in clutch, super simple to set up. I was about to delete the game and be done with it. But I'm really glad that I didn't. A huge thank you to everyone who worked on the juiced patch. It totally revived the game and I'm super excited to finish it now. My favorite juiced addon has to be the unlocked framerate. I never thought I'd be playing this game in super high frames and fidelity. Even if the supposed SR2 dev patch doesn't come in, the game is more than playable in it's current state.
Just one small thing that's been hindering me is that I used the radio mod and the way I did it was that I used GOTR and dropped the mod files into it and patched and replaced the files in the main directory and it didn't work. What's weird is that I sent the patched GOTR file to my friend and their radio works perfect and crisp. I think it's not that big of a deal, but if anyone else encountered the same problem, I'd greatly appreciate a workaround for this. Other than that, thanks again everyone for giving advice on a forum that I wasn't even expecting a response on.
Just one small thing that's been hindering me is that I used the radio mod and the way I did it was that I used GOTR and dropped the mod files into it and patched and replaced the files in the main directory and it didn't work. What's weird is that I sent the patched GOTR file to my friend and their radio works perfect and crisp. I think it's not that big of a deal, but if anyone else encountered the same problem, I'd greatly appreciate a workaround for this. Other than that, thanks again everyone for giving advice on a forum that I wasn't even expecting a response on.
How exactly does Juiced detect GotR?
Edit: Could I suggest making the warning a little less harsh? I understand why it's there, but forcing the player out of the game seems a bit much to me.
As well, the check doesn't account for false positives from older mods that were built off GotR. I'm sure there's a valid technical reason for that, but it might be intimidating for new players to see the current warning despite not having installed GotR at all.
Maybe have the message function like the Juiced settings notif; tell the player GotR was detected, warn them that it doesn't fix anything, and then give them the option to quit the game, or keep playing if they know what they're doing or if it's a false positive.
Love the mod, and have nothing but respect for you guys.
Edit: Could I suggest making the warning a little less harsh? I understand why it's there, but forcing the player out of the game seems a bit much to me.
As well, the check doesn't account for false positives from older mods that were built off GotR. I'm sure there's a valid technical reason for that, but it might be intimidating for new players to see the current warning despite not having installed GotR at all.
Maybe have the message function like the Juiced settings notif; tell the player GotR was detected, warn them that it doesn't fix anything, and then give them the option to quit the game, or keep playing if they know what they're doing or if it's a false positive.
Love the mod, and have nothing but respect for you guys.
Last edited:
Juiced used to detect the steam version before it used to auto-patched it, and warn that you should upgrade the exe yourself to do the LAA/4GB Patch yourself, people skipped this easily and still complained on why the Steam version crashes, so no
Then it's not really a false positive you're taking one huge part from GOTR and installing it on vanilla is a recipe for issues
That makes sense. I always played with the LAA patch, so I never even knew that problem existed. My bad.
"allow cutscene pausing to work with controllers"
Is the controller button in this case the same one to open map?