https://bugs.winehq.org/show_bug.cgi?id=46359
Bug ID: 46359 Summary: Vietcong: shooting from weapon causes game crash Product: Wine Version: 4.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3d Assignee: wine-bugs@winehq.org Reporter: havran.jan@email.cz Regression SHA1: b18a53a5b44b651cde8e05200c75eacf54f49926 Distribution: Other
Created attachment 63092 --> https://bugs.winehq.org/attachment.cgi?id=63092 Vietcong: WINEDEBUG=+tid,+seh,+timestamp
With Wine 4.0-rc3 there is new regression: 75b7ff60562880b6e7b646a8fa84486670162d00 for d3d8 (Vietcong) and b18a53a5b44b651cde8e05200c75eacf54f49926 for d3d9 (Vietcong with VCStarter)
Reproducible in Vietcong - all you need to do is shoot from any weapon (or let NPC to shoot at you). Wine crashes every time with: 002a:err:d3d:wined3d_device_process_vertices Failed to map resource.
Vietcong uses software vertex processing.
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #1 from Jan Havran havran.jan@email.cz --- I forgot to note that I was not able to reproduce this bug with +d3d debug channel - this is reason why my output is without these logs.
My system: $ uname -r 4.19.12-arch1-1-ARCH
$ glxinfo | grep string server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 OpenGL vendor string: X.Org OpenGL renderer string: AMD OLAND (DRM 2.50.0, 4.19.12-arch1-1-ARCH, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.1 OpenGL core profile shading language version string: 4.50 OpenGL version string: 4.5 (Compatibility Profile) Mesa 18.3.1 OpenGL shading language version string: 4.50 OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.3.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
https://bugs.winehq.org/show_bug.cgi?id=46359
Jan Havran havran.jan@email.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #2 from Mathew Hodson mathew.hodson@gmail.com --- Is this fixed with this commit? If so, we can mark this as a duplicate of bug 46362.
https://source.winehq.org/git/wine.git/commitdiff/70a95cea66384b475bd3584768...
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #3 from Jan Havran havran.jan@email.cz --- Yes, bug #46362 indeed seems to be duplicate of this bug.
It seems that the crash I mentioned is fixed by https://source.winehq.org/git/wine.git/commitdiff/70a95cea66384b475bd3584768... respectively https://source.winehq.org/git/wine.git/commitdiff/bdccebcab40fdc3bb04c4d6cae... for D3D9 respectively D3D8, but instead of the crash Wine spam output by following line:
wined3d_device_process_vertices Failed to map resource.
So, the crash is fixed, the output messages (hundreds of them) still persists.
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #4 from Jan Havran havran.jan@email.cz --- Created attachment 63149 --> https://bugs.winehq.org/attachment.cgi?id=63149 4.0-rc4-WINEDEBUG=+tid,+seh,+timestamp,+d3d
Update: although crash during shooting is fixed (but there are printed err lines from wined3d_device_process_vertices), I found out that there are other issues.
As I commented on bug #46362, there are issues with certain maps. Some crash during loading and some during certain event. This is example of map Firework, where it crash after taking handmap. After this crash there appears message window of title "TransformPoints", text "ProcessVertices" and one button "ok".
On top of that, in this map is not rendered camp fire, which worked before this regression.
The attached log contains first 20k lines and last 1M5 lines (Wine 4.0-rc4)
https://bugs.winehq.org/show_bug.cgi?id=46359
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #5 from joaopa jeremielapuree@yahoo.fr --- Console outputs are not bug. You can avoid spam with WINEDEBUG=-all. The policy of wine bug tracker is ONE bug report for ONE bug. If your originally bug is fixed, please mark this bug as FIXED. Please, open new bug report for the other bugs that you see with this game.
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #6 from Jan Havran havran.jan@email.cz --- (In reply to joaopa from comment #5)
Please, open new bug report for the other bugs that you see with this game.
This regression is NOT fixed. These crashes and outputs were introduced by ONE commit series and the game still crashes. I can ignore the fact that error output is useless now without additional filtering - but the game it is still unplayable because of this regression.
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #7 from joaopa jeremielapuree@yahoo.fr --- So, why did you write
Update: although crash during shooting is fixed (but there are printed err lines from wined3d_device_process_vertices),
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #8 from Jan Havran havran.jan@email.cz --- (In reply to joaopa from comment #7)
So, why did you write
Update: although crash during shooting is fixed (but there are printed err lines from wined3d_device_process_vertices),
Because that certain crash place was fixed.
In my opinion "fixing" one crash place by introducing another crash places, rendering issues and spam on standard error just is not proper fix. It is replacing one regression by more regressions.
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #9 from Henri Verbeet hverbeet@gmail.com --- (In reply to Jan Havran from comment #8)
(In reply to joaopa from comment #7)
So, why did you write
Update: although crash during shooting is fixed (but there are printed err lines from wined3d_device_process_vertices),
Because that certain crash place was fixed.
In my opinion "fixing" one crash place by introducing another crash places, rendering issues and spam on standard error just is not proper fix. It is replacing one regression by more regressions.
In case it helps, I don't think any bugzilla admin or Wine developer disagrees with your assessment of this bug. We do occasionally get less than helpful comments from well-meaning people trying to help out.
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #10 from Jan Havran havran.jan@email.cz --- (In reply to Henri Verbeet from comment #9)
In case it helps, I don't think any bugzilla admin or Wine developer disagrees with your assessment of this bug. We do occasionally get less than helpful comments from well-meaning people trying to help out.
I am not native speaker so maybe I used some wrong words, I just wanted to explain why I think this bug should not be marked as "fixed".
To end this discussion, I will open new bug(s). The question is: one bug for both
After this crash there appears message window of title "TransformPoints", text "ProcessVertices" and one button "ok".
and
On top of that, in this map is not rendered camp fire, which worked before this regression.
or open separate bugs?
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #11 from Henri Verbeet hverbeet@gmail.com --- (In reply to Jan Havran from comment #10)
(In reply to Henri Verbeet from comment #9)
In case it helps, I don't think any bugzilla admin or Wine developer disagrees with your assessment of this bug. We do occasionally get less than helpful comments from well-meaning people trying to help out.
I am not native speaker so maybe I used some wrong words, I just wanted to explain why I think this bug should not be marked as "fixed".
I think everything you said was reasonable, and just keeping this bug report open until it's fully resolved is fine.
https://bugs.winehq.org/show_bug.cgi?id=46359
--- Comment #12 from Jan Havran havran.jan@email.cz --- So I opened new bug #46403 for crash described in comment #c4
https://bugs.winehq.org/show_bug.cgi?id=46359
Jan Havran havran.jan@email.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |46403
https://bugs.winehq.org/show_bug.cgi?id=46359
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |joseph.kucia@gmail.com
--- Comment #13 from Józef Kucia joseph.kucia@gmail.com --- Please retest if the problem is fixed with https://source.winehq.org/git/wine.git/?a=commit;h=dc3221a9c8cbc967ddd403691...
https://bugs.winehq.org/show_bug.cgi?id=46359
Jan Havran havran.jan@email.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |70a95cea66384b475bd3584768b | |5fffc5f940a17
--- Comment #14 from Jan Havran havran.jan@email.cz --- (In reply to Józef Kucia from comment #13)
Please retest if the problem is fixed with https://source.winehq.org/git/wine.git/?a=commit; h=dc3221a9c8cbc967ddd4036917f0cb5b4caff205
I created bug #46403 for that issue, but yes, all Vietcong related regressions (excluding Wine staging) are fixed now. Thank you.
This one is fixed by https://source.winehq.org/git/wine.git/commitdiff/70a95cea66384b475bd3584768... (D3D9) respectively by https://source.winehq.org/git/wine.git/commitdiff/bdccebcab40fdc3bb04c4d6cae... (D3D8)
https://bugs.winehq.org/show_bug.cgi?id=46359
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.0-rc6.
-
wine-bugs＠winehq.org