New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graphics Glitches on Multiple Games Without Threaded Rendering. #264

Open
PixelCrusader opened this Issue Sep 11, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@PixelCrusader

PixelCrusader commented Sep 11, 2018

Windows 7 64 bit, AMD Radeon HD 6450, Intel i5-2320 CPU @ 3.00GHz
RetroArch 1.7.4 1155e11 - Reicast 0.1 03360bf

There are multiple games that display up to two graphical errors when run with threaded rendering turned off.

  1. A line of white displays at the top and right side of the screen.

  2. When loading, a graphical glitch will appear in the lower left hand corner, in the shape of a square. I am unable to capture this within RetroArch as the UI is unavailable during this. Simply going through the Dreamcast startup screen and/or going through the title screen should reveal the problem most of the time.

Some games that display examples of issue 1 (click to see):

Sonic Adventure:
sonic adventure usa -180906-012349

Crazy Taxi:
crazy taxi usa -180908-174129

Tokyo Xtreme Racer:
tokyo xtreme racer usa -180908-033258

King of Fighters Dream Match 1999:
king of fighters the - dream match 1999 usa -180911-022916

Zombie Revenge:
zombie revenge usa -180911-022736

Some games that have no white lines, but display the square glitch when loading.

Dead or Alive 2
18 Wheeler - American Pro Trucker

None of this seems to occur when threaded rendering is activated. Also, switching from the resolution being used at launch to a much higher one and then switching back seems to mitigate the white line issue in some games, but the problem fullly reappears once another game is launched. Custom cfg aspect ratios are also an imperfect workaround for wide screen monitors.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment