Dolphin, the GameCube and Wii emulator - Forums

(12-06-2013, 09:52 AM)JMC47 Wrote: [ -> ]People with NVIDIA graphics cards; it seems as though OpenGL doesn't have the reset bug on certain hardware configurations even on dualcore. If any other users cold confirm this, please let me know.

My Rig:

Linux Mint 16
i7 @ 3.4Ghz
6 GB Ram (Tri-Channel)
Nvidia GTX295 (Single Card configured as SLI) with official 319.32 drivers

Dolphin settings that give me the best performance on f-zero x:

Dolphin Version 4.0-482

Backend = OpenGL
Fullscreen Resolution = Auto
Aspect Ratio = Force 16:9
V-Sync = False
Fullscreen = True

Internal Res = Auto
Anti-Aliasing = None
Aniostropic = 1x
Post Processing = Off
Scaled EFB Copy = True
Per-Pixel = False
Force Texture Filtering = False
Widescreen Hack = False
Disable Fog = False

Skip EFB Access = True
Ignore Format Changes = True
EFB copies = Texture
Accuracy = Fast
External Frame Buffer = Disable
Cache Display Lists = False
Disable Destination Alpha = False
Open CL Texture Decoder = False
OpenMP Texture Decoder = False
Fast Depth Calculation = True
Vertex Streaming Hack = True

Advanced Tab = ALL False

Individual Game Config:
----------------------------------

Enable Dual Core = Override
All other options = Use Config Setting

Notes:
---------

The above settings give me ~50fps on the starting line of a race and once I am in first place I get 60fps most of the time.
The game is NOT completely stable with those settings. I have completed a number of Cups without crashing but I would estimate that there is a 10% chance of seeing some sort of hard lock during a race.

For anyone who is struggling to achieve good speeds I recommend testing the above settings, A point that needs raising that I don't think some people are aware of is that the individual game settings have a higher priority over the main Dolphin config. When trying to achieve performance you must always adjust these first!!!

Hope it helps.

On windows, as long as you don't have vsync on, the game won't crash, which is nice. I also can no longer trigger the reset bugs, which is also nice.

(12-06-2013, 05:02 AM)Toxicshadow Wrote: [ -> ]Out of interest, how did you raise a comment on the commit? Skid suggested it earlier but I could not find any option to add it? Do you require a google code account?

Hmm, I think it just used my regular Google account that was already logged in.

To all Linux users:

Version 4-0-615 cuts performance in half for f-zero gx because it removes the vertex streaming hack.

I believe that the latest nvidia drivers now have support for buffer_storage (the reason for removing the hack) but sadly most ubuntu based distros are stuck at v319.32 in the official repos.

If you cannot use the latest nvidia drivers I recommend that you stick with v4-0-614 which gives very high frame rates.

(edit: referenced the wrong storage type)

This is the fault of non-dolphin entities. Do note that Geforce 8000, 9000, 200, and 300 do not support the Buffer streaming and storage, and will be slower from this point onward.

hi folks,

Hadn't tried this one in a while and thrilled to see that it now keeps at a mostly stable 60FPS during races on my 2500k and integrated HD3000 graphics in Linux (I've overclocked the CPU to 4.1 and the GPU to 1.4, which probably helps), using Dual Core, OpenMP, Fast Depth, Vertex Streaming, and EFB to Texture at 720p.

Using the newest build from the Ubuntu PPA, which is 4.0, 10/19/13.

Only one issue, and it's a major one: the game will periodically quit outright on me. This happens after about 10-20 minutes of gameplay on average, always during a race. Any known fix? Nothing on the wiki seemed helpful apart from not using Dual Core, which doesn't seem like an option with this game, as powerful as the 2500k is.

Thanks!

The wiki is being honest. If the GPU thread falls behind in this game, the game resets for some reason. The only solution is using the Sync GPU option or using Single Core, both of which are huge performance drops.

Ah well, thanks. I thought maybe because the application was quitting outright rather than resetting it was a different issue. Still impressed that I can get 720p on this game with a couple-generations-old iGPU!

The application quitting out outright could mean it's a vsync issue. Try turning off vsync in graphics driver options + dolphin.

Haven't got vsync enabled in Dolphin. Been running F-Zero in fullscreen on one monitor while the other continues displaying the web browser, twitter, etc; if some low-level Xorg vsync setting is the issue there's no way it's worth isolating