ParaLLel N64 not using the widescreen resolution when starting the game
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
Mario Party 1, with ParaLLEl N64 (2.0-rc2). Starts the game in normal-mode, Not widescreen. Widescreen option are set and saved. It was working in older versions of RetroArch, so I think it is a RetroArch bug with loading core options.
Expected behavior
Every time I start Mario Party 1 with ParaLLEl N64 (2.0-rc2).
Actual behavior
ParaLLEl N64 (2.0-rc2) with MarioParty (Have not tested other roms with this core) starts the game in Normal mode, when widescreen is set. Making a small change in options and restart the game, makes the widescreen active.
Steps to reproduce the bug
- Install and use the ParaLLEl N64 (2.0-rc2) Core.
- Start Mario Party 1 and set it to use Widescreen and higher res, save the settings for the game.
- Restart game gives widescreen, but if I close the game and starts it, the settings are saved but the game starts in Normal mode. I have to make a change and restart the game to get widescreen. Every time.
Bisect Results
I was testing different cores to make Mario Party 1 on N64 to work perfect. ParaLLEl N64 (2.0-rc2) makes the game run smooth and perfect + characters are visible on the "turn-map" in the game.
Version/Commit
- RetroArch: Version: 1.8.9
Environment information
- OS: Windows 10 Pro, X64
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.8.9, the ParaLLEl N64 2.0-rc2 core, and Mario Party 1, focusing on saved core-option loading during a fresh launch. Trace the core options used for widescreen and higher resolution, then verify that saved settings are applied without requiring an option change or restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100