Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: SF-Junky on March 17, 2021, 02:06:10 pm

Title: Game crash: "Debris[objp->instance].is_hull"
Post by: SF-Junky on March 17, 2021, 02:06:10 pm
Game crashes and I get this error msg:

Code: [Select]
Assert: "Debris[objp->instance].is_hull"
File: beam.cpp
Line: 1949

ntdll.dll! ZwWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 142 bytes
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes

[ This info is in the clipboard so you can paste it somewhere now ]


Use Debug to break into Debugger, Exit will close the application.

ntdll.dll! ZwWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 142 bytes
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_21_1_0_20210313_649fe7e3c_x64_SSE2-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes

fs2_open.log and the .mdmp mentioned therein are attached.

I feel it's a problem with the Sathanas model? There is a Sathanas in the mission and if I get this right the game crashes when it attempts to fire a beam at an enemy warship while doing a turn. But I could be wrong.

And while we are still at it: what's with the "No XSTR entry in strings.tbl for index 1616" which is in there like a million times?

[attachment deleted to save space]
Title: Re: Game crash: "Debris[objp->instance].is_hull"
Post by: Asteroth on March 19, 2021, 06:49:08 pm
What mission is it? And it happens every time?
Title: Re: Game crash: "Debris[objp->instance].is_hull"
Post by: SF-Junky on March 20, 2021, 06:34:57 am
A mission in my mod. It happened the last couple of times I tried to play it.
Title: Re: Game crash: "Debris[objp->instance].is_hull"
Post by: Novachen on March 20, 2021, 09:12:25 am
And while we are still at it: what's with the "No XSTR entry in strings.tbl for index 1616" which is in there like a million times?

Well, as this is a language specific entry, i think it had to do with this:

Code: [Select]
Setting language to RETAIL HYBRID.

Please check your fs2_open.ini for the language entry and delete it or change it to English, German whatever.
This is an invalid language. No idea where this one is coming from.
But i think that could be the cause of this problem. As the game is looking for a language called Retail Hybrid.
Title: Re: Game crash: "Debris[objp->instance].is_hull"
Post by: Goober5000 on March 20, 2021, 08:48:15 pm
And while we are still at it: what's with the "No XSTR entry in strings.tbl for index 1616" which is in there like a million times?

Well, as this is a language specific entry, i think it had to do with this:

Code: [Select]
Setting language to RETAIL HYBRID.

Please check your fs2_open.ini for the language entry and delete it or change it to English, German whatever.
This is an invalid language. No idea where this one is coming from.
But i think that could be the cause of this problem. As the game is looking for a language called Retail Hybrid.

RETAIL HYBRID refers to the hybrid language mode that retail used: translating internal strings (in strings.tbl) but not translating external strings (in tstrings.tbl) when running in English.  For any language other than English, everything is always translated.

The "No XSTR entry in strings.tbl for index 1616" message is because there is an XSTR("Energy", 1616) in the game code but there is no corresponding entry in strings.tbl.
Title: Re: Game crash: "Debris[objp->instance].is_hull"
Post by: Asteroth on March 23, 2021, 12:00:57 am
A mission in my mod. It happened the last couple of times I tried to play it.
Is it compatible with retail? Or at least close to it? I'd like to see it, if possible. You can DM me if you'd prefer it not to be public. Alternatively, can you reproduce this crash using just a retail test mission?