[Bryan See]

Upon flying any mission on debug builds on FSO, there's an assertion saying that the invalid bitmap handle -1 passed to the function possibly due to an invalid animation somewhere else. However, it did not specify on what's the cause among the files of the modpack, nor the code itself.

Code: [Select]

Assert: "bm_bitmaps[bitmapnum].handle == handle"
File: bmpman.cpp
Line: 857
Invalid bitmap handle -1 passed to bm_get_info().
This might be due to an invalid animation somewhere else.


ntdll.dll! ZwWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 159 bytes
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 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 + 159 bytes
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170710_3035a86_x64_SSE2-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes

I don't know whether anyone besides me having this kind of error. Here is the attached log.

[attachment stolen by Russian hackers]

[m!m]

Your modpack has a lot of warnings, some of which originate from the HUD code which tells you that bitmaps could not be loaded. Fix those issues first, that's a likely cause for your issue.

Generally, if you see a warning then you should fix it immediately since assertion failures or errors are likely to be caused by ignoring them.

[The E]

And specifically, you, Bryan See, must fix these issues. We cannot help you until you do, because chances are very good that the issues you're experiencing are your own fault.

[Bryan See]

OK, but is there anything can do to identify what's the cause? If that's the case, I'm doing to fix that right now. Thanks for the info.

[The E]

Read the log. Look at the warnings. Fix them. It's not hard, just a lot of work.

[Bryan See]

I did. And it worked. Thanks!