Darkradiant Doesn't Start

[sparhawk]

I can put this in the bugtracker, but I think I ask first, wether this is only a local problem of my configuration. Still, it probably shouldn't happen, nevertheless, because if there is really a problem with my setup, then it should tell me about it.

 

When I start DR, I get the graphic splashscreen. Then it asked me about my global preferences and then it showed me a nice error message saying there is a problem in lib/signal/signal.h:341, assertion failure SignalBase::disconnet invalid id.

 

When I click OK, I get the error from windows about invalid pointer references, a few other such boxes as above, and then DR dies.

 

Also I wonder why it asks me about my preferences again. It already was configured with an earlier release. Does this mean that my setup has been overwritten?

[greebo]

I don't know what could cause the signal.h error, but I guess your local user.xml file could be the source of some problems. Have you tried renaming your local user.xml (the one in C:\Dokumente und Einstellungen\sparhawk\Anwendungsdaten\DarkRadiant\).

 

DR always asks you if you want to reset your settings if the previous startup failed, but you don't necessarily have to choose "yes".

[sparhawk]

It doesn't work on both accounts. I try to remove this XML file you mentioned.

[sparhawk]

There is no user.xml on this path that you told me. Only a global.pref and a directory doom3.game which is empty.

 

The error log looks like this (the last message repeats at least 10 times and I also have to click each time, which should be avoided). It would be convinient to have a button to ignore further messages, because it is pretty dumb to click 15 times on OK.

 

-------------------------

Started logging to D:\User\Profiles\Administrator.GERHARD\Anwendungsdaten\DarkRadiant\/radiant.log

Today is: Fri Jan 26 17:18:22 2007

This is DarkRadiant 0.8.0

libs/signal/signal.h:341

assertion failure: SignalBase::disconnect: invalid id

----------------

----------------

libs/modulesystem/singletonmodule.h:95

assertion failure: module still referenced at shutdown

----------------

----------------

libs/modulesystem/singletonmodule.h:95

assertion failure: module still referenced at shutdown

----------------

----------------

libs/moduleobservers.h:36

assertion failure: ModuleObservers::~ModuleObservers: observers still attached

----------------

----------------

libs/modulesystem/singletonmodule.h:95

assertion failure: module still referenced at shutdown

----------------

----------------

libs/moduleobservers.h:36

assertion failure: ModuleObservers::~ModuleObservers: observers still attached

----------------

----------------

libs/modulesystem/singletonmodule.h:95

assertion failure: module still referenced at shutdown

----------------

[greebo]

What version of DarkRadiant have you been using before?

[OrbWeaver]

If in doubt, I would delete the entire DarkRadiant folder underneath Application Data. This will lose your settings but at least it will confirm whether there is a problem with the application itself.

 

I don't understand why these assertions are even appearing, since this is supposed to be a release build which does not use assertions.

[sparhawk]

What version of DarkRadiant have you been using before?

 

Maybe it was 0.5 but I'm not sure as I didn't do much with it anyway, so I usually used D3edit for the little. I had DR setup and running though, but this was long ago. Maybe it was even before 0.5.

 

BTW: there seems also to be a problem with the shutdown. I could not delete the directory itself because it is locked. In the tasmanager I can see nothing that would indicate DR, so I don't know what it is that locks it. I could delete all the files though.

[sparhawk]

Deleting the old version helped. Now it works.

[greebo]

Phew, glad that helped.

[sparhawk]

When I close DR, then I get another assert. orphan shader still referenced in plugins/shaders/shaders.cpp:690