Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: 0rph3u5 on April 28, 2016, 12:25:41 pm

Title: Light of Antares - CTD
Post by: 0rph3u5 on April 28, 2016, 12:25:41 pm: Having a CTD when running Light of Antares, Mission 2 in its updated form, this bug is new and I don't know where it is coming from ...

Help is much appricated...

Error message:
Code: [Select]
Assert: vm_vec_mag(plane_normal) > 0.999f && vm_vec_mag(plane_normal) < 1.001f File: vecmat.cpp Line: 106 ntdll.dll! ZwWaitForSingleObject + 12 bytes KERNELBASE.dll! WaitForSingleObject + 18 bytes fs2_open_3_7_2-DEBUG.exe! SCP_DumpStack + 354 bytes fs2_open_3_7_2-DEBUG.exe! WinAssert + 194 bytes fs2_open_3_7_2-DEBUG.exe! vm_project_point_onto_plane + 104 bytes fs2_open_3_7_2-DEBUG.exe! fvi_sphere_plane + 371 bytes fs2_open_3_7_2-DEBUG.exe! mc_check_sphereline_face + 124 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp_poly + 622 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 178 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 236 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 208 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 236 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 208 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 236 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 236 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 208 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 236 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 236 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 208 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 208 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 236 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 236 bytes fs2_open_3_7_2-DEBUG.exe! model_collide_bsp + 236 bytes fs2_open_3_7_2-DEBUG.exe! mc_check_subobj + 915 bytes fs2_open_3_7_2-DEBUG.exe! model_collide + 1080 bytes fs2_open_3_7_2-DEBUG.exe! pp_collide + 195 bytes fs2_open_3_7_2-DEBUG.exe! create_model_path + 504 bytes fs2_open_3_7_2-DEBUG.exe! ai_find_path + 321 bytes fs2_open_3_7_2-DEBUG.exe! ai_acquire_depart_path + 548 bytes fs2_open_3_7_2-DEBUG.exe! mission_do_departure + 622 bytes fs2_open_3_7_2-DEBUG.exe! mission_eval_departures + 377 bytes fs2_open_3_7_2-DEBUG.exe! mission_parse_eval_stuff + 40 bytes fs2_open_3_7_2-DEBUG.exe! game_simulation_frame + 1060 bytes fs2_open_3_7_2-DEBUG.exe! game_frame + 497 bytes fs2_open_3_7_2-DEBUG.exe! game_do_frame + 239 bytes fs2_open_3_7_2-DEBUG.exe! game_do_state + 379 bytes fs2_open_3_7_2-DEBUG.exe! gameseq_process_events + 237 bytes fs2_open_3_7_2-DEBUG.exe! game_main + 782 bytes fs2_open_3_7_2-DEBUG.exe! WinMain + 330 bytes fs2_open_3_7_2-DEBUG.exe! __tmainCRTStartup + 358 bytes fs2_open_3_7_2-DEBUG.exe! WinMainCRTStartup + 15 bytes KERNEL32.DLL! BaseThreadInitThunk + 36 bytes ntdll.dll! RtlUnicodeStringToInteger + 595 bytes ntdll.dll! RtlUnicodeStringToInteger + 542 bytes
fs2_open.log attached

[attachment DELETED!! by Strong Bad]
Title: Re: Light of Antares - CTD
Post by: AdmiralRalwood on April 28, 2016, 12:59:10 pm: Quote
Code: [Select]
FreeSpace 2 Open version: 3.7.2.11329
...Um. Could you try it on a slightly more recent version?
Title: Re: Light of Antares - CTD
Post by: 0rph3u5 on April 28, 2016, 01:06:33 pm: Quote from: AdmiralRalwood on April 28, 2016, 12:59:10 pm
Quote
Code: [Select]
FreeSpace 2 Open version: 3.7.2.11329
...Um. Could you try it on a slightly more recent version?

This is my recommended build for re-release (because it is the most recent final build, so installation requirements don't get too overcomplicated)... if we get to a 3.7.4 Final in the next say 10 days, I would upgrade to that (for release purposes)

I will see what happens if I run in through a 3.7.4...
Title: Re: Light of Antares - CTD
Post by: 0rph3u5 on April 29, 2016, 06:53:46 am: Same thing with 3.7.4 RC1

Code: [Select]
Assert: vm_vec_mag(plane_normal) > 0.999f && vm_vec_mag(plane_normal) < 1.001f File: vecmat.cpp Line: 132 ntdll.dll! ZwWaitForSingleObject + 12 bytes KERNELBASE.dll! WaitForSingleObject + 18 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! SCP_DumpStack + 354 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! WinAssert + 194 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! vm_project_point_onto_plane + 124 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! fvi_sphere_plane + 359 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! mc_check_sphereline_face + 141 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp_poly + 648 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 185 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 243 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 215 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 243 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 215 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 243 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 243 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 215 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 243 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 243 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 215 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 215 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 243 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 243 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide_bsp + 243 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! mc_check_subobj + 1067 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! model_collide + 1147 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! pp_collide + 196 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! create_model_path + 512 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! ai_find_path + 318 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! ai_acquire_depart_path + 539 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! mission_do_departure + 612 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! mission_eval_departures + 404 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! mission_parse_eval_stuff + 40 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! game_simulation_frame + 1041 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! game_frame + 496 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! game_do_frame + 231 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! game_do_state + 403 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! gameseq_process_events + 232 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! game_main + 787 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! WinMain + 328 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! invoke_main + 30 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! __scrt_common_main_seh + 346 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! __scrt_common_main + 13 bytes fs2_open_3_7_4_RC1_SSE2-DEBUG.exe! WinMainCRTStartup + 8 bytes KERNEL32.DLL! BaseThreadInitThunk + 36 bytes ntdll.dll! RtlUnicodeStringToInteger + 595 bytes ntdll.dll! RtlUnicodeStringToInteger + 542 bytes

[attachment DELETED!! by Strong Bad]
Title: Re: Light of Antares - CTD
Post by: 0rph3u5 on May 10, 2016, 04:26:29 pm: Anything new here? I really want to have this in release'ish shape next before the end of the month
Title: Re: Light of Antares - CTD
Post by: niffiwan on May 10, 2016, 04:43:10 pm: Those sort of issue are hard to track down, probably need a stack trace and then info about the data in memory. Some vector which is supposed to be normalised is outside the acceptable bounds for normalisation (i.e. +/- .001 from 1.0). Not sure how or why that occurs.

Anyway; does it always occur in the same place in the mission? Fairly soon after starting and when "Ny 1" departs?
Title: Re: Light of Antares - CTD
Post by: 0rph3u5 on May 12, 2016, 03:43:09 am: Quote from: niffiwan on May 10, 2016, 04:43:10 pm
does it always occur in the same place in the mission? Fairly soon after starting and when "Ny 1" departs?

When one of the "ambient civilians" (which include Ny 1; the ambiert civilians are groups of Satis, Ma'at and Bast-Freighters) arrives - they are all on randomized arrival cues (which I am going to re-work on the weekend, to fix a bug with the randomisation as they are not supposed to arrive while hostiles are around)
Title: Re: Light of Antares - CTD
Post by: niffiwan on May 12, 2016, 06:06:43 am: hmm.... so I used the stack trace above to do a bit of hunting; and I'm going to guess it could possibly be a model issue? I think the Assertion is being triggered when processing a collision with a models BSP tree; I guess the other option is there could be a bug which is putting bad data into the BSP tree (although I'd think that's less likely).

Anyway; could you maybe see if it's one of those three models that's always triggering the issue?

Lastly, and perhaps small comfort, this issue won't trigger in a release build... whether that's just masking a problem or harmless depends on exactly what the problem is... (that wasn't very helpful was it)