Hello,
When I tried to switch to Weapons Loadout screen from Mission Briefing or Ship Selection after loading. I get this:
Error: Could not load in '2_weaponloadout-m'!
File: missionweaponchoice.cpp
Line: 2016
ntdll.dll! ZwWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 159 bytes
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170724_1743e5f_x64_SSE2-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes
I checked in the contents of the mod, and 2_weaponloadout-m is still in the Interface directory.
Enclosed here is the FS2_Open.log file.
I am developing a total-conversion mod, perhaps an original one, powered by the FSO engine.
EDIT: I thought three years ago that the weapons loadout screen is the root of all problems caused by FSO in the past.
[attachment stolen by Russian hackers]