https://bugs.winehq.org/show_bug.cgi?id=39718
--- Comment #35 from swswine@gmail.com --- (In reply to mactrix from comment #33)
(In reply to swswine from comment #32)
PlayOnlinux or using winetricks in Wineskin don't make it much better, UX still sucks. One problem with winetricks is that you apply it to the entire wrapper. In my case I want to run the PC version of Steam in one wrapper and then Fallout 3 and Fallout New Vegas through that Steam setup. I only need to apply the d3d9 trick for Fallout 3, not for Fallout New Vegas so winetricks or the registry overwrite is not suitable here. Wineskin allows to apply different Windows versions to different exe files through a pretty good winecfg interface. So I can set Fallout 3 to run in Windows XP mode while Fallout New Vegas can run in Windows Vista mode and Steam itself can run in Windows 7 mode (just as an example) - all this within the same wrapper. This is nicely done in winecfg under Wineskin, that's why I am wondering if the same couldn't be done for graphic adapters.
As far as I understand what is UX, the word "UX" cannot stand near setting PciVendorID manually either way (through some GUI, regedit or vim). The same holds true for overriding dlls manually. If you care about UX Apple way you simply can't ask users to set such sort of scary things at all. If you are already asking users to run winecfg each time to switch between the games (or even just once to install the game), why can't you just give them 2 reg files instead to double click? Or just make a shell script wrappers for game start which will update registry each time?