[Bug 56232] New: Sega Bug fails to initialize
https://bugs.winehq.org/show_bug.cgi?id=56232 Bug ID: 56232 Summary: Sega Bug fails to initialize Product: Wine Version: 3.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75943 --> https://bugs.winehq.org/attachment.cgi?id=75943 WINEDEBUG=+d3d,+ddraw Steps to reproduce: 1. Insert the Sega Bug CD 2. Run `Xephyr :1 -ac -screen 800x600x8 &` 3. Run `DISPLAY=:1 openbox &` 4. Run `DISPLAY=:1 wine 'D:\win95\bug!.exe'` An error dialog titled "Error Initialising" appears that says "A hardware-only DirectDraw object creation was attempted but the driver did not support any hardware." After clicking OK, a second dialog appears that says "Could not initialise DirectDraw". I have a patch that I could apply to Wine < 3.17 to get the game to work, but this error is relatively new. `git bisect` says: 7b2ff904042ee95214b6c5b4a80e51d7f6b24c2b is the first bad commit commit 7b2ff904042ee95214b6c5b4a80e51d7f6b24c2b Author: Józef Kucia <jkucia(a)codeweavers.com> Date: Mon Sep 24 01:09:31 2018 +0200 wined3d: Pass feature levels to wined3d_device_create(). Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Debug traces are attached. I believe the relevant line is: 0024:warn:ddraw:ddraw_surface_create Video memory surfaces not supported without 3D support. -- 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=56232 Alex Henrie <alexhenrie24(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression Regression SHA1| |7b2ff904042ee95214b6c5b4a80 | |e51d7f6b24c2b URL| |https://archive.org/downloa | |d/BUGDEMO/BUG_DEMO.rar --- Comment #1 from Alex Henrie <alexhenrie24(a)gmail.com> --- The free demo has the same problem. $ sha256sum BUG_DEMO.rar 7f8b9b4a0b95819e7386f85a10ff333f6d640dcf4d2c2c46a52273a05a32a68a -- 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=56232 --- Comment #2 from Alex Henrie <alexhenrie24(a)gmail.com> --- The game works in DxWnd 2.06.02 <https://sourceforge.net/projects/dxwnd/> with the following settings: Video > Initial virtual color setting > 8 BPP Video > Initial virtual color setting > Lock GDI > Synchronize GDI to ddraw palette Hook > Do hook update And in winecfg: Graphics > Emulate a virtual desktop -- 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=56232 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com --- Comment #3 from Zeb Figura <z.figura12@gmail.com> --- There are actually two regressions here. I haven't formally bisected the commits, but I'm reasonably confident in this diagnosis. The first regression, introduced by 7b2ff9040 as previously bisected, should have been fixed by b04220a21d315e4f2f75eee4410435deec0c40c7 ("wined3d: Set a feature level for NO3D adapters.") However, before that commit happened, the second regression was introduced by 33d182dd5414c609e65c5882dc92d9cefb5faa31 ("ddraw: Reject creating DDSCAPS_VIDEOMEMORY surfaces with DDRAW_NO3D.") Unfortunately this may very well just be correct behaviour. The game seems to expect video memory support, and I suspect it would fail with a 2D-only card on Windows. I don't know for sure, though. This is the failure that's visible in the attached log, and that warn:ddraw line that you pointed out. So this bug could either be resolved FIXED or INVALID; I'm not sure which makes more sense. Or we leave it open until I'm able to test a 2D-only card on Windows 98 and verify whether the game really does fail that way, but I don't think I have one and I'm not sure how easily I'll be able to acquire one. -- 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=56232 --- Comment #4 from Alex Henrie <alexhenrie24@gmail.com> --- (In reply to Zeb Figura from comment #3)
Unfortunately this may very well just be correct behaviour. The game seems to expect video memory support, and I suspect it would fail with a 2D-only card on Windows. I don't know for sure, though. This is the failure that's visible in the attached log, and that warn:ddraw line that you pointed out.
So this bug could either be resolved FIXED or INVALID; I'm not sure which makes more sense. Or we leave it open until I'm able to test a 2D-only card on Windows 98 and verify whether the game really does fail that way, but I don't think I have one and I'm not sure how easily I'll be able to acquire one.
The game runs successfully on my old 486 desktop PC that has Cirrus Logic CL-GD5434 graphics, which does not support 3D acceleration. -- 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=56232 --- Comment #5 from Alex Henrie <alexhenrie24@gmail.com> --- (The 486 runs Windows 95.) -- 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=56232 --- Comment #6 from Alexandre Julliard <julliard@winehq.org> --- (In reply to Zeb Figura from comment #3)
So this bug could either be resolved FIXED or INVALID; I'm not sure which makes more sense. Or we leave it open until I'm able to test a 2D-only card on Windows 98 and verify whether the game really does fail that way, but I don't think I have one and I'm not sure how easily I'll be able to acquire one.
I'd suggest to mark this bug FIXED for the first regression, and create another bug for the second regression. -- 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=56232 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |b04220a21d315e4f2f75eee4410 | |435deec0c40c7 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Zeb Figura <z.figura12@gmail.com> --- (In reply to Alexandre Julliard from comment #6)
(In reply to Zeb Figura from comment #3)
So this bug could either be resolved FIXED or INVALID; I'm not sure which makes more sense. Or we leave it open until I'm able to test a 2D-only card on Windows 98 and verify whether the game really does fail that way, but I don't think I have one and I'm not sure how easily I'll be able to acquire one.
I'd suggest to mark this bug FIXED for the first regression, and create another bug for the second regression.
I'm at least closing this one. I'm not sure the second regression is valid, so I'll hold off on creating a new bug report for now. -- 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=56232 Alexandre Julliard <julliard@winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Alexandre Julliard <julliard@winehq.org> --- Closing bugs fixed in 11.0-rc4. -- 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