Template:GlobalProblems/NES: Difference between revisions

From Dolphin Emulator Wiki
Jump to navigation Jump to search
(Created page with "{{#if:{{{1|}}}|The problems listed below may/will occur with any NES game on Dolphin.}} === Black Screen/Distortion === All NES Virtual Console games show either nothing but a...")
 
No edit summary
 
(25 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{#if:{{{1|}}}|The problems listed below may/will occur with any NES game on Dolphin.}}
{{#vardefine:tl_globalproblems_NES_active|
=== Black Screen/Distortion ===
 
All NES Virtual Console games show either nothing but a black screen, or show heavily distorted video. The games run, with audio and controls working, but are unplayable. See {{issue|4103}}.
}}{{#vardefine:tl_globalproblems_NES_fixed|
=== <s>DirectX with NES Games</s> ===
Most NES games suffer strange graphical issues when using the DirectX backend with some graphics drivers; notably NVIDIA. This is a driver bug.
{{image|Legend of Zelda-Collector's Edition-Nvidia Title Corruption.png|NVIDIA Title Corruption|br}}
 
As of {{revision|5.0-4869}}, the D3D driver bugs can be worked around by setting Ubershaders to Exclusive/Synchronous (Ubershaders). It's unknown what exactly is going on with the driver that's causing Exclusive Ubershaders/Synchronous (Ubershaders) to work properly.
 
This seems to have been rectified at some point, though it's unclear what resolved it.
}}<noinclude>{{#var:tl_globalproblems_{{#regex:{{SUBPAGENAME}}|/\s+/|_}}_active}}{{#var:tl_globalproblems_{{#regex:{{SUBPAGENAME}}|/\s+/|_}}_fixed}}</noinclude>

Latest revision as of 00:27, 6 June 2021

DirectX with NES Games

Most NES games suffer strange graphical issues when using the DirectX backend with some graphics drivers; notably NVIDIA. This is a driver bug.

As of 5.0-4869, the D3D driver bugs can be worked around by setting Ubershaders to Exclusive/Synchronous (Ubershaders). It's unknown what exactly is going on with the driver that's causing Exclusive Ubershaders/Synchronous (Ubershaders) to work properly.

This seems to have been rectified at some point, though it's unclear what resolved it.