Streets of Rage Remake 5.2 - add to Ports ?

hawkes_84

@Refazeshot1 I never use SSH. Is this where you can link up to the Pi command lines via your PC etc? I tend to just press f4 when on the Pi and so all my tinkering from there. As you may have guessed I know nothing of Python or Linux. I tend to the type in what the smart guys tell me and hope it works! :D

Refazeshot1

@hawkes_84 If you have the PI 4 file manager is located in your retropie options from emulation station. All you need is a keyboard. Just navigate to where the system TXT is and its F4 to edit. When you make the change CTRL-X to exit and Y to save. All your doing is removing the extra space at the top of the document. Just make sure if you have little experience with this type of editing; not to edit anything else just the document mentioned.

ExarKunIv

@Refazeshot1 @hawkes_84 scripted updated

Refazeshot1

@ExarKunIv That was fast! @hawkes_84 Just update the script :)

ExarKunIv

@Refazeshot1 i just got to work and saw what was going on, once i duplicated what you guys saw i knew what i had fix

ExarKunIv

@Refazeshot1 said in Streets of Rage Remake 5.2 - add to Ports ?:

@hawkes_84 If you have the PI 4 file manager is located in your retropie options from emulation station. All you need is a keyboard. Just navigate to where the system TXT is and its F4 to edit. When you make the change CTRL-X to exit and Y to save. All your doing is removing the extra space at the top of the document. Just make sure if you have little experience with this type of editing; not to edit anything else just the document mentioned.

@hawkes_84 doing what he said will also work so you dont have to update anything

Refazeshot1

@ExarKunIv We really appreciate all the work that is put into this kind of stuff. Cheers and thank you. This thread should answer any questions in regards to getting the game up and running 100%

hawkes_84

@Refazeshot1 I managed to get all this done and thanks for the info as it's taught me something new about editing rom files etc. Unfortunately it didn't fix the issue for me but I don't think we had the same problem anyway. I could get widescreen fine except for the right black border . I'd actually prefer the pic to be 640x480 like the old Megadrive had it as opposed to wide screen but no such luck. Just to confirm I was to change it to BORDERLESS_SYNC like floob had it and not AUTO?

Refazeshot1

@hawkes_84 The border to the right was the problem I was having but that is only after I updated. Floobs video was just used as a reference to see spacing. It has to stay on Auto.

hawkes_84

@Refazeshot1 thanks. It was on AUTO for me originally so it probably wont fix the border for me but cheers anyway. Still rocking the 800x600 res? if I wanted to update it what am I typing into the command line?

Refazeshot1

@hawkes_84 Correct, Still rocking 800X600 but you can try 640X480 (Be sure it says full screen not windowed in the options. While I understand that is what the megadrive is set too, SORR has some edited effects and flashy graphics thrown it to give it a slightly modern look. I am with you on this one though, you just want to stick to minimum, its what these systems were made for and its great.

hawkes_84

@Refazeshot1 when I do the 800x600 wide screen the picture grows but it's still only populates a small space in the middle of the screen and the rest is cut off. Kinda hard to explain but it's unplayable hence why I stick to the one I have. Same kinda issue with the 640x480. I'm using a regular widescreen TV

Refazeshot1

@hawkes_84 You have it set to full screen in the in game options and have over scan disabled?

hawkes_84

@Refazeshot1 yep. wide screen in game options and overscan definitely disabled unless it's different for ports

Dochartaigh

Sorry all, but is there a definitive way to get this working on a Pi 4? I'm trying to follow along... like tried the very first post after TWO people confirmed that way works... which sadly it didn't... started to follow a bunch of other things too, then somebody else posts they don't work... then that new script was posted (which does it clear out the original script I used? do I have to remove that through experimental packages first?).... then someone that script is wrong and you have to edit it? Or edit things it does? To be blatantly honest I'm now completely lost and don't know much of what you guys are talking about... what XINIT is, bgdi, etc. etc. etc.

I CAN follow clear directions though lol... any kind soul out there have good directions? Are Pi 4 users still getting screen tearing?

I LOVE this game, and haven't gotten it to run since I posted a how-to back in 2016 when it was broken through the experimental menu (off and on) for years.

ExarKunIv

@Dochartaigh
Well it depends on who you got the script from.
If you got it from my GitHub then you just run the upgrade script (instructions are in the readme on the GitHub)

If you got it from zerojay you will have to remove the old one since it will not install over it. If will just add a number after it since there is a double.

Other then changing the settings in the run command the gray box that comes up when you start the game to a certain resolution and you have to play with the settings in the game itself.
It's the combination of these two that will give you the best results.

Hope this helps get you started

hawkes_84

@Dochartaigh I feel your pain dude. You're pretty much in the same boat as me. And this thread having close to 100 posts doesn't help! Good luck!

Floob

@Dochartaigh
Once I get a Pi4 I'll do a step-by-step like the Pi 3B one.

hawkes_84

@Floob cheers fella. I'd have sent you my spare a few months back if I'd known. They're so expensive these days

ExarKunIv

@hawkes_84 @Dochartaigh yeah due to how it runs there is no one size fits all for this game.

And there is a difference from how 5.1 and 5.2 run
5.2 does seem to be more power hungry then 5.1 was on my pi3

You can always remove the xinit from the emulator.cfg and see how that will work. But when I played around with it it seemed to make it run slower when wide screen was enabled.