Trunk 3348 CTD

NorthenderPNE · Post by **NorthenderPNE** » Sat May 15, 2010 8:54 am

Right this is what i did in exact order. First, upon startup i load new commander, second i launch from station, thirdly i pause the game and select start new game. Every time it CTD with or without Addons!

Note, that's with and without addons.

Oh and it does this when not loading a commander with and without addons. Right off to bed, some people worked last night!

Post by **another_commander** » Sat May 15, 2010 9:11 am

That's the beauty of trunk: one day it works fine, the next day it spontaneously combusts. You can never get bored with it.

SVN3348 is extremely unstable and we are fully aware of it. You will also find that just adding System Redux in your OXP folder will kill the game every single time you attempt a launch from station.

We are working on it. Stay tuned.

JensAyton · Post by **JensAyton** » Sat May 15, 2010 11:01 am

I believe this is fixed in r3350.

Yrol_Denjeah · Post by **Yrol_Denjeah** » Sat May 15, 2010 11:05 am

I get some errors with r3350
( windows pc, using the builtpackage from the wiki )

Compiling file src/Core/Materials/OOTextureLoader.m ...
src/Core/Materials/OOTextureLoader.m: In function `+[OOTextureLoader loaderWithTextureSpecifier:extraOptions:folder:]':
src/Core/Materials/OOTextureLoader.m:103: warning: instance variable `path' accessed in class method
src/Core/Materials/OOTextureLoader.m:103: warning: local declaration of `path' hides instance variable
src/Core/Materials/OOTextureLoader.m:104: warning: instance variable `path' accessed in class method
src/Core/Materials/OOTextureLoader.m:104: warning: local declaration of `path' hides instance variable
src/Core/Materials/OOTextureLoader.m:113: warning: instance variable `path' accessed in class method
src/Core/Materials/OOTextureLoader.m:113: warning: local declaration of `path' hides instance variable

Anything i can help with?

JensAyton · Post by **JensAyton** » Sat May 15, 2010 11:21 am

Suppressed in r3351.

Yrol_Denjeah · Post by **Yrol_Denjeah** » Sat May 15, 2010 11:50 am

Yup

I am getting MASSES of errors related to OOopengl.m line 65:
[rendering.opengl.error] OOOpenGL.m:65: OpenGL error: "invalid enumerant" (0x500), context: SkyEntity after drawing <SkyEntity 0x1209afa8>{position: (-1842.29, 3615.28, 24271.9) scanClass: CLASS_NO_DRAW status: STATUS_EFFECT}

Thousands of them, prolly because it throws an error each time i
move a millimeter in space or so.

JensAyton · Post by **JensAyton** » Sat May 15, 2010 12:19 pm

I’d like a report with OO_CHECK_GL_HEAVY enabled. I think this will work:

Code: Select all

make clean
make debug=yes OO_CHECK_GL_HEAVY=yes

You should then get the error report for a different file/line, probably OOSkyDrawable.m.

Yrol_Denjeah · Post by **Yrol_Denjeah** » Sat May 15, 2010 12:24 pm

On the way...

Ahruman:
Email sent. As i do not know exactly what part of the log is important,
i just made a big one and as thats too big for the forum, i zipped it
and sent it to you.

The part with OOSkyDrawable.m is fairly tiny.

Post by **another_commander** » Sat May 15, 2010 1:14 pm

There are still problems in the trunk, but the "invalid enumerant" (0x500), context: SkyEntity after drawing <SkyEntity 0x1209afa8>{position: (-1842.29, 3615.28, 24271.9) scanClass: CLASS_NO_DRAW status: STATUS_EFFECT} errors have been around for ages (they are silenced by default) and are not critical. Still, it would be desirable to get rid of them somehow.

Yrol_Denjeah · Post by **Yrol_Denjeah** » Sat May 15, 2010 1:24 pm

Hmpf

That is what i meant. I lack the ability to judge between
what really is an error and what is just an usual bug.

Post by **another_commander** » Sat May 15, 2010 1:26 pm

Yrol_Denjeah wrote:
Hmpf

That is what i meant. I lack the ability to judge between
what really is an error and what is just an usual bug.

That's fine, whenever someone notices something unusual or otherwise worth reporting, by all means please do so. It might be that we have missed somehting and any input is appreciated.

Yrol_Denjeah · Post by **Yrol_Denjeah** » Sat May 15, 2010 1:31 pm

I just looked around a bit...
That error is around and unfixed since ( at least ) three years??

https://bb.oolite.space/viewtopic.ph ... highlight=

Post by **another_commander** » Sat May 15, 2010 1:35 pm

Yes. As I said, it is not critical and therefore low priority.

Yrol_Denjeah · Post by **Yrol_Denjeah** » Sat May 15, 2010 1:40 pm

Sorry. i am just surprised that there never was a time to fix that.

JensAyton · Post by **JensAyton** » Sat May 15, 2010 1:44 pm

The error doesn’t occur for me, and no-one else could be bothered to narrow it down. :-)