[Bryan See]

Hello, I've been trying out nightly builds for more than three years.

However, upon loading my mission for a test on FSO's new particle system, it crashes. Apparently, there's an invalid index 0 in "index >= 0 && index < numHats()" at joy-sdl.cpp, line 445.

Attached is the fs2_open.log file.

EDIT: I think the Avast is the culprit, as it messed all of its executables and dll files, I've excluded it from its file system scan. But, is there a need to make it the AV think it's free of something bad (malware, backdoors, etc.).

EDIT #2: Still, it doesn't solve the problem.

Code: [Select]

Assert: "index >= 0 && index < numHats()"
File: joy-sdl.cpp
Line: 445
Invalid index 0!

ntdll.dll! NtWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 143 bytes
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_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! NtWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 143 bytes
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_7_5_20170120_5342853_x64_SSE2-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes

[attachment deleted by admin]

[m!m]

The E has found a fix for this and it has been merged. The next nightly should fix this issue.

[Bryan See]

The E has found a fix for this and it has been merged. The next nightly should fix this issue.

And when was it happened? And when the next nightly build released, fixing this persistent one?

[m!m]

The next nightly will be built tomorrow. Typically they appear around one day after the last build.

[Bryan See]

But I want that thing fixed by then. If not, we'll likely not be able to playtest missions with each new nightly build.

[m!m]

It has already been fixed. It will just take a while until the next nightly build will be released which contains the fix.

[Bryan See]

Okay, noted.

[Bryan See]

Downloaded the latest nightly build and run it. I was able to load a mission without any crash. Thanks a lot