WineHQ Bugzilla – Bug 34464 – Jagged Alliance 2 fails to start (becomes unresponsive after startup)

Bugzilla

Last modified: 2013-11-15 13:39:51 UTC

Jagged Alliance 2 fails to start (becomes unresponsive after startup)

Bug 34464 - Jagged Alliance 2 fails to start (becomes unresponsive after startup)


Summary:	Jagged Alliance 2 fails to start (becomes unresponsive after startup)

Status:	CLOSED FIXED

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	d3d
Version:	1.7.1
Hardware:	x86 Linux

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Mr. Bugs

URL:	http://www.fileplanet.com/11467/10000...
Keywords:	download, regression

Depends on:
Blocks:
	Show dependency tree

Reported:	2013-09-06 10:31 UTC by Béla Gyebrószki
Modified:	2013-11-15 13:39 UTC (History)
CC List:	1 user (show)

See Also:
Regression SHA1:	6f321ff2f97a4eb1e613022342399c3ffc41bc89
Fixed by SHA1:	aea8d5c11ee42642a77911a76f119e2cd9488f1a
Distribution:	---
Staged patchset:

Attachments
patch (681 bytes, patch) 2013-09-08 16:29 UTC, Henri Verbeet	Details \| Diff
View All Add an attachment (back traces, logs, proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Béla Gyebrószki 2013-09-06 10:31:18 UTC

I observe this problem with a few games. JA2 demo is showing a black screen after startup and the ja2.exe process is consuming 100% CPU, but nothing happens.

Terminal output:
fixme:win:EnumDisplayDevicesW ((null),0,0x32f648,0x00000000), stub!
fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16
fixme:d3d:wined3d_device_set_render_target Surface 0x1282a8 doesn't have render target usage.
fixme:d3d_surface:wined3d_surface_flip Ignoring flags 0x1.

This is a recent regression:
6f321ff2f97a4eb1e613022342399c3ffc41bc89 is the first bad commit
commit 6f321ff2f97a4eb1e613022342399c3ffc41bc89
Author: Henri Verbeet <hverbeet@codeweavers.com>
Date:   Thu Sep 5 09:54:39 2013 +0200

    ddraw: Don't imply WINED3DUSAGE_RENDERTARGET on primary surfaces.
    
    If the application actually wants to do 3D rendering on the primary surface,
    it should set DDSCAPS_3DDEVICE as well.

:040000 040000 7489dc38430c1447071ecac4bbe3d21cfdb3b7f8 4fe57e7d8e75952d72c0916dca3107b22de5f8ee M	dlls

Reverting the patch fixes the problem.

Nvidia binary drivers 325.15

Comment 1 Henri Verbeet 2013-09-08 16:29:16 UTC

Created attachment 45902 [details]
patch

I believe the attached patch should help for at least JA2. There are probably some more places where we assume the front buffer is always a render target though, so the patch may not help for some of the other games you mention, and there's a chance 6f321ff2f97a4eb1e613022342399c3ffc41bc89 is going to come up for future regressions as well.

Comment 2 Béla Gyebrószki 2013-09-08 21:04:25 UTC

(In reply to comment #1)
> Created attachment 45902 [details]
> patch
> 
> I believe the attached patch should help for at least JA2. There are probably
> some more places where we assume the front buffer is always a render target
> though, so the patch may not help for some of the other games you mention, and
> there's a chance 6f321ff2f97a4eb1e613022342399c3ffc41bc89 is going to come up
> for future regressions as well.

Thanks, the patch fixes the problem in JA2 as well as in many other games affected by this regression.

Comment 3 Henri Verbeet 2013-09-13 03:48:49 UTC

Should be fixed by commit aea8d5c11ee42642a77911a76f119e2cd9488f1a.

Comment 4 Béla Gyebrószki 2013-09-13 10:15:37 UTC

(In reply to comment #3)
> Should be fixed by commit aea8d5c11ee42642a77911a76f119e2cd9488f1a.

Fixed indeed, thank you.

Comment 5 Alexandre Julliard 2013-09-13 13:19:52 UTC

Closing bugs fixed in 1.7.2.

Comment 6 Alexandre Julliard 2013-11-15 13:39:51 UTC

Removing 1.6.x milestone from bugs included in 1.6.1.