libretro / libretro/parallel-n64

[RHI] [Angrylion] Various bugs between difference video renderes using Angrylion

Open
#520 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
407
Forks
151
Avg merge
11h 53m
Merged PRs (30d)
11

Description

RA v 1.7.3
Windows 10 x64
16GB DRAM
GTX 1080 driver version 197.55
Haswell 4690K@4.4ghz

Vulkan:

Starting vulkan from the command line breaks Vsync. Using the vysnc flag doesn't seem to help.

OpenGL:
VI Overlay kills the visible display. Audio can be heard playing the background. Toggling VI overlay on/and off within the same game, or between loads of a game produces the same effect.

D3D 10:
Works just fine. Probably a bug with RA, loading a game does not load the shader preset and has to be enabled every time.

D3D 12:
Works fine, but shaders seem to have no effect (probably just not supported yet).

Miscellaneous bug:
Applying per game configurations changes the configuration for the entire core. For example, disabling VI Overlay while running, using the save per game config option, and then loading another title has VI Overlay disabled as well.

Finally, and I am sure the devs are aware of this, there are pretty severe regressions between parallel using gliden64 and CXD4, and m64p using the same plugins. Seeing as the parallelie plugin support was dropped recently, there doesn't seem to be a reason why this should be the case.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Vulkan Vsync, OpenGL VI Overlay, D3D10 shader preset, and per-game configuration cases described for RA 1.7.3 on Windows 10. Compare the listed renderer behaviors and isolate each regression before changing anything; done means the reported reproducible issues are resolved and verified across the affected renderers.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics, game-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.