libretro / libretro/parallel-n64
Two parallel_n64 core settings not being picked up when changed or when core initially loaded
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 407
- Forks
- 151
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 11
Description
Hi,
Today when trying the latest version (as of today) of parallel_n64_libretro.dll, I notice two issues with how its picking up some configuration changes I have made from within the core settings. I am testing with Goldeneye 64 and have a single parallel ParaLLEl N64.opt, not one per game where I have been tweaking various settings.
I noticed two issues
-
When I set the core to use the widescreen aspect ratio, to match the in-game watch being set to widescreen, it looks perfect. If I then close out of the core and come back in, even though the widescreen setting is there it doesn't get picked up until I toggle it on/off again (or toggle any other setting). It then gets picked up after the toggle. Does it not load on initial startup?
-
When I set the VI Refresh / overclock setting to 2200, it gets picked up and is used. If I then in game set it back to Auto or 1500, it doesn't change back. It stays overcloked, even at auto. I guess it should or should it be tagged as requiring a (restart)? It requires me to quit out of the core and load it again.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue with GoldenEye 64 using a single parallel ParaLLEl N64.opt file, then trace where core settings are loaded on startup and applied after changes. Done means widescreen is honored on initial load and changing VI Refresh from 2200 back to Auto or 1500 takes effect without restarting the core.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100