What is the best recent dev build in experience?

[JosJuice]

It's normal that some games give you a magenta screen in some situations if you're using XFB to Texture Only (for instance the results screen in Super Smash Bros. Brawl's classic mode). But if you're getting only a magenta screen and nothing else in an entire game, something weird is going on...

[JonnyH]

I haven't see any issues recently with my gc version of Z:TP

Did you update a previous install? Perhaps it still had some settings hanging around that are now conflicting? Is it still magenta if you extract to a new directory and run with a "portable.txt" file next to the .exe?

[retroben]

I always keep many versions of Dolphin in dedicated folders on a new folder in "C:/Emulators" so no conflicts with read/write access can happen.

So do I just create portable.txt in that version's folder and then run it then configure it all freshly?

[Kolano]

No, every title has it's own forum page under "Game Support", add a posts indicating the issue under the appropriate forum threads.

It's rather unlikely that it occur on "every title" so you've managed to pick a particularly special set of titles if that's the behavior you are seeing.

[retroben]

The portable.txt option fixes my issue. :/

[JonnyH]

(02-14-2018, 08:46 AM)retroben Wrote: I always keep many versions of Dolphin in dedicated folders on a new folder in "C:/Emulators" so no conflicts with read/write access can happen.

So do I just create portable.txt in that version's folder and then run it then configure it all freshly?

Without a local 'portable.txt' for each, this would cause all your different versions to share the global configs (which may be dangerous, as this issue shows, if defaults/names for things/meanings of config values changes between versions), as well as any caches (sharing the shader cache may cause excess invalidation if the keys change based on the dolphin version).

If you have multiple versions installed, it may be a good idea to use the portable mode.

[Kolano]

I think you are describing something different than the typical "Purple" due to Hybrid XFB. With Hybrid XFB titles play normally and only subsections of the image render purple. From your bug report it seems the titles don't run at all and instead output a solid magenta screen?

[Kolano]

If portable.txt fixes it you've twiddled some other setting away from defaults that's to blame.

[retroben]

To point it out for others,it was exactly a setting for XFB which was the old "disable XFB" setting of older Dolphin builds which heavily conflicted with newer updates with Hybrid XFB.

The solution here is that the configuration should always be handled directly by the given build version instead of being part of the global folders.

Not the same could be said for save files like the memory cards and custom cheats on GameSettings files because that is extra annoying to deal with requiring a copy/paste. (problem is I can't even do that because of the other GameSettings set with the hundreds of files for settings)

(Edit) Found that the User folder is there afterward where it just houses the cheats only I think/hope,because I hastily copy/pasted my ol' ini cheat files into it already.

Also was off-putting with the new gci saves but easily solved by selecting the raw memory card option in the drop-down list and placing my saves file into a pre-located directory due to matching the other directory set for it.

For Wii saves I had to remember the binary named folders in the Wii Title directory tree and copy/paste the save folders in there.
An easy way to find the directory for each is to have a save file made on the new version so you can open the location on both then go up some directories until getting inside of the title folder where you copy the folders from the old version to the folder of the new build.

Hope this helps anyone else that could end up running into the same issue and end up using a portable.txt afterward.

Edit: Man,build 5.0-6327 crashes a whole lot more than 5.0-4994 does. I can't get crash dumps working because I previously stopped them from being created from the potential of greatly aging my laptop's HDD when I mess around finding codes due to the frequent close errors that may happen when I break games too much in order to attempt finding an otherwise tough to find code.
All I did was load a save-state then realize I forgot to try and copy/paste my cheat Game Settings ini after purposefully creating a random new cheat in the list so it could reveal the needed directory.
Once I stopped the game,Dolphin just crashes with a close message,I really hate that problem and whole-fully blame Windows for that and its dastardly nature of ruining a lot of things.
Save-states didn't act this harshly on 4994 if that is the main cause.
It can't be dual-core because I use single-core to avoid other crashes that games do themselves along with debugger being broken whilst on dual-core.
Guess I will need to see if other backends share the same fate and hope one works better than D3D11 if that is one thing causing it.

[mstreurman]

(02-14-2018, 11:43 AM)retroben Wrote: To point it out for others,it was exactly a setting for XFB which was the old "disable XFB" setting of older Dolphin builds which heavily conflicted with newer updates with Hybrid XFB.

The solution here is that the configuration should always be handled directly by the given build version instead of being part of the global folders.

Not the same could be said for save files like the memory cards and custom cheats on GameSettings files because that is extra annoying to deal with requiring a copy/paste. (problem is I can't even do that because of the other GameSettings set with the hundreds of files for settings)

(Edit) Found that the User folder is there afterward where it just houses the cheats only I think/hope,because I hastily copy/pasted my ol' ini cheat files into it already.

Also was off-putting with the new gci saves but easily solved by selecting the raw memory card option in the drop-down list and placing my saves file into a pre-located directory due to matching the other directory set for it.

For Wii saves I had to remember the binary named folders in the Wii Title directory tree and copy/paste the save folders in there.
An easy way to find the directory for each is to have a save file made on the new version so you can open the location on both then go up some directories until getting inside of the title folder where you copy the folders from the old version to the folder of the new build.

Hope this helps anyone else that could end up running into the same issue and end up using a portable.txt afterward.

Edit: Man,build 5.0-6327 crashes a whole lot more than 5.0-4994 does. I can't get crash dumps working because I previously stopped them from being created from the potential of greatly aging my laptop's HDD when I mess around finding codes due to the frequent close errors that may happen when I break games too much in order to attempt finding an otherwise tough to find code.
All I did was load a save-state then realize I forgot to try and copy/paste my cheat Game Settings ini after purposefully creating a random new cheat in the list so it could reveal the needed directory.
Once I stopped the game,Dolphin just crashes with a close message,I really hate that problem and whole-fully blame Windows for that and its dastardly nature of ruining a lot of things.
Save-states didn't act this harshly on 4994 if that is the main cause.
It can't be dual-core because I use single-core to avoid other crashes that games do themselves along with debugger being broken whilst on dual-core.
Guess I will need to see if other backends share the same fate and hope one works better than D3D11 if that is one thing causing it.

For Wii saves you can right click the game in the games list and click "Open Wii Save Folder" or you can copy the whole NAND...