6,906
edits
F-Zero GX: Difference between revisions
Jump to navigation
Jump to search
move boulder shadow and heat blur slowdown to emulation information, move v-sync crashing to enhancements, remove v-sync off from config. doesn't d3d11 have support for logicops now?
No edit summary |
(move boulder shadow and heat blur slowdown to emulation information, move v-sync crashing to enhancements, remove v-sync off from config. doesn't d3d11 have support for logicops now?) |
||
| Line 14: | Line 14: | ||
== Emulation Information == | == Emulation Information == | ||
=== Missing Boulder Shadows === | |||
In Chapter 2 of F-Zero GX, the boulders that roll across the track will have no shadows in Direct3D. It is very unlikely this can be fixed in D3D; F-Zero GX uses a feature known as "LogicOps" which malfunctions in D3D11. To see their shadows properly, use the OpenGL backend. See {{issue|7183}}. | |||
{{image|F-ZeroGX-Boulders-Direct3D.png|Direct3D}} | |||
{{image|F-ZeroGX-Boulders-OpenGL.png|OpenGL|br}} | |||
=== Heat Effect/Blur === | |||
Sand Ocean's heat effect cuts speed on even the most powerful computers. The effect can be disabled by turning on "Skip EFB Access from CPU." | |||
=== Powersliding Glitch === | === Powersliding Glitch === | ||
When near the start/finish line while racing on a Lightning themed track, the powerslide effect is glitched out, stretching out like a laser beam toward the finish line. This is a glitch with the game and not Dolphin; this occurs even on a real GameCube. See {{issue|6042}}. | When near the start/finish line while racing on a Lightning themed track, the powerslide effect is glitched out, stretching out like a laser beam toward the finish line. This is a glitch with the game and not Dolphin; this occurs even on a real GameCube. See {{issue|6042}}. | ||
| Line 29: | Line 37: | ||
== Problems == | == Problems == | ||
{{Problems|{{#vardefineecho:problems| | {{Problems|{{#vardefineecho:problems| | ||
=== Master Difficulty End Credits === | === Master Difficulty End Credits === | ||
Credits sequence after Master difficulty completion isn't 100% accurate on default settings. The sepia tone images are supposed to appear to the right after the special character movie plays. The specifics have been untested but if the problem is similar to the [[Super Smash Bros. Brawl#Saving Screenshots|Super Smash Bros. Brawl snapshot feature problem]], a snapshot is generated either during a race or after crossing the finish line. Storing EFB Copies to RAM can be taxing, so the best solution would probably be to disable '''Storing EFB Copies to Texture Only''' before crossing the finish line on the third lap and then enabling '''Storing EFB Copies to Texture Only''' after the announcer announces the rank you earned. See {{issue|9065}}. | Credits sequence after Master difficulty completion isn't 100% accurate on default settings. The sepia tone images are supposed to appear to the right after the special character movie plays. The specifics have been untested but if the problem is similar to the [[Super Smash Bros. Brawl#Saving Screenshots|Super Smash Bros. Brawl snapshot feature problem]], a snapshot is generated either during a race or after crossing the finish line. Storing EFB Copies to RAM can be taxing, so the best solution would probably be to disable '''Storing EFB Copies to Texture Only''' before crossing the finish line on the third lap and then enabling '''Storing EFB Copies to Texture Only''' after the announcer announces the rank you earned. See {{issue|9065}}. | ||
{{image|F-ZeroGXEFBtoTexCredits.png|Improper Credits}} | {{image|F-ZeroGXEFBtoTexCredits.png|Improper Credits}} | ||
{{image|F-ZeroGXEFBtoRAMCredits.png|Proper Credits|br}} | {{image|F-ZeroGXEFBtoRAMCredits.png|Proper Credits|br}} | ||
=== Emblem Editor Issues === | === Emblem Editor Issues === | ||
| Line 51: | Line 47: | ||
=== <s>Dual Core Resets</s> === | === <s>Dual Core Resets</s> === | ||
When Dual Core mode is enabled, the game may reset randomly. It generally only resets on the first run and plays fine after that, but it may reset in game. It has been tested and is pretty reliable, but it may reset anyway. Use at your own risk. For an absolute fix, uncheck "Enable Dual Core", or for a faster performing fix, check "Synchronize GPU thread" as per gameINI advice. Fixed with {{Revision|5.0-1012}}, where Sync GPU is enabled by default in Game-Ini. | When Dual Core mode is enabled, the game may reset randomly. It generally only resets on the first run and plays fine after that, but it may reset in game. It has been tested and is pretty reliable, but it may reset anyway. Use at your own risk. For an absolute fix, uncheck "Enable Dual Core", or for a faster performing fix, check "Synchronize GPU thread" as per gameINI advice. Fixed with {{Revision|5.0-1012}}, where Sync GPU is enabled by default in Game-Ini. | ||
}}}} | }}}} | ||
== Enhancements == | |||
=== V-Sync Crashes === | |||
If V-Sync is enabled, F-Zero GX will inevitably crash at some point early in play, to the point where it's difficult to even complete a race. Make sure V-Sync is disabled to avoid this. Alternatively, for NVIDIA GPUs, Adaptive V-Sync can be enabled and not cause F-Zero GX to crash. | |||
== Configuration == | == Configuration == | ||
<!--A full list of options is available at Template:Config/doc--> | <!--A full list of options is available at Template:Config/doc--> | ||
{{Config | {{Config | ||
|efb2texonly = Off | |efb2texonly = Off | ||
|efb2texonlynotes = Corrects Master end credits sequence inaccuracies | |efb2texonlynotes = Corrects Master end credits sequence inaccuracies | ||