Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

San Francisco Rush 2049 - Screen cropped at the top. #137

Closed
PixelCrusader opened this issue Jul 8, 2018 · 9 comments
Closed

San Francisco Rush 2049 - Screen cropped at the top. #137

PixelCrusader opened this issue Jul 8, 2018 · 9 comments

Comments

@PixelCrusader
Copy link

PixelCrusader commented Jul 8, 2018

Windows 7 64 bit, AMD Radeon HD 6450, Intel i5-2320 CPU @ 3.00GHz
RetroArch 1.7.3 - Reicast 0.1 d8a0197

The top of the screen is obscured. The game does not respond to in-game video settings.

san francisco rush 2049 usa -180708-043628
san francisco rush 2049 usa -180708-043941
san francisco rush 2049 usa -180708-043526
san francisco rush 2049 usa -180708-043537


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@flyinghead
Copy link

@twinaphex This commit flyinghead/flycast@c035635 should fix it

@inactive123
Copy link

@flyinghead Backported - 02beb05

@inactive123
Copy link

Seems fixed to me -

image

@PixelCrusader
Copy link
Author

That picture looks accurate, yes. With a +25 vertical center, the bottom of the screen would be filled in too.

Please excuse my inexperience. I'm an end user not really familiar with downloading and compiling from here. Have the changes been made to buildbot nightlies? If not, I'm willing to take your word for it and close the issue. Currently on version fb98f7e.

@inactive123
Copy link

Download the core again tomorrow and it should be up to date with latest then.

@PixelCrusader
Copy link
Author

Reicast 0.1 c3712fa

The screen cropping at the top no longer occurs. Thanks! There does seem to be a very slight amount of overscan at the very top of the screen, it's most noticeable on the game's main menu and on the pause menu. I'm only pointing it out for thoroughness' sake, though.

The only big problem that I can still see are with the in-game video settings. The game still doesn't seem to respond to increasing the vertical center.

san francisco rush 2049 usa -180710-200620

san francisco rush 2049 usa -180710-200713

Increasing vertical center should normally stretch the game display downward, completely covering the black border at the bottom at around +26 before stretching off of the monitor's screen at higher numbers. Set correctly, it would look like this (edited photos):

san francisco rush 2049 usa -180710-200620edit

san francisco rush 2049 usa -180710-200713edit

@flyinghead
Copy link

I'm pretty sure these video settings just change the timing of vblank/hblank interrupts in the output video signal of the Dreamcast. They do not change the generated bitmap image and thus have no effect in an emulator.

@PixelCrusader
Copy link
Author

PixelCrusader commented Jul 11, 2018

I see. I only thought otherwise because both Redream and Demul have the same problem with the empty space at the bottom, and the video settings could be used to work around it.

If it's working as intended, I think this issue can be closed.

Edit: Upon looking up gameplay footage, it could be not a matter of the game filling the whole screen, but of the game being oriented towards the top of the screen rather than centered in the middle.

References: 1 2 3

@PixelCrusader
Copy link
Author

Windows 7 64 bit, AMD Radeon HD 6450, Intel i5-2320 CPU @ 3.00GHz
RetroArch 1.7.5, Git 7c93a0934e, Reicast 0.1 207db67

I hesitated to post this, because I didn't know if this was really a definitive solution or just a band-aid fix that offloaded more work onto end users.

Rush 2049 has been working fine for me now, because I've learned about using custom configurations and custom aspect ratios in RetroArch:

san francisco rush 2049 usa -181109-194104

Before I go further I should point out that doing this will break the games outside of fullscreen mode. If you play in windowed mode, this isn't for you.

What you need is a config file in RetroArch/config/Reicast with a name that matches that of the game you're trying to modify. You can do this by creating a .cfg file with a text editor, but another way is to just save a game override within RetroArch. Launch the game > Open the Quick Menu > Overrides > Save Game Overrides.

My cfg file for this game looks like this:

aspect_ratio_index = "23"
custom_viewport_height = "1181"
custom_viewport_width = "1466"
custom_viewport_x = "227"
custom_viewport_y = "-11"

YMMV. What works for my monitior might not work for another. If you want to do this yourself, change the values in a text editior and save it as videogame.cfg, Otherwise, you can calibrate the screen in RetroArch. Launch the game, open the Quick Menu and back out into the Main Menu without the closing the game. Go to Settings, then go down to Video. Scroll down, change the Aspect Ratio to Custom and then change the Custom Aspect Ratio X Pos, Y Pos, Ratio Width and Ratio Height as needed. You can use a ratio calculator if you have trouble maintaining the correct aspect ratio.

https://www.google.com/search?q=ratio+calculator&ie=utf-8&oe=utf-8&client=firefox-b-1

Once you've resized the image, you can drag it all the way to the left edge of the screen, count the custom_viewport_x number it lands on (hopefully 0), then drag it all the way to the right, noting the number it falls on when the screen hits the edge. Divide by that number (far right value plus the amount of negative numbers you might get on the left) by half and you know what number to center the screen on. Either that, or just move it to the left and right until it looks right to you.

For more information on this and some already made custom cfgs, you can go here:

https://forums.launchbox-app.com/topic/36088-zombeavers-retroarch-psx-and-saturn-overrides/

So with all that out of the way, San Francisco Rush 2049 currently runs great on Reicast Libretro, if you're willing to go through the extra hoops to make it that way.

If there are no objections, I will be closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants