Divinity: Dragon Commander Beta

Divinity: Dragon Commander Beta

Euphoria Jun 30, 2013 @ 5:06pm
The Big List of Crash FIXES
I'll keep this as a rolling update as I see different solutions come out.

If you stopped your game from crashing, let me know how and I'll add the fix to the list.

1. Steam's Big Old Memory Dump Fix

Steam limits games to 2 GB of RAM allocation only. I'm not positive, but I'm pretty sure it's because they hate fun.

Once games go over, Steam says "NOPE" and you get the quick desktop crash. It's nothing more than a line drawn in the sand, and is generally bypassable.

To fix it:

Open CMD prompt with administrator and type in without the parenthesis "bcdedit /set increaseuserva 6000".

Change the number 6000 to how much ram you have on your computer minus what you estimate your OS needs. I have 8gb, so mine is set to 6000. (leave some room for system operation, etc). This'll generally stop games from crashing if they go over the 2 gb limit.

Now make sure you've set both steam and the game to automatically run as admin. You have to edit the settings for the steam.exe AND the dragon commander exe.

Seriously be judicious with your memory allocation. You can break your computer: for realzies.

2. Compatability Mode

by Humor

"Go into the Dragon Commander folder, then open up your "Shipping" Folder. There you should find BetaLauncher.exe, and DCA.exe, or whatever it's called. From here, right click and go into the properties of both applications, and simply check "Run As Admin", and change the compatability mode to run as "Windows XP (Service Pack 2)".

Again, I'm not sure if this is going to help anyone out, however, I've been able to proceed into skirmishes without fail, and after repeated attempts."

3. Don't Slot-Lock

by Sauce

"When creating a lobby in multiplayer DO NOT lock other player slots.

I was locking slots so I could try the game in private first, but that led me to crashing all day yesterday. Leaving the player slots unlocked allowed me to load the game."

This solution helped a few others as well.
Last edited by Euphoria; Jul 1, 2013 @ 4:40pm
< >
Showing 1-12 of 12 comments
Euphoria Jun 30, 2013 @ 5:12pm 
Oh, and please post if this doesn't work for you, or more importantly if it did. Most CTD's happen due to memory, so include what your system memory is and what you set it to.
Emperor Marcus Jun 30, 2013 @ 7:51pm 
Ah greeze should have known. I have another program to use on the EXE file to extend its Ram use that i have used for Paradox mods that use alot of ram to run properly.
Emperor Marcus Jun 30, 2013 @ 8:11pm 
Games more stable now but still crash to desktop during the skirmish match i played.
Emperor Marcus Jun 30, 2013 @ 8:31pm 
still crash during desktop. That said i only have like 4 gigs of ram unlike you
Euphoria Jun 30, 2013 @ 10:01pm 
Did you restart your computer after doing this?

Does it crash to desktop while loading, or when things in a match get busy?
perilperineum Jul 1, 2013 @ 3:05am 
Thank you for this, Cupcake. I learned how to do this a long time ago but completely forgot how to do it. I have 32GB of RAM (overkill, yes, I know) and was still running out of memory. The game tends to do a bit of rubber-banding, not latency, but frame lag, but is playable now.

Cheers!
Euphoria Jul 1, 2013 @ 4:10pm 
Great to hear it, Codi. :) Yeah, I first used this trick with the release of Planetside 2, and I've used it for every game since (it's a lifesaver when running Skryim with 100+ mods).

I've been told that the times when your framerate stalls are actually when your game would have crashed otherwise. So each framerate hiccup is a CTD avoided. Relish them!

Cheers
bloodraven43 Jul 2, 2013 @ 6:59am 
nope...dosent work
Avifir Jul 2, 2013 @ 9:43am 
What about the resolution issues? (Input out of Range, etc) Technically not a crash, but yeah...
If you do include a fix for it, feel free to either link to my guide or use parts of it. (If you want to)
Jon Flint Jan 11, 2014 @ 11:15am 
Okay... i messed up. Really sorry. I input the bcedit /set value increaseuserva 6000 before reading your entire text first.. only to realize that is the entirety of my RAM. Tried deleting it using bcedit /deletevalue increasuserva. But now for some reason bcedit is not recognized as an external or internal command. I tried changing the pathing to C:\Windows\System32. I see there are alot of issues with this on the internetz... but im not that much of a computer wiz to just fix this.. All i want to do is delete the value so i can safely play the game again without breaking my computer... cryyyyyy
Last edited by Jon Flint; Jan 11, 2014 @ 11:22am
Raze_Larian Jan 11, 2014 @ 4:17pm 
Originally posted by Rasorshot:
But now for some reason bcedit is not recognized as an external or internal command.

Do you mean bcdedit? If you dropped the 'd' in DOS, that would explain the command not being recognized.

Did you try just repeating the original command, with a lower value? such as:
bcdedit /set increaseuserva 4000
GerahWar Dec 13, 2014 @ 3:16am 
Doesnt work
< >
Showing 1-12 of 12 comments
Per page: 1530 50