120 dpi = crash [Archive] - Team17 Forum

PDA

View Full Version : 120 dpi = crash

asylumjim
26 Dec 2007, 06:59
Recently I set my computer up in our living room, and although the TV doesnt have a problem displaying the default 96 dpi scale, I have it set to 120 dpi so I can still read the font from 8+ feet away and keep the resolution to a tolerable 1024X768. But WA seems to have a problem with a 120 dpi scale and crashes instantly.
This is more of an inconvenience then a problem since I am still able to play worms if I reset the font back to 96 dpi(then restart computer for it to take affect.) I dont know where the problem lye's, but with more and more monitor quality TVs coming out, I cant be the only one with this issue. So if there a way to I dunno make a workaround for it in the next patch or add it to the list for 4.0, that would be nice.

KRD
26 Dec 2007, 07:45
Normally having the font size set to something other than the default results in graphical glitches, not a crash. As far as I know. But yes, this won't be a problem once the frontend's remade, which will hopefully happen before version 4.0 already.
Until then, you could try the Large_Fonts_On registry key from the Tweaks folder, the result of this lovely thread:
http://forum.team17.co.uk/showthread.php?t=32478
Post #15 (http://forum.team17.co.uk/showpost.php?p=576669&postcount=15) explains why the frontend's so hard to modify and post #24 (http://forum.team17.co.uk/showpost.php?p=576733&postcount=24) has a couple screenshots of the tweak in action.

CyberShadow
26 Dec 2007, 13:48
Large_Fonts_On will not fix crashes with non-standard DPIs... there is no known workaround, except to revert the DPI to the default setting (96). As far as I know, it's a limitation of the GUI framework that the W:A UI is build on (MFC). Like KRD said, if it's just for W:A then use the large fonts tweak on a normal DPI.
A remake of the front-end won't come before 4.0.

asylumjim
26 Dec 2007, 18:50
Large_Fonts_On will not fix crashes with non-standard DPIs... there is no known workaround, except to revert the DPI to the default setting (96).
Yeah unfortunatily WA isnt what I need the larger font for, but like I said its not a major issue its just an inconvenience, and if its not fixable I can live with it.

Deadcode
26 Dec 2007, 20:15
W:A should work fine with 120 dpi fonts. There was a problem regarding that, but I implemented a workaround back in v3.6.19.7.
Just now I tested it again, both with the latest beta (v3.6.28.0) and with the latest alpha, and both work fine with 120 dpi fonts.
Something different must be going on in your system. Perhaps we can fix it by working with you to troubleshoot the problem.

CyberShadow
26 Dec 2007, 20:40
OK, so there was a fix... taking back what I said - do you get an ERRORLOG.TXT file with the crash?

asylumjim
26 Dec 2007, 22:57
Hmm... well now I feel like an ass cause I just tried it again and it worked fine. Sorry I dont know what was different between then and now but yesterday it seemed that WA would only work if I reverted back to 96 dpi. Im not sure what is useful in the errorlog so here whats on top;
WA caused an Access Violation (0xc0000005)
in module WA.exe at 001b:00409144.
Exception handler called in ExceptionAttacher.cpp - AfxWinMain.
Error occurred at 12/26/2007 00:08:48.
C:\Team17\Worms Armageddon\WA.exe, run by Owner.
Operating system: Windows Vista (6.0.6000).
1 processor(s), type 586.
55% memory in use.
1022 MBytes physical memory.
460 MBytes physical memory free.
2296 MBytes paging file.
1445 MBytes paging file free.
2048 MBytes user address space.
1924 MBytes user address space free.
Read from location 00000000 caused an access violation.
Context:
EDI: 0x00001770 ESI: 0x00000002 EAX: 0x00000000
EBX: 0x00000001 ECX: 0x00000000 EDX: 0x0012966c
EIP: 0x00409144 EBP: 0x00129764 SegCs: 0x0000001b
EFlags: 0x00010216 ESP: 0x0012964c SegSs: 0x00000023
Bytes at CS:EIP:
8b 08 8b 15 3c 5f 6b 00 52 8b 41 58 ff d0 c7 45
I hope this helps in some way and Im sorry for the waste of time.

CyberShadow
26 Dec 2007, 23:46
We can still take a look at the error log - but we'll need all of it. Please compress and upload it if you like.

asylumjim
27 Dec 2007, 03:35
...here is the whole errorlog

CyberShadow
27 Dec 2007, 04:00
I believe that it crashed because it failed to create a DirectDraw surface. Restarts usually fix that. By the way, the upcoming Beta now displays an error message instead of crashing.

vBulletin® v3.8.6, Copyright ©2000-2013, Jelsoft Enterprises Ltd.