(04-23-2018, 06:23 AM)Renazor Wrote: [ -> ]In the GUI there's:
Stable
Beta
Development
Those are update tracks. Stable gives you stable releases only, and Development gives every development build (which is a lot! many per day) Beta just give you development builds once a month, aligned with the progress reports. There's nothing special about them, they are literally just dev builds. The beta update track is just for those that don't want to update for every single new development build.
To reiterate, there is no such thing as Beta builds, there is only the Beta update track.
(04-23-2018, 08:19 AM)Renazor Wrote: [ -> ]I would never want the various development builds to overwrite my main config data which a stable installed version would use.
Moving between builds is seamless because stable and dev builds use the same configuration files and settings. If you change a setting in a stable build, that setting will be changed in dev builds, and vice versa. There is no overriding!
If you want your stable builds to be totally isolated for whatever reason, you can just put portable.txt into your stable build. But we're not going to do that for everyone, as that's not how we want users to use Dolphin.
If you want to run multiple Dolphin builds in portable mode, just use the registry setting to force all Dolphin builds to run in portable mode so you don't have to create portable.txt over and over. It's much more convenient that way.
Looks like it just happened
https://bugs.dolphin-emu.org/issues/11084 
But I'm not holding up the original idea, whatever longterm solution or not you guys come up with, or let's just say it's was a lucky coincidence
How is a GC rumble crash in any way related to this thread? At no point here have you mentioned anything like that.
(05-07-2018, 08:41 AM)MayImilae Wrote: [ -> ]How is a GC rumble crash in any way related to this thread? At no point here have you mentioned anything like that.
I guess it's the other way around in this case, or similar, the older config is messing with a new version (kinda normal), not that the new version is messing with the config files themself, old versions still work fine IMO, just running a newer version thankfully doesn't start overwriting existing configs unless commanded by the user.
But I had something like that in my mind I may have not actually written it in this thread before.
But it's similar, it took me serveral hours to remind myself to check with fresh settings and use portable.txt which lead me deeper into this issue.
It's at least an eample how portable mode helped troubleshoot, even if I could have just cleaned out the global config in the first place, maybe it's a meh argument but hey, horray for portable mode!
Infact I forgot to add portable.txt, that's why I added it, out of ROUTINE, not because I was thinking of trying portable, actually, now I remember. Also it's good I forgot, then I wouldn't discover this crash. What a nice evening story, man I love troubleshooting.
Well, you just used portable.txt correctly - as a diagnostic tool!
We're still not going to ship it with Dolphin builds though, for all the reasons mentioned earlier.
I understand, but for anyone that thought such conflicts "never" happen ... hehe. The interesting part is, out of so many people it's me who discovered it almost right on time, hah. Because I was only speculating at the start, maybe it could have a bit of a difference starting this thread with a solid example, in the end probably not enough, as it looks like too many other reasons, that's understandable.
You haven't shown that this is a "conflict" between different versions. For all we know, you might as well be able to trigger it by only using one version of Dolphin and setting certain settings to certain values.