0002312: game crashes whilst starting - Dwarf Fortress Bug Tracker

(0008338)
Logical2u (manager)
2010-06-13 16:19

Sounds like it might be your video card then.

What version are you using - legacy or SDL? In either case, try the other.

Also try updating your video card drivers.

And also make sure you're installing a clean version - that is, not unzipping/opening the folder on top of an existing DF installation.

(0008341)
ratboy (reporter)
2010-06-13 16:32

sdl with new drivers. It was fine in the 40d sdl version. The card is older nvidia 8600gt but should be good enough I'd have thought. I'll live with it rather than lose any fps as it bogs down with 100+ dwarves at the best of times.

(0008344)
Logical2u (manager)
2010-06-13 16:39
edited on: 2010-06-13 16:39

Have you tried legacy? And as long as you aren't installing 31.06 on top of 40d, I suppose you're fine there.

Have you tried disabling stuff like the intro video in the init options?

I only suggested it was a video card problem since my video card, an 8600 mobile or whatever they call it, has died, it'll take a few attempts to get Windows to properly recognize a video card, and otherwise remove artifacts. It sounded kind of similar to your description.

(0008345)
ratboy (reporter)
2010-06-13 16:51

No but I'm DLing it now. I never install versions of anything on older version, it's just bad practice. And yes movie off

(0008346)
ratboy (reporter)
2010-06-13 16:53
edited on: 2010-06-13 17:09

Ok it works but isn't the idea that the sdl version is quicker and will replace legacy at some point.

(0008354)
Footkerchief (manager)
2010-06-13 17:18

Are you copying over your init file from a previous version? Have you tried SDL when it's freshly downloaded and totally unaltered? If so, does each SDL PRINT_MODE cause a crash?

(0008359)
ratboy (reporter)
2010-06-13 17:58

I modify inits individually, it's easy enough. As for the 2nd question I've done so just now but with the following changes; movies off (for quickness) and graphics on (I want graphics, if you want I can try it off), otherwise totally standard and brand new (previously it was DFG32). Standard, partial:0 and 2, all started but crashed (black non-responsive window) on maximizing the window. accum-buffer and vbo flashed black and disappeared. Frame_buffer worked perfectly 3 or 4 times then flashed black and gone.

(0008363)
Footkerchief (manager)
2010-06-13 18:06
edited on: 2010-06-13 18:10

Please try it with COMPLETELY unaltered init files. I understand you want graphics, but this is Step Zero of tracking down the error.

Are you positive your drivers are up-to-date (version 197.45)?

Do STANDARD and PARTIAL_PRINT crash at all if you don't maximize the window?

(0008364)
ratboy (reporter)
2010-06-13 18:11

197.45 as you say, I even eyeballed them to be sure. As I've said I can work around this but the question is why I am I the only one that reports this. Would a process list help.

(0008365)
Footkerchief (manager)
2010-06-13 18:12

I edited that note with some extra questions:

Please try it with COMPLETELY unaltered init files. I understand you want graphics, but this is Step Zero of tracking down the error.

Do STANDARD and PARTIAL_PRINT crash at all if you don't maximize the window?

(0008372)
ratboy (reporter)
2010-06-13 18:30

In answer to the last part the standard graphics on version is happily genning a world so I'd say no but I'll check further.

(0008373)
ratboy (reporter)
2010-06-13 18:41

Graphics on; standard and partial both load and save successfully as long as their not maximized. Now I'll check a standard version.

(0008375)
ratboy (reporter)
2010-06-13 19:09

Totally untouched other than print mode.
2D is fine
STANDARD is the same as before (BTW it's just graphically dead as there is still music playing.
PARTIAL ditto
ACCUM_BUFFER crash on maxxing
FRAME_BUFFER flash black rectangle
VBO as above

In short accum_ and frame_buffers might have swapped but frame buffer has reacted differently at the same settings earlier.

(0019635)
Footkerchief (manager)
2012-02-15 07:21

Please reopen this report or PM me on the forums if this problem still exists.

Notes
(0008338) Logical2u (manager) 2010-06-13 16:19	Sounds like it might be your video card then. What version are you using - legacy or SDL? In either case, try the other. Also try updating your video card drivers. And also make sure you're installing a clean version - that is, not unzipping/opening the folder on top of an existing DF installation.

(0008341) ratboy (reporter) 2010-06-13 16:32	sdl with new drivers. It was fine in the 40d sdl version. The card is older nvidia 8600gt but should be good enough I'd have thought. I'll live with it rather than lose any fps as it bogs down with 100+ dwarves at the best of times.

(0008344) Logical2u (manager) 2010-06-13 16:39 edited on: 2010-06-13 16:39	Have you tried legacy? And as long as you aren't installing 31.06 on top of 40d, I suppose you're fine there. Have you tried disabling stuff like the intro video in the init options? I only suggested it was a video card problem since my video card, an 8600 mobile or whatever they call it, has died, it'll take a few attempts to get Windows to properly recognize a video card, and otherwise remove artifacts. It sounded kind of similar to your description.

(0008345) ratboy (reporter) 2010-06-13 16:51	No but I'm DLing it now. I never install versions of anything on older version, it's just bad practice. And yes movie off

(0008346) ratboy (reporter) 2010-06-13 16:53 edited on: 2010-06-13 17:09	Ok it works but isn't the idea that the sdl version is quicker and will replace legacy at some point.

(0008354) Footkerchief (manager) 2010-06-13 17:18	Are you copying over your init file from a previous version? Have you tried SDL when it's freshly downloaded and totally unaltered? If so, does each SDL PRINT_MODE cause a crash?

(0008359) ratboy (reporter) 2010-06-13 17:58	I modify inits individually, it's easy enough. As for the 2nd question I've done so just now but with the following changes; movies off (for quickness) and graphics on (I want graphics, if you want I can try it off), otherwise totally standard and brand new (previously it was DFG32). Standard, partial:0 and 2, all started but crashed (black non-responsive window) on maximizing the window. accum-buffer and vbo flashed black and disappeared. Frame_buffer worked perfectly 3 or 4 times then flashed black and gone.

(0008363) Footkerchief (manager) 2010-06-13 18:06 edited on: 2010-06-13 18:10	Please try it with COMPLETELY unaltered init files. I understand you want graphics, but this is Step Zero of tracking down the error. Are you positive your drivers are up-to-date (version 197.45)? Do STANDARD and PARTIAL_PRINT crash at all if you don't maximize the window?

(0008364) ratboy (reporter) 2010-06-13 18:11	197.45 as you say, I even eyeballed them to be sure. As I've said I can work around this but the question is why I am I the only one that reports this. Would a process list help.

(0008365) Footkerchief (manager) 2010-06-13 18:12	I edited that note with some extra questions: Please try it with COMPLETELY unaltered init files. I understand you want graphics, but this is Step Zero of tracking down the error. Do STANDARD and PARTIAL_PRINT crash at all if you don't maximize the window?

(0008372) ratboy (reporter) 2010-06-13 18:30	In answer to the last part the standard graphics on version is happily genning a world so I'd say no but I'll check further.

(0008373) ratboy (reporter) 2010-06-13 18:41	Graphics on; standard and partial both load and save successfully as long as their not maximized. Now I'll check a standard version.

(0008375) ratboy (reporter) 2010-06-13 19:09	Totally untouched other than print mode. 2D is fine STANDARD is the same as before (BTW it's just graphically dead as there is still music playing. PARTIAL ditto ACCUM_BUFFER crash on maxxing FRAME_BUFFER flash black rectangle VBO as above In short accum_ and frame_buffers might have swapped but frame buffer has reacted differently at the same settings earlier.

(0019635) Footkerchief (manager) 2012-02-15 07:21	Please reopen this report or PM me on the forums if this problem still exists.

Issue History
Date Modified	Username	Field	Change
2010-06-13 16:15	ratboy	New Issue
2010-06-13 16:19	Logical2u	Note Added: 0008338
2010-06-13 16:32	ratboy	Note Added: 0008341
2010-06-13 16:39	Logical2u	Note Added: 0008344
2010-06-13 16:39	Logical2u	Note Edited: 0008344	View Revisions
2010-06-13 16:51	ratboy	Note Added: 0008345
2010-06-13 16:53	ratboy	Note Added: 0008346
2010-06-13 17:09	ratboy	Note Edited: 0008346	View Revisions
2010-06-13 17:18	Footkerchief	Note Added: 0008354
2010-06-13 17:58	ratboy	Note Added: 0008359
2010-06-13 18:06	Footkerchief	Note Added: 0008363
2010-06-13 18:10	Footkerchief	Note Edited: 0008363	View Revisions
2010-06-13 18:11	ratboy	Note Added: 0008364
2010-06-13 18:12	Footkerchief	Note Added: 0008365
2010-06-13 18:30	ratboy	Note Added: 0008372
2010-06-13 18:41	ratboy	Note Added: 0008373
2010-06-13 19:09	ratboy	Note Added: 0008375
2010-06-21 11:36	Footkerchief	Relationship added	related to 0002371
2010-06-21 11:38	Footkerchief	Tag Attached: SDL-only
2012-02-15 07:21	Footkerchief	Note Added: 0019635
2012-02-15 07:21	Footkerchief	Status	new => resolved
2012-02-15 07:21	Footkerchief	Fixed in Version	=> 0.31.07
2012-02-15 07:21	Footkerchief	Resolution	open => fixed
2012-02-15 07:21	Footkerchief	Assigned To	=> Baughn