rampancy: Editing winmm.dll gets around earlier mentioned bugs with winmm in various GOG games.
Gydion: I keep meaning to ask, do you still need to do this with recent Staging builds? Staging has a patch that should help (fixes JK: DF II at least) as seen in
bug 37983. You would need to set an override of "winmm (native,builtin)" to use it.
Looking at some of the later comments it appears to not be sufficient for Outlaws though?
I honestly haven't checked, but I do know that the override only worked in CrossOver; in vanilla wine it would crash both Jedi Knight and Outlaws. However, that was long, long ago, before wine-staging was even released.
I am tempted to try it out on games like Parkan, though...
rampancy: a) The game apparently needs Mono or .NET installed to run; I've had success with both .NET 2.0 and the version of Mono offered for download when a new Wineskin wrapper is created (presumably from winetricks). .NET 4.0 won't work as the game will complain that it hasn't found the right runtime version to work.
te_lanus: I think it's because I'm using PoL as stated in my report, PoL installs Mono and Gecko by default.
rampancy: b) I had to set ddr=gdi in winetricks, otherwise I got a black screen. Also, I had to set the override winmm.dll to (native, builtin) in winecfg to get music working.
te_lanus: I didn't need anything changed.
rampancy: c) CSMT crashes the game after the opening title crawl, but I never noticed any significant drop in game performance.
te_lanus: CSMT gave me a nice performance boost. didn't find any crash so far
I would hasten to add that these are likely OS X-specific fixes. OS X's display layer and drivers are different enough that, while what works for Linux users likely will work for Mac users 95% of the time, there are the occasional cases where that isn't the case.
Odd that you didn't have to use the winmm.dll override though. I don't recall, were you using wine-staging? (I used staging 1.9.15.)