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.
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]