Debug assert in Somewhere mission

[stgatilov]

I have debug assertion failed in mission "Somewhere Above The City" when I start new mission.

 

Of course this is self-made debug build of TDM. Asserts are wiped out of release version.

 

 

 

Seems like Grayman created rigid body with nonpositive mass?

[grayman]

TDM source code has numerous places where assertions fail with a Debug DLL. I don't know if the dev team has a history of eliminating them, but I myself haven't tried finding the root cause of any.

 

You can push through them by selecting "Ignore", which is what a Release DLL does, which is why they don't normally show up.

 

 

Btw, I make no specific mass settings in Somewhere, so what you're seeing isn't specific to that mission.

[grayman]

I researched this this morning and I have to humbly eat my words.

 

W/O giving anything away, there is a custom movable object in the mission whose mass I changed to zero at one point during development to keep it from being blown away under certain circumstances. By the time the mission was released, those circumstances were no longer possible, but I neglected to reset the mass to the custom setting of 0.6. Since it's only caught by an assertion with Debug DLL's, the problem never surfaced during normal gameplay.

 

Good catch, and I will keep this in mind for future missions. There's no need to release another version of SATC to fix this.