[Re-release] Light of Antares, Omnibus version (1.1.1)

FreeSpace Releases > Mission & Campaign Releases

<< < (2/9) > >>

AdDur:
Maybe then, as in case of Interceptor it would be nice to mention about introducing Phoenix, or getting shipment of it on Myrmidon?

Version 1.0.0 of Antares, with 3.8.0-3 FSO.

Yeah in my second proper playtrough i saw this nice strike... It was devastating.

woutersmits:
Error: Error parsing sexp variables - unknown persistence type encountered. You can continue from here without trouble.
File: sexp.cpp
Line: 3672

ntdll.dll! NtWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 162 bytes
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
fs2_open_3_8_0_x64_AVX.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes

i get this error
https://fsnebula.org/log/5ccbff72cb0d33530ac8bac2
with log
on every mission

Nightmare:
Probably you should've use a nightly build instead of 3.8.0?

woutersmits:
https://fsnebula.org/log/5ccc08bacb0d335300c8bab3Assert: "vm_vec_mag(plane_normal) > 0.999f && vm_vec_mag(plane_normal) < 1.001f"
File: vecmat.cpp
Line: 132

ntdll.dll! NtWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 162 bytes
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
[...]
[ 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 + 162 bytes
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190502_1da2c03_x64_SSE2-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes

bugged campaign
gives errors

0rph3u5:

--- Quote from: woutersmits on May 03, 2019, 03:46:00 am ---Error: Error parsing sexp variables - unknown persistence type encountered. You can continue from here without trouble.

--- End quote ---

That's one from using the a build that doesn't have the new persistence scheme - was not aware that it wasn't in complete build.

Solution use a Nightly 3.8.1 - they are easy enough to get on Knossos.

As for second one, no clue.

I can only guess that it has something to do with a ship arriving or a weapon being fired, but none of the ship types arriving or possibily arriving around, or the weapons that potentially be fired, that point in the mission are uncommon across campaigns (SF Scropion, SF Manticore, GTC Fenris, PVFr Bast, PVFr Satis, PVT Isis, PVFr Ma'at, VC 3, VAC 4, PVS Scarab) for that bug to exist "just here".

The second mission was known to create problems with older versions of the Freespace Port MediaVPs due to the differences between the original Karnak and previous versions of the HTL Karnak - but that was sync'ed aged ago. Light of Antares is specifically set to use the newest avalible MediaVPs (including Freespace Port MediaVPs) for that reason - also why there is no manual install package this time.

Another guess would be that it is an issue to unique to Nightly released on May 2nd - since it is newer than the campaign I have testing data on it. I used the Nightly released on April 15th for testing.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version