The 3 of them will be worth something in the future, especially brand new, which is why I'd really like to keep them that way.
I have both rogue squadron games as well as Bounty Hunter, still sealed, and i really don't want to open them to play on my real gamecube, plus I REALLY want to play them at 1080P. What I am after is ANY help for particular settings to run the Star Wars games well. So I am confident that there is *some* way I will be able to have a good dolphin experience on this machine.
MSI Alpha 15, 3750H quad core, 16GB ram, 5500M 4GB, Win 10 Home.ĮTA prime does tons of dolphin videos and he is showing success even with the in built Vega graphics on the AMD APU's, at 1080P upscaling (and even higher on some games). In any case, I decided to just buy a windows laptop dedicated to emulation and nothing else, so i got a nice cheapie. using Nvidia 1050TI for example and an average quad core CPU.Īre you sure something hasn't been broken in the last year or so in Dolphin with regards to certain games? The thing is, and this is a big "thing", there are TONS of videos out there showing fantastic Rogue squadron performance even at 4K upscaled, in older Dolphin builds. I have bootcamp installed on this and no joy either. I decided to return the machine for other reasons (Catalina breaking 50% of my music apps) and am back to my 2015 haswell 2.8ghz quad core with Nvidia 750M and Mojave.
I was hovering around 3.8ghz on all 8 cores when the issues happened (16" macbook pro has decent thermals). this was ATI's top mobile graphics card (equivalent to about a 1660TI Max Q but with 8GB ram) and Intel's very fastest mobile chip in existence. the reason I am posting in here, is because of the post that said it might be an Nvidia issue. and I could not get ANY game to run without stuttering, even at native res, let alone upscaled LOL! Note this post sort of goes OT but it tells a story and explains all the issues I had with Dolphin and Star Wars games.Īfter I had no success on mac with Dolphin and it was suggested I use bootcamp, I ended up upgrading to a 16" MBP, 8GB 5500M, 64GB Ram, 2TB SSD, 9980HK 8 core CPU.
It may be that there simply isn't a CPU on the market fast enough to emulate these features at full speed. It may be that you're still CPU bound, despite having a fast CPU that can easily blaze through the majority of titles without breaking a sweat.
(12-23-2019, 02:27 AM)JonnyH Wrote: But be aware the Rogue Squadron games are notorious for using weird and wonderful gamecube/wii hardware features that few other games utilize, which are often hard to emulate on a PC architecture. If that is the case, you may still be able to get small improvements by tweaking the clocks - the ryzen 10 series respond more to RAM clock tuning than CPU clock tuning for the most part - there may be some performance you can gain there, but at best it'll be a few percent, so likely only useful if you're just on the verge of being smooth, rather than making a completely unplayably choppy game buttery smooth.
One thing that may be useful to try is to disable vsync (in both dolphin and the nvidia control panel) - while it might tear, if the stutters disappear that may suggest it's a frame timing issue - that can often be caused where you're just on the cusp of running it at 100% speed, but occasionally *just* misses the vsync period, so has to wait for another frame before displaying the next - so the same frame is shown twice appearing as 'stutter'.īut be aware the Rogue Squadron games are notorious for using weird and wonderful gamecube/wii hardware features that few other games utilize, which are often hard to emulate on a PC architecture. Ubershader options aside, your GPU should be more than enough to run any title at non-crazy settings (IE not more than 4k IR, no stupidly high MSAA or similar). The "Stutter on NVidia GPUs despite async ubershaders enabled" is only visible in some titles on the OpenGL and Vulkan backends - if it still stutters on the D3D backend it's not that.įor ubershaders, make sure you're using the 'asynchronous ubershaders' option - the others are only really for debugging issues (the synchronous ubershaders option puts a LOT more load on the GPU for no benefit, it's only useful for debugging and testing issues like the stuttering mentioned above) or extremely resource-limited systems.