N64 custom screen placement with integer seems to be currently bugged.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
Edit: Think I found the culprit please check my latest message. The 1280x960 resolution option is the issue I think not working as intended for my custom aspect ratio with integer!
Recently updated retroarch on my steam deck to find the mupen64plus -next core screen location right down at the bottom. I use integer scaling & custom aspect ratio.
Changing the custom aspect ratio Y position into the minus brings it back to center
Expected behavior
Launch the core & screen should be dead center with positions x & y be at 0
Steps to reproduce the bug
Load n64 game using mupen64plus-next on vulkun
set integer scale on & use aspect ratio to custom.
Version/Commit
1.20.0
Bisect Results
Haven't tested recently
Check in the nightly version
I don't know
Platform & operating system
Linux, Steam Deck using Flatpak Retroarch from discover store
Affected Cores
Mupen64plus-next
Environment information
Installed through Flatpak
Relevant log output
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with RetroArch 1.20.0 on a Steam Deck using the mupen64plus-next core, Vulkan, integer scaling, custom aspect ratio, and the 1280x960 resolution option. Compare the screen position at custom X/Y values of 0 with the expected centered placement; no source file or test is identified in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- computer-graphics, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100