[Bug 52625] New: Vertex texture fetch advertised on R300-R500 class AMD hardware
https://bugs.winehq.org/show_bug.cgi?id=52625 Bug ID: 52625 Summary: Vertex texture fetch advertised on R300-R500 class AMD hardware Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: pavel.ondracka(a)gmail.com CC: stefan(a)codeweavers.com Distribution: --- I'm not 100% sure if this is an app bug, or if wine messes something up, but Unigine sanctuary reports: Found optional Vertex texture fetch and later fails badly, see https://gitlab.freedesktop.org/mesa/mesa/-/issues/6053 This is with mesa r300 driver (latest git). None of the R300-R500 cards have vertex texture support and as far as I can see mesa correctly reports GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS = 0 BTW Anno1404 under nine also produces TXL opcodes in vertex shaders, but there is might be also gallium-nine problem. The Sanctuary is with pure 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=52625 Pavel Ondračka <pavel.ondracka(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Vertex texture fetch |Vertex texture fetch |advertised on R300-R500 |advertised on R300-R500 |class AMD hardware |class AMD GPUs -- 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=52625 Pavel Ondračka <pavel.ondracka(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://assets.unigine.com/ | |d/Unigine_Sanctuary-2.3.msi -- 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=52625 C. Leu <kle(a)bluewin.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kle(a)bluewin.ch --- Comment #1 from C. Leu <kle(a)bluewin.ch> --- A short side note, maybe Unigine Sanctuary also doesn't work on R500 hardware (in conjunction with WineD3D) because the "ATI texture fetch 4" and "ATI hardware shadow" features are not implemented (or buggy). Regarding this I have opened some time ago a separate report, see bug 52570. PS I post this here because Stefan Dösinger is in the CC mailing list. ;-) -- 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=52625 --- Comment #2 from Stefan Dösinger <stefan(a)codeweavers.com> --- Advertising VTF on r500 HW is something we shouldn't do, that sounds like a bug. Sadly I don't have access to my r500 GPU at the moment, and won't have for a while. Regarding FETCH4, it is indeed unimplemented in wined3d. The reason is that we don't know of a game that needs it and can't be made to work in some other way. The games I know of all have some "more standard" codepath that either already works or could be made to work - e.g. a d3d10/11 renderer that has textureGather in its official API set, PCF shadows via regular d3d shadow formats (aka GL_ARB_shadow). I know that e.g. 3DMark 2006 can use FETCH4, but it will happily use the regular PCF support built into D3DFMT_D24S8, which we do support. Is there some GL interface to implement FETCH4 on r500 hardware? I believe the driver supports GL_ARB_shadow, so we should be good for most situations. (There's a better argument that can be made for DF16/DF24, which is linked to FETCH4 though) -- 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=52625 --- Comment #3 from C. Leu <kle(a)bluewin.ch> --- Thanks Stefan Dösinger for your fast answer! Okay, so it looks that this is clearly a WineD3D related issue not a Mesa one. Will close in this case the Mesa bug. And regarding Unigine Sanctuary it is strange that I can run it in native OpenGL mode only when Gallium Nine is present (in the corresponding Wine prefix). For whatever reason Unigine Sanctuary doesn't starts up properly in a standard Wine prefix. (It is hanging at the start-up screen.) I know, this doesn't makes a lot sense. Maybe @Pavel Ondračka can confirm this behavior. ;-) Unigine Sanctuary can be directly launched from the CLI in OpenGL mode via the Sanctuary_gl.bat file. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=52625 mirh <mirh@protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh@protonmail.ch --- Comment #4 from mirh <mirh@protonmail.ch> --- Idk really if this is the case here, but FWIW it's not that rare to check for features against D3D, even when you are eventually going to use them in opengl. (or at least I know we tended to do that with pcsx2, because you can bet on directx being always available and robust while opengl is driver-provided and hence a can of worms even just for querying capabilities). -- 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 (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla