https://bugs.winehq.org/show_bug.cgi?id=53671
Stefan Dösinger stefan@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan@codeweavers.com
--- Comment #4 from Stefan Dösinger stefan@codeweavers.com --- Woo, so 15 years late a non-zero number of users cares about using wined3d to bring d3d10 to Windows XP :-) .
We most likely get some GL capability check wrong. Do you get an GL errors? Those would be reported to stderr. If the application you are running is marked as GUI subsystem (not console subsystem) it won't print anything by default, even if you run it from a cmd shell. You'll have to redirect output to a file (e.g. foo.exe 2>> log.txt)
with "set WINEDEBUG=d3d" you enable d3d debug logging. If the output file is empty, something is wrong. It should have lots of content. An error reported from GL is marked with ">>>>>>>" in the output.