 |
Cannot reproduce this - opening maps is working perfectly here (Win32 release build). Are you on a DEBUG build? |
 |
No, made the default Linux release build from source through SVN. |
|
|
Just updated from SVN and ran make distclean, ./autogen.sh, ./configure, make, logged in as root, and finally make install like normal. New map never really starts to load, and editor crashes. I get warnings on compiling and this error when trying to install. test -z "/usr/local/lib/darkradiant/scripts" || /bin/mkdir -p "/usr/local/lib/darkradiant/scripts" /usr/bin/install -c -m 644 ././install/scripts/commands ./install/scripts/init.py ./install/scripts/test.py '/usr/local/lib/darkradiant/scripts' /usr/bin/install: omitting directory `././install/scripts/commands' make[2]: *** [install-scriptsDATA] Error 1 make[2]: Leaving directory `/usr/local/games/darkradiant' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/usr/local/games/darkradiant' make: *** [install-recursive] Error 1 |
|
|
Bah, I can't see that behaviour in Windows here. I guess we'll have to wait until I get my Linux set up again by the release of Ubuntu 9.10. Unless you manage to attach a debugger (gdb) and post a stack trace when it's crashing? |
|
|
When I run the release build from console, I get this error in the console right before it crashes. xmlMemFree(A4420F0) error xmlMallocBreakpoint reached on block 0 darkradiant: namespace/Namespace.cpp:169: virtual Namespace::~Namespace(): Assertion `_uniqueNames.empty()' failed. Aborted Is this what you're looking for? Or should I run a debug version? I get other errors too when running the editor in the console. |
|
|
The assertion should only be effective if you're in a debug build - as a workaround you can build a release build of DarkRadiant and the error should be prevented. Still curious that the assertion is firing, as I don't recall that happening for a while. I'll have to check a debug build myself sometime. |
|
|
I'm currently testing a debug build in Windows, but the assertion does not fire on my end. Which map exactly where you trying to switch from and to? Or does this occur with every map? |
|
|
Yes, it only happens with maps that are converted from QuArK Brush Primitives to Doom 3 worldspawn in Doom 3 Editor. Converted maps that I copied from DarkRadiant into other *Radiant editors works fine. I even had to copy the maps one brush at a time, saving in between each brush, because *Radiant editors wouldn't recognize format. Error goes away with correct Doom 3 maps. |
|
|
Same issue as bug 0001955 about copy and paste world brushes inside DarkRadiant. |
|
|
So I gather it is not a DarkRadiant bug? Or is this a conversion issue? In case you have coding skills, would you be interested in writing a converter plug-in? |
|
|
Conversion problem. I wish editors had a converter plug-in, but no, I don't have coding skills. Maybe one day... |
|
|
Fair enough. As there is already an issue report about the old brushDef format, I'll set this report to resolved without fix. |
- Anonymous
