WineHQ Bugzilla – Bug 23551 – Ignition display hangs when changing resolution

Bugzilla

Last modified: 2013-12-06 13:44:43 UTC

Ignition display hangs when changing resolution

Bug 23551 - Ignition display hangs when changing resolution


Summary:	Ignition display hangs when changing resolution

Status:	CLOSED FIXED

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	-unknown
Version:	1.2-rc6
Hardware:	x86 Linux

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

URL:	http://www.abandonia.com/en/games/107...
Keywords:	download

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-07-07 10:35 UTC by Luke Benstead
Modified:	2013-12-06 13:44 UTC (History)
CC List:	1 user (show)

See Also:
Regression SHA1:
Fixed by SHA1:
Distribution:	---
Staged patchset:

Attachments
+d3d log (46.58 KB, application/x-gzip) 2010-07-07 10:36 UTC, Luke Benstead	Details
+d3d,+ddraw log (155.09 KB, application/x-gzip) 2010-07-08 08:20 UTC, Luke Benstead	Details
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 Luke Benstead 2010-07-07 10:35:12 UTC

Ignition is an old game that by default runs at 320x200. At the game menu you can change the in-game resolution up to 800x600, but the menu itself will always remain at 320x200.

If you select either 640x480 or 800x600 as the in-game resolution and then start the game, the resolution happens but the display is garbled and the game seems to do nothing after this point. This problem does not occur when using  the "Emulate a virtual desktop" setting, only when using proper fullscreen. Also, if you leave the in-game resolution at 320x200 the game runs perfectly, it's something to do with the resolution change.

It's not a driver bug as I've seen the same issue on open source ATI drivers and closed nvidia drivers.

I've attached a +d3d trace but I'm not sure how helpful it is.

Comment 1 Luke Benstead 2010-07-07 10:36:06 UTC

Created attachment 29423 [details]
+d3d log

Comment 2 Luke Benstead 2010-07-07 12:41:54 UTC

Actually, the game does continue using the sound I can hear that the game is continuing, it's just the screen stops being updated.

Comment 3 Luke Benstead 2010-07-08 05:19:19 UTC

The problem seems to occur around line 380 in the log. That's where the mode change is attempted. Soon after it complains about this:

warn:d3d:IWineGDISwapChainImpl_Destroy (0x135568) Something's still holding the front buffer
warn:d3d:IWineGDISwapChainImpl_Destroy (0x135568) Something's still holding the back buffer

Which may be relevant.

Comment 4 Luke Benstead 2010-07-08 05:27:38 UTC

May also be related to bug 13810 as SetDisplayMode seems to be called twice, each time creating a new swap chain. The former of the two seems to be destroyed while the game is still holding a reference to the front and back buffers.

Comment 5 Luke Benstead 2010-07-08 08:20:38 UTC

Created attachment 29434 [details]
+d3d,+ddraw log

Just attached the probably far more useful +ddraw, +d3d log.

Comment 6 Luke Benstead 2010-07-08 08:39:12 UTC

(In reply to comment #4)
> May also be related to bug 13810 as SetDisplayMode seems to be called twice,
> each time creating a new swap chain. The former of the two seems to be
> destroyed while the game is still holding a reference to the front and back
> buffers.

Ignore this comment, the patch in 13810 doesn't fix the problem so not related.

Comment 7 joaopa 2011-05-26 10:01:55 UTC

Works fine here. Can you confirm that bug is fixed?

Comment 8 butraxz 2013-11-24 12:06:57 UTC

Reported as fixed in 2011.

Comment 9 Austin English 2013-11-25 14:32:01 UTC

(In reply to comment #8)
> Reported as fixed in 2011.

Fixed.

Comment 10 Alexandre Julliard 2013-12-06 13:44:43 UTC

Closing bugs fixed in 1.7.8.