Resolution Problem Creating Unhandled Exception Crash
Issue #310
resolved
Hi there,
I want to preface this by emphasizing immediately that this is probably all my fault. I was playing Daikatana 1.3, enjoying it as always, when I decided to be an idiot and play around with the screen resolution settings. My default is 1366x768, which I believe is the native resolution of my computer. I set it to some resolution my computer wasn't compatible with (I don't remember which one it was), and so I couldn't even open the game anymore. As a last resort, I used the dedicated console executable in the game directory, and I screwed this up even more by accidentally putting in screen resolution numbers that no computer in existence could possibly work with (like instead of 1366 I may have put 13 or something, you know?). This was quite a while ago, so I'm sorry if I'm a little vague here, but that's what happened. So I can't even launch the game anymore. A minidump file was generated, so I can include that here. Is there anything that can be done, or is this a drill through the hard drive scenario?
Comments (15)
-
-
Hi there,
I’m the user who created this issue, now using an account to comment. Thank you for getting back to me so quickly, and for your help!
Success! The game now works as intended.
You know that movie Idiocracy? You watch and it and you hope to yourself that you wouldn’t fit in that world, but then something like this happens and you start to wonder, you know? Anyways, thank you for getting me out of this one. Much appreciated.
-
Hey Harrison,
Glad it worked out for you. I'll take a look at that dump and make sure there isn't anything else I can do to prevent some crazy values crashing the game.
Do you happen to know what build of DK 1.3 you're using? Date and platform?
-
Also posting the old current.cfg if you still have it will help.
-
Hi Frank,
I reinstalled DK 1.3 just the day before yesterday, so it’s the 64-bit build dated from the 22nd of December 2022, the one that includes pak5 and pak6. As for the config file, I renamed it to ‘newcurrent’. Despite the name, I presume that’s the old one? The game still defaults to current.cfg so I figure this is true. I’ll see if I can attach it in a separate comment.
-
Hello again, apparently only images are allowed to be posted in a comment. Chalk it up to my inexperience with this site, I’m not sure how to get this config file to you.
-
- attached newcurrent.cfg
<div class="preview-container wiki-content"><!-- loaded via ajax --></div> <div class="mask"></div> </div></div> </form>
-
Ha! Never mind it’s there now
-
Ah, OK I see the problem you put it in parantheses:
set r_mode "(1366x768)"
set r_customheight "(1366)"
set r_customwidth "(768)"The parser probably doesn’t work with that so will need to add some sanity checks for invalid input.
I also added the ability to start the game with -safe on the command line. This will default to a 640x480 windowed mode so you can fix it. You’re not the first person to make a goof like this and I think this should help in the future.
-
Okay awesome, thank you again for helping me out with my goof.
Also I suppose this issue probably wasn’t ‘critical’ in hindsight, so pardon me for making it such.
-
Oh also I hope you’ll forgive me for asking since technically this issue isn’t about this: Do you know of any way to slow the player speed down other than turning ‘always run’ off? I love the game as it is, but I thought it’d be cool to try taking it slower for a playthrough.
-
Yes, you can change cl_forwardspeed CVAR. Default value is 200, lower it to move slower.
-
Oh awesome, thank you!
-
- changed status to resolved
No problem. I've used your config file to add some new code that will verify the custom resolution isn't coming up as 0 (it will if you set it wrong, like in your case) and if it does then it will return that it's an invalid resolution and eventually resolve back to 640x480. The -safe command switch will also force it to 640x480 windowed and reset the custom resolution CVARs.
This new code will be in the next release. Thanks for reporting!
-
Absolutely, thank you for helping me out!
- Log in to comment
Hi,
The dump is probably not as useful I’d hope it to be, but I can take a look.
In the meantime, simply go to Documents\My Games\Daikatana\Data folder. In there will be current.cfg. Rename it and restart DK. It should generate default config again for you.
Frank