[Bug 39718] d3d9.dll trick for Fallout 3 no longer working in Steam

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=39718

--- Comment #19 from swswine at gmail.com ---
(In reply to mactrix from comment #18)
> (In reply to swswine from comment #17)
> 
> Cool. The game no longer crashes with the imported registry file (and by
> removing the d3d9.dll file and the winecfg entry). Quality settings are set
> to 'Low' but it works. I don't know if the GeForce Go 7300 is the most
> suitable choice.
Is the 'Low' is an automatically imposed limit or the game just don't work if
you set higher settings? If the first is true than changing video card ID to
some newer one should help, otherwise changing the card reported still has a
chance to help but less likely.

> 
> Thanks for the tip, though it's a bit complex to explain to average users.
> 
Well, I suppose if users can find and copy a custom dll for the fix than they
can find and import registry file equally well (this should work just by
clicking the file in Explorer actually). It is also safer as almost no chance
to get a malware with such a fix. If you know some places where the players of
Fallout 3 search for such sort of tricks, maybe it would be a good idea to
deliver this registry file there.

> Also I didn't understand the part how to exclude other apps from the
> modified registry and to only apply it to Fallout 3.
You can't within the same wine prefix. So you should either use a separate wine
prefix for Fallout 3 or remove/add those keys when required. The first variant
(to keep dedicated wine prefixes for different apps) is quite a common approach
actually. If not to bother switching them manually (and also easily switch wine
versions), PlayOnLinux manages these prefixes perfectly for me.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.