[Bug 32986] New: Fallout New Vegas: Anti-aliasing doesn't work properly
http://bugs.winehq.org/show_bug.cgi?id=32986 Bug #: 32986 Summary: Fallout New Vegas: Anti-aliasing doesn't work properly Product: Wine Version: 1.5.24 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: joedavison.davison(a)gmail.com Classification: Unclassified Before continuing I should mention Multisampling is enabled in the Wine registry. Anti-aliasing in Fallout: New Vegas doesn't seem to work like it should. Values up to 8 samples (as per the launcher) apply anti-aliasing, but it seems like it's only in fact rendering with 2 samples. Selecting 9 samples or more simply disables anti-aliasing altogether. World details are anti-aliased correctly. Buildings, streetlamps and the like are smoothed like they should be, while objects like grass are not. Furthermore, structures in the distance (like pylons) are not aliased at all and look like pencil scribbles from MS Paint. I've observed this in Wine versions throughout the 1.5.x series. My distro is Arch Linux x86_64. DirectX 9 DLL overrides *are* being used as the Steam installer for New Vegas installs DirectX automatically. I have not yet tested it without overrides. This doesn't occur in Skyrim, a game that uses the same engine as New Vegas. My specs: Nvidia 660Ti 2GB 16GB DDR3 RAM Intel Core i5 3.4GHz @ 4.0GHz -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
https://bugs.winehq.org/show_bug.cgi?id=32986 --- Comment #1 from Austin English <austinenglish(a)gmail.com> --- This is your friendly reminder that there has been no bug activity for over 700 days. Is this still an issue in current (1.7.36 or newer) wine? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=32986 xhocfkwl(a)sharklasers.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xhocfkwl(a)sharklasers.com --- Comment #2 from xhocfkwl(a)sharklasers.com --- Issue is still present with 1.7.37. Tested with and without dx9 overrides. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=32986 Nicholas O'Connor <nrfoconnor+wine(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrfoconnor+wine(a)gmail.com --- Comment #3 from Nicholas O'Connor <nrfoconnor+wine(a)gmail.com> --- (In reply to Joe from comment #0)
DirectX 9 DLL overrides *are* being used as the Steam installer for New Vegas installs DirectX automatically. I have not yet tested it without overrides.
That's not how that works. Even though Steam runs the installer for the DirectX DLLs, you still have to manually specify (via winecfg) that you want FalloutNV.exe to use native DLLs. Source: I literally just did this five minutes ago to fix a different series of bugs I was having. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=32986 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- 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.
participants (1)
-
wine-bugs＠winehq.org