https://bugs.winehq.org/show_bug.cgi?id=44143
Bug ID: 44143 Summary: Fix “0030:fixme:d3d:resource_check_usage Unhandled usage flags 0x20.” Product: Wine Version: 3.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: Markus.Elfring@web.de Distribution: ---
I could play the game “The settlers (gold edition)” with previous Wine versions in a low graphic resolution for a while. Further software evolution made it unplayable. * Text is not displayed on buttons for main menus. * The scenery display is flickering.
I got the following log during my test attempt.
elfring@Sonne:~> wine /run/media/elfring/SHOK_GOLD/autorun.exe 0030:fixme:win:EnumDisplayDevicesW ((null),0,0x33e4b4,0x00000000), stub! 0030:fixme:win:EnumDisplayDevicesW ((null),0,0x33e854,0x00000000), stub! 0030:fixme:d3d:resource_check_usage Unhandled usage flags 0x20. 0030:fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. 0030:fixme:d3d:swapchain_gl_present WINED3D_SWAP_EFFECT_FLIP not implemented. … 0030:fixme:d3d:resource_check_usage Unhandled usage flags 0x20.
Now I am curious which other open issues will be still remaining if the software situation can be improved a bit more also around such programming interfaces.
https://bugs.winehq.org/show_bug.cgi?id=44143
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Fix |Graphic glitches in The |“0030:fixme:d3d:resource_ch |Settlers |eck_usage Unhandled usage | |flags 0x20.” |
--- Comment #1 from Matteo Bruni matteo.mystral@gmail.com --- Is the game actually The Settlers 2?
Can you find out a Wine version that works correctly and then bisect the regression?
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #2 from Markus Elfring Markus.Elfring@web.de --- (In reply to Matteo Bruni from comment #1)
Is the game actually The Settlers 2?
Which version number belongs to “The Gold Edition”? https://appdb.winehq.org/objectManager.php?sClass=version&iId=5360
Can you find out a Wine version that works correctly
No. - You can see some of my observations for previous versions in corresponding database entries.
and then bisect the regression?
I do not really want to try such a development procedure at the moment.
I would prefer to help a bit in checking improvements for aspects which were mentioned in the shown messages.
https://bugs.winehq.org/show_bug.cgi?id=44143
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Graphic glitches in The |Graphic glitches in The |Settlers |Settlers: Heritage of Kings
https://bugs.winehq.org/show_bug.cgi?id=44143
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-d3d CC| |joseph.kucia@gmail.com
--- Comment #3 from Józef Kucia joseph.kucia@gmail.com --- Might be a duplicate of bug 43627.
https://bugs.winehq.org/show_bug.cgi?id=44143
Béla Gyebrószki gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69@gmail.com
--- Comment #4 from Béla Gyebrószki gyebro69@gmail.com --- @Markus Elfring: Is this also reproducible in the demo version?
https://www.fileplanet.com/148630/140000/fileinfo/The-Settlers:-Heritage-of-...]
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #5 from Markus Elfring Markus.Elfring@web.de --- (In reply to Béla Gyebrószki from comment #4)
I do not know at the moment if my observations can be reproduced also with the demo version for this game. Other software testers can try it out (if desired).
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #6 from Béla Gyebrószki gyebro69@gmail.com --- (In reply to Markus Elfring from comment #5)
(In reply to Béla Gyebrószki from comment #4)
I do not know at the moment if my observations can be reproduced also with the demo version for this game. Other software testers can try it out (if desired).
The reason that I asked you to check the demo is that Wine devs could have a look at the issue without having the full version of the game. I don't have such issues in the game (GOG.com, demo) on Nvidia (proprietary, nouveau/mesa).
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #7 from Markus Elfring Markus.Elfring@web.de --- (In reply to Béla Gyebrószki from comment #6)
Interested developers (and other software users) could take another look as usual.
I don't have such issues in the game …
Did you notice any log messages during your test approach?
How do you think about possibilities to complete the implementation for four functions (in my example) which can be questionable at the moment?
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #8 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Markus Elfring from comment #7)
How do you think about possibilities to complete the implementation for four functions (in my example) which can be questionable at the moment?
The fixme messages you mentioned are unlikely related to the visual problems. Please attach a WINEDEBUG=+d3d,+d3d9 log.
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #9 from Markus Elfring Markus.Elfring@web.de --- (In reply to Józef Kucia from comment #8)
The fixme messages you mentioned are unlikely related to the visual problems.
I find the mentioned messages generally suspicious. How much unwanted software behaviour can an information like “0030:fixme:d3d:swapchain_gl_present WINED3D_SWAP_EFFECT_FLIP not implemented.” trigger?
Can such development challenges be distinguished from difficulties with related software components like Mesa anyhow?
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #10 from Markus Elfring Markus.Elfring@web.de --- (In reply to Józef Kucia from comment #8)
Please attach a WINEDEBUG=+d3d,+d3d9 log.
* For which information would you look in these data?
* Can this log output be filtered for the details which would be really needed for further clarification?
I did not notice an improvement during another test try for this game together with the software “wine 3.0~rc2-730.1”.
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #11 from Markus Elfring Markus.Elfring@web.de --- (In reply to Józef Kucia from comment #8)
Do you find another message worth for further considerations?
002e:warn:d3d9:d3d9_device_QueryInterface {580ca87e-1d3c-4d54-991d-b7d3e3c298ce} not implemented, returning E_NOINTERFACE.
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #12 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Markus Elfring from comment #11)
Do you find another message worth for further considerations?
002e:warn:d3d9:d3d9_device_QueryInterface {580ca87e-1d3c-4d54-991d-b7d3e3c298ce} not implemented, returning E_NOINTERFACE.
No, it's harmless.
(In reply to Markus Elfring from comment #10)
- Can this log output be filtered for the details which would be really
needed for further clarification?
A complete log would be preferred. Logs compress very well.
(In reply to Markus Elfring from comment #9)
Can such development challenges be distinguished from difficulties with related software components like Mesa anyhow?
Generally, someone has to debug the issue and see where the things go wrong in order to confirm if it's a bug in Wine or in a graphics driver.
There are some shortcuts though, e.g. you could record an apitrace [1], upload it somewhere, then I could inspect OpenGL commands generated by Wine for your version of the game, and replay the trace on a different hardware.
[1] - https://github.com/apitrace/apitrace
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #13 from Markus Elfring Markus.Elfring@web.de --- (In reply to Józef Kucia from comment #12)
002e:warn:d3d9:d3d9_device_QueryInterface {580ca87e-1d3c-4d54-991d-b7d3e3c298ce} not implemented, returning E_NOINTERFACE.
No, it's harmless.
Why is such a warning presented at all when this software situation is so “harmless”?
Generally, someone has to debug the issue
This would be nice.
and see where the things go wrong
Which software components are responsible for the display of labels on buttons for example?
in order to confirm if it's a bug in Wine or in a graphics driver.
How much do the mentioned messages influence this situation?
There are some shortcuts though, e.g. you could record an apitrace [1], upload it somewhere, then I could inspect OpenGL commands generated by Wine for your version of the game, and replay the trace on a different hardware.
Do you imagine that I might be affected by other software details which would not be represented by Wine error messages (for incomplete implementations) so far?
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #14 from Józef Kucia joseph.kucia@gmail.com --- Please provide the requested debug information. Wine Bugzilla is not a discussion forum.
(In reply to Markus Elfring from comment #13)
Why is such a warning presented at all when this software situation is so “harmless”?
Wine debug channels are used to trace what an application is doing. The mentioned warning message says that the application tries to do something that doesn't necessarily work. It is not related to this bug report though.
Generally, someone has to debug the issue
This would be nice.
So far, you are the only person who can reproduce the problem, and you didn't provide the requested debug log. The game appears to work fine here.
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #15 from Markus Elfring Markus.Elfring@web.de --- (In reply to Józef Kucia from comment #14)
Wine Bugzilla is not a discussion forum.
It is just another structured communication interface.
The mentioned warning message says that the application tries to do something that doesn't necessarily work.
A lot of function calls can fail for various reasons.
So far, you are the only person who can reproduce the problem,
I am curious if more software users will try it again from their CDs.
and you didn't provide the requested debug log.
* Very detailed log files might exceed size limits (also with compression) for attachments in issue trackers.
* Will the software situation become better also for my test environment if more function implementations will be completed anyhow?
The game appears to work fine here.
Do I stumble on any differences between a demo version and my software packages?
https://bugs.winehq.org/show_bug.cgi?id=44143
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #16 from Markus Elfring Markus.Elfring@web.de --- Created attachment 59984 --> https://bugs.winehq.org/attachment.cgi?id=59984 Log file from another test try for a game with the software “wine 3.0~rc2-730.2”
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #17 from Markus Elfring Markus.Elfring@web.de --- (In reply to Józef Kucia from comment #14)
Do you find the attached data useful for further clarification?
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #18 from Markus Elfring Markus.Elfring@web.de --- Created attachment 59989 --> https://bugs.winehq.org/attachment.cgi?id=59989 excerpt from a screenshot with missing text display
This picture demonstrates a questionable software situation.
https://bugs.winehq.org/show_bug.cgi?id=44143
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #19 from joaopa jeremielapuree@yahoo.fr --- For me, the bug does not occur with the demo.
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #20 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-4.5?
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #21 from Markus Elfring Markus.Elfring@web.de --- (In reply to joaopa from comment #20)
I have observed the questionable display situation also with the software “Wine 4.5-986.1”.
By the way: My test run ended with the message “004a:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0!” this time.
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #22 from Markus Elfring Markus.Elfring@web.de --- The game became playable again with the software combination “Wine 5.0-1095.1”.
Now I am curious if remaining details will get further software development attention.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100 0009:fixme:exec:SHELL_execute flags ignored: 0x00004100 0030:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0030:fixme:d3d:resource_check_usage Unhandled usage flags 0x20. 0030:fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. 0040:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. 0030:fixme:d3d9:Direct3DShaderValidatorCreate9 stub
* I hope also that the run time characteristics can be improved (like a reduction of the startup duration). * It would be nice if higher level system settings will become supported finally.
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #23 from joaopa jeremielapuree@yahoo.fr --- For me, with the demo, everything is fine. NO graphical glitches/ And all the highest videos options are available.
Please attach a screenshot showing the graphical glitches.
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #24 from Markus Elfring Markus.Elfring@web.de --- (In reply to joaopa from comment #23) There are some factors involved why this game software did not activate the maximum graphic functionality in my test environment. How much is the situation influenced by the current Wine capabilities?
https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #25 from joaopa jeremielapuree@yahoo.fr --- Instead of answering questions we did not ask, can you answer questions we asked?
Can an attach a screenshot showing the graphical glitches? If there is no glitch, please close this bug as fixed. And open a new bug report for the problem of capabilities.
The policy of bugzilla is ONE bug report per bug, not one bug report per application.
https://bugs.winehq.org/show_bug.cgi?id=44143
Markus Elfring Markus.Elfring@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |WORKSFORME
--- Comment #26 from Markus Elfring Markus.Elfring@web.de --- (In reply to joaopa from comment #25) The initially reported questionable display was fixed somehow.
Remaining issues might get additional attention by subsequent clarification requests.
https://bugs.winehq.org/show_bug.cgi?id=44143
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #27 from Austin English austinenglish@gmail.com --- Closing.