Game Development Community

Constructor crashes on startup

by Tobias B. · in Constructor · 01/26/2009 (2:36 am) · 13 replies

Hi,

for some reason, the Constructor crashes on all machines I tested (Win XP Pro 32bit, Vists Business 64bit). V1.0.3 shows the menu bar before it crashes, the 1.0.51 Patch doesn't even show the application window.

What's happening here? One month ago I remember I just opened the program for testing purposes, and it ran fine.

In the meantime, the only changed were some regular Microsoft Win patches and new graphics drivers from nVidia - does Constructor crash on these?

Thanks for help and best regards,

Tobias

#1
01/26/2009 (6:12 am)
No, the updates should be fine. Can you post your console.log?
#2
01/26/2009 (7:10 am)
Threre is no console.log - maybe the application crashes before it creates the log file?!?
#3
01/26/2009 (7:22 am)
Not sure then - maybe something has gotten corrupted. Have you tried reinstalling to a new directory?
#4
01/26/2009 (8:05 am)
I always installed in the same directory.

Choosing a different one, it starts up, I type in my registration code and the proxy, then it crashes and a restart also leads only to crashes.

So it seems to be unable to verify the registration code...

How do I have to type the proxy and port?

Both xxx.xxx.xxx.xxx (IP only) and xxx.xxx.xxx.xxx:xxx (IP:port) failed. Is the implementation that unstable that is crashes if it doesn't find the GG server? And retrying is impossible without installing in a different(!!!) directory?
Btw.: Still no log file after these steps...
#5
01/26/2009 (4:25 pm)
It's probably an issue with their registration system after the site revisions... I'd just wait it out until they fix it on their end.
#6
01/28/2009 (11:42 am)
Hmmpppf!

Hey Guys... your servers are down!!!

(No response)
#7
01/28/2009 (12:52 pm)
The authorization servers should be back up.
#8
01/29/2009 (12:31 am)
Thank you.

Unfortunately, the program still crashes on all machines I have. Is there anything I can do?
#9
01/29/2009 (10:53 am)
Tobias, we did a fix to our ignition system...are you still seeing the issue today?
#10
01/30/2009 (7:51 am)
@Tobias - Are you missing a dependency, or something like that? You may want to check it with DependencyWalker Did you reinstall after the auth servers came back up?

Sorry I'm not much of a help, but I don't really know what's going on. I'm current on MS Patches, and nVidia drivers, and run XP64 and Vista32, but I don't see this problem. :(
#11
01/31/2009 (6:50 am)
Hi,

and first of all: Thanks for help so far - I'm impressed by the help which is offered here!

I reinstalled the software again - no success. I try to register, and a second later the program crashes! But there seems to be a problem - the dependency walker says :

Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

The error reported for most of the DLLs is E6. What is happening? Is it connected to mixed 32bit / 64bit programs and libraries?
#12
01/31/2009 (7:47 pm)
Someone in another thread reported a problem with some versions of the OpenAL32.DLL causing a problem on 64 bit vista (causing it to crash right at startup). It's a longshot, but you may want to try copying that over from a working TGE install... Beyond that, it probably is some sort of 64bit issue.

Have you tried all of the normal vista tricks? Running as administrator, turning off Aero, setting it in compatibility mode for XP?
#13
02/01/2009 (3:39 am)
Got it!

I tried already the Compatibility Mode and ran it as an administrator which didn't change anything, but the following setting in the folder Right Click -> Properties -> Compatibility made it:

- Run program in compatibility mode for WinXP SP2
- Disable visual themes
- Disable desktop composition
- Run as administrator

Now I still have to test it on my XP machines, but may reinstallation with the new ignition system fixes it there...

Thanks to everyone - Jaimi: Your hint was the key ;-)