What is the best recent dev build in experience?

[retroben]

Sorry if asking this is a problem,but I want to update,yet I know many have mentioned issues with cheats and other bugs so I was wondering what the latest build is that doesn't have such nasty issues so there could be a chance of better/similar performance and improvements over the now fairly old 5.0-4994 build I have and for decent stability.

I think something like this ought to have a sticky thread with each newer build that has been deemed fairly stable in recent testing for most conditions.

The stable 5.0 version has been around for ages and I have a handful of newer builds that work fine but wish to access more of the updates that improve emulation and other features. (despite the move to the currently limited qt-ui and the old ui missing the useful add Gecko cheat option thanks to being qt exclusive)

So,I am looking for a build before that unfinished qt-ui is thrown on top of it,please.
(not bashing the qt-ui,just want to avoid the limitations it has currently,like potentially the debugger stuff,until it gets a bit more complete)

Sure,it would be extra helpful for me to point out every bug I encounter via qt interface so it can be looked into and fixed,but not everybody wants to have to do that.

[Helios]

Latest.

Don't use the Qt UI. simple. The Qt UI isn't default yet.

[JonnyH]

The QT ui is being developed beside the WX one - it's not replaced it in any dev builds, so the latest should still have the "complete" WX gui.

Just don't run the qt version of the executable and it won't ever affect you.

[retroben]

Thanks for the quick responses.

Sometimes the latest build can end up with problems by a single commit,though I can always try each older build to see if an issue isn't happening then mention it to help get it fixed in future commits.

[retroben]

Sorry for double post,but I am running into a warning of "The specified file "bug" does not exist" when using a shortcut file renamed "Dolphin Debug" locally in the same folder as Dolphin itself and appending -debug on the end of it like I have for the older build which is pinned to the taskbar.

I don't think it should require being pinned to the taksbar in order to work without this warning.

To note,the debugger still works after this warning is closed,so the real question is how do I prevent this warning?

[JonnyH]

(02-14-2018, 06:54 AM)retroben Wrote: Sorry for double post,but I am running into a warning of "The specified file "bug" does not exist" when using a shortcut file renamed "Dolphin Debug" locally in the same folder as Dolphin itself and appending -debug on the end of it like I have for the older build which is pinned to the taskbar.

I don't think it should require being pinned to the taksbar in order to work without this warning.

To note,the debugger still works after this warning is closed,so the real question is how do I prevent this warning?

I think you want either just '-d' or '--debugger'

-debug is being interpreted as:
-d -e bug

so it's enabling the debugger, then trying to execute "bug"

(generally, the way GNU-style command line arguments work is a single dash means "one or more single character options follow", while a double-dash means "a single multi-character option follows")

[retroben]

Thanks,that worked with just -d appended.

Issues,games are giving me a magenta screen with the game running???
Just knew with my luck lately that an issue would happen.
Software graphic won't go anywhere and I forgot what settings to use in order to make that visible.

My backend of choice now is D3D11 but OpenGL also has this issue and Vulkan likely has the issue and other problems on Nvidia.
What could of made it this broken,its so disturbing.

Old 5.0-4994 build is still working fine but this latest one wasn't all out of gum.

Edit: Using it without debugger doesn't help,now trying without hybrid ubershaders.

Edit 2: Darn,disabling ubershaders didn't help. Oh bother!

[retroben]

Found out the possible cause,seems that XFB to texture only is making it stay magenta/pink for some odd reason.
Using the accurate (kinda ugly) full XFB makes it render but with slow performance.

Edit: Take note that I must stay on single-core in order for debugger to not crash and glitch out.

Edit 2: Performance actually isn't all that bad as long as the speedhack is active but still slows down in places like Hyrule with pure xfb.

[Kolano]

The magenta screens are an outcome of Hybrid XFB, and as you note can typically be fixed by disabling "XFB to texture only". Please report these titles on their forum pages so appropriate wiki notes / ini updates can be applied for them.

[retroben]

What do I do exactly???

"these titles"

Do you mean list my issue/s and the solution (inconvenient workaround) on a thread with Hybrid XFB in the name on the articles forum section or another sub-forum?

It happens on every game i have tried opening and I can confirm the workaround on the Gamecube version of Zelda Twilight Princess.

One thing I can do is report the bug on bugs.Dolphin or whatever the exact site name is.

Edit: Bug report made and I also found that 5.0-6291 also gives me this issue.