Emulator

Game Name?

F-Zero GX

Game ID? (right click the game in the game list, Properties, Info tab)

GFZP01

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

e1081d2e1701de9dd5114388e361dbdf

What's the problem? Describe what went wrong.

When loading F-Zero GX from the system menu by changing disc to it and then going to the Disc Channel it'll start off with the camera being at odd angles in the attract mode.
The car select screen will not display any 3D models and neither will the performance graph (nor will it show the graph or vehicle statistics properly).
Loading into a race/practice will once again show the stage intro with odd camera angles (mainly pointed straight up) and then start into the race with the error messages "NaN cam_pos" and "NaN cam_intr" on screen. Your car will not be visible, nor will the AI cars, you can't move and neither will the AI. Pressing the accelerator only plays the sound effect when in training mode and hitting the boost (together with accelerator) will play the boost sound effect and drain energy.

Additionally the controller calibration will refuse to recognize parts of the joystick range.

Booting the game directly from the Dolphin game list results in normal behavior and a perfect playing experience.

What steps will reproduce the problem?

From Dolphin's main screen:
Tools > Load Wii System Menu 4.3E.
Accept health/safety warning.
Go back to Dolphin, change disc to F-Zero GX.
Open Disc Channel and hit Start once disc is recognized.
Activate either 50 or 60 Hz mode.
See camera being messed up while the attract mode plays; and also for the rest of the game.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Yes. Version 5.0-11617.

Is the issue present in the latest stable version?

According to issue #11952 latest stable doesn't support MIOS, so I saved myself the trouble of installing it.

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

The bisection tool thread says "Broken due to infra changes for now" so I didn't even try.

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]
FIFO logs and screenshots are here: https://www.dropbox.com/s/pigq7qd1al5ht6m/F-Zero%20GX%20Dolphin%20bugreport.rar?dl=0
Inside the RAR you'll find screenshots and FIFO logs taken after launching the game from Dolphin and launching the game through the System Menu.

What are your PC specifications? (CPU, GPU, Operating System, more)

AMD Ryzen 5 3600, NVIDIA GeForce GTX 1070, Windows 10 (1909), 32 GB RAM.

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

[Anything else here]