libretro / libretro/parallel-n64
(Win64) Internal resolution core option issues with Angrylion
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 407
- Forks
- 151
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 11
Description
Besides the fact that the Angrylion plugin is unplayably slow at the moment on most games, I encountered a couple of issues with it. Given it is a software plugin, internal resolution option settings should not affect its output, but they in fact do. Setting it to 320x240 zooms in the image to the upper left hand corner, and higher resolutions result in other weirdness like the image being squished or repeated, a black screen, or even outright crashes. Only 640x480 makes it look as it should.
Problem is, some shaders get messed up due to this. Interlacing.cg, for instance, activates its interlacing effect on this setting, which is, of course, wrong behavior for most N64 games. To get the proper effect, I had to disable said interlacing within the shader code itself to get stable scanlines.
I may as well also mention that games which ARE interlaced or switch to an interlaced mode mid-game crash RetroArch immediately.
I realize, of course, that this is a WIP plugin still undergoing proper integration, but I thought I'd mention some of the behavior I encountered upon testing.
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
Start by reproducing the Angrylion plugin behavior on Win64 with internal resolutions other than 640x480, including games that enter interlaced modes. Investigate how resolution settings and interlacing reach the plugin and shaders; done means these settings no longer distort, blank, or crash output and interlaced games remain stable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100