Author Topic: [Re-release] Light of Antares, 2019 Update  (Read 5514 times)

0 Members and 1 Guest are viewing this topic.

Offline 0rph3u5

  • 211
  • I want to be here less...
    • Steam
    • Twitter
[Re-release] Light of Antares, 2019 Update


Antares, the great battlefield of Terran-Vasudan War, was changed by the arrival of Shivans; allegiances shifted and alliances were struck.
Passing through the system on their way to Ribos appeared to be an easy task for the pilots and crew of the GTD Myrmidon, however in the attempt to do so they became locked into a life-and-death struggle with a group of Hammer of Light-fanatics.

-link removed-

Note: This release will eventually folded into a Memories of the Great War-"omnibus" release.









Summary of changes since the 2007 release:
- Overhauled Mission 3, mostly so the Shivans don't dominate the field as much.
- Overhauled Mission 4, so the mission is less likely to fail completely in the final minutes.
- Overhauled the end of Mission 5.
- Added a new Epilogue.
- Added a number of helpful counters to the directives in regards to time sensitive objectives.
- Upgraded the campaign persistence features for the cruisers "Priest", "Illuminated", "Ravana", "Kumbhakarna", "Damocles", "Deadalus" and "Icarus". If they are not destroyed in Mission 3, or Mission 4 respectively, they will be in Mission 5.

Hidden Text: Development history • Show
Light of Antares (sometimes with the added article) was originally created and released in 2007 - during the glorious months in between my graduation from secondary school and my year of military service. It is one of those campaign that are quickly slapped together in a fit of creative mania. Over the years I have been planning to re-release it several times, each time accompanied with a new beta-testing phase. As the script for Vega must burn is still "out at the editor", I took some time away and finally done everything but a total overhaul of the mission dialogue.

Back then its premiere feature was that I got into my head to design the mission around the "All Teams at War-flag" meaning combat between multiple forces in the same mission. Up until that point, no other campaign had done so, as far as I knew/know.

Silent Threat: Reborn was also still a year away at that point, so the field for FS1-era campaigns seemed very much open.

CREDITS:

Based on Conflict: Freespace by :v:

Uses the Freespace Port

Scenario/Mission Design - Jan ''0rph3u5'' Dombert

Beta Testers:
2007 release:
- "Macfie"
- "Trashman"
2009 update candidate:
- "Rodo"
- "Solatar"
2016 update candidate:
- "Taranis"
- "Lykurgos88"

Hammer of Light-reskins:
- Hammer of Light-logo - remastered by "Galemp" and "MjnMixael"
- PVF Anubis – by “Kestrellius” & Jan ''0rph3u5'' Dombert
- PVF Horus – by “Kestrellius” & Jan ''0rph3u5'' Dombert
- PVF Seth – by “Kestrellius”
- PVF Toth – by “Kestrellius”
- PVB Osiris – by “Kestrellius”
- PVB Amun – by “Kestrellius”
- PVS Scarab – by “Kestrellius”
- PVC Aten – by “Galemp”
- PVD Typhon – by “Galemp”

The "core"-package also contains:
- PVFg Cleopatra aka PVM Naunet – by “Axem”, with textures by “Black Wolf”
- PVCa Ramses aka PVCa Bastet – by “Black Wolf”
- GTF Hercules, Recon-variant – by “Galemp”
- PVM Duat - by "Oddgrim"

The campaign also comes bundeled with Axem's Message Box-script as an optional package.
(Note: the packages "Message Box-Script" and "Message Box-Script+small HUD" are mutually exclusive)

Hidden Text: continuity • Show
With regards to continuity:
- Light of Antares keeps close contunity with Rain on Ribos IV (originally released in 2007; updated release TBD) and the upcoming Vega must burn, as well as another project currently in my back pocket.

Hidden Text: Beta Videos • Show


Version History:
1.0.0 - Released on May 14, 2019 - Release version
1.0.1 - Released on June 27, 2019 - table clean-up
« Last Edit: January 09, 2021, 06:57:46 am by 0rph3u5 »
"When you work with water, you have to know and respect it. When you labour to subdue it, you have to understand that one day it may rise up and turn all your labours into nothing. For what is water, which seeks to make all things level, which has no taste or colour of its own, but a liquid form of Nothing?" - Graham Swift, Waterland

==================

"I am Curiosity, and I've always wondered what would become of you, here at the end of the world." - The Guide/The Curious Other, Othercide

"As you sought to steal a kingdom for yourself, so must you do again, a thousand times over. For a theft, a true theft, must be practiced to be earned." - The terms of Nyrissa's curse, Pathfinder: Kingmaker

"...because they are not Dragons."

 
Re: [Re-release] Light of Antares, 2019 Update
Note: This release will eventually folded into a Memories of the Great War-"omnibus" release.

Would you reccomend playing this now or after this is released?

 

Offline PIe

  • 28
  • GTVA POLICE
    • freespace3.com
Re: [Re-release] Light of Antares, 2019 Update
Not to detract from your work but "memories "is misspelled in the banner image.  Congrats on the release.
[6:23 PM] PIe: why do I have the feeling that I shouldn't be able to give orders to 22nd armored hq
[6:24 PM] Axem: 22nd armored hq, i order you to get me a cup of coffee
[6:24 PM] PIe: and donuts
[6:24 PM] PIe: BECAUSE THIS IS THE GTVA POLICE
[6:25 PM] Axem: :O
[6:25 PM] Axem: am i under arrest
[6:26 PM] [`_`]/: no, just please step out of the myrmidon
[6:26 PM] [`_`]/: you have so much to fred for

[9:50 PM] Sottises: wait did you do vassago's verge?
[9:50 PM] Sottises: .. dirge?
[9:50 PM] Axem: yes
[9:50 PM] Sottises: ohh
[9:50 PM] Sottises: well I have that and JAD too
[9:50 PM] Axem: :)
[9:50 PM] Sottises: what a contrast of themes lmao
[9:50 PM] Axem: isnt it
[9:51 PM] Axem: super grimdark thriller about unknowable alien intelligence and over the top colorful action about friendship
[9:51 PM] PIe: jad is grimdark???
[9:51 PM] Axem: :skull:

 

Offline AdDur

  • 25
Re: [Re-release] Light of Antares, 2019 Update
OK, just played it. Short, yet fun to play campaign. I like campaigns set between well known events. Missions are rather simple, but I don't regret time spent with Light. I'm impatently waiting for rest of Memories re-release. I really liked the confusing battles of this campaign with three sides - using shivans as an asset that may every moment kill you was interesting experience.

In mission 2... Shouldn't Myrmidon start a bit damaged? I mean, it's mentioned in briefing that it sustained some damage during the run for Ribos node. Minor damage like havin only 90-80% of hull damage would be fitting, I think.

I'm also not sure if Phoenix V existed at the moment the campaign is set, but it's a minor detail and i might (and probably am) wrong.

Sometimes I had a feeling of... emptiness. I mean missions 2 and 4 could use some more dialogues between wingmen (maybe about unexpected "ally"), maybe some HoL boasting (like mission later)? Especially mission 4, where for most time you just snipe enemies with your interceptors. It was nice, relaxing mission, but i felt a lack of something.

I actually managed to... break last mission. By hiding in Temple hangar it is possible to destroy it even before the beacons start to jump in - especially that some fighters kept trying to attack me, and therefore haven't attacked Myrmidon battlegroup, just floating around the destroyer. Mission ended normally, but still with debriefing about heavy damage to Myrmidon... which went trough battle without a scratch.

 

Offline 0rph3u5

  • 211
  • I want to be here less...
    • Steam
    • Twitter
Re: [Re-release] Light of Antares, 2019 Update
Not to detract from your work but "memories "is misspelled in the banner image.

Exhausting makes a bad companion. The banner in Knossos itself should be fixed.

Note: This release will eventually folded into a Memories of the Great War-"omnibus" release.

Would you reccomend playing this now or after this is released?

Now. The omnibus release doesn't even have a vague release date - heck, if I had not promised Galemp the maps for the Horus and Anubis, this might have lingered on my harddrive a lot longer.



I'm also not sure if Phoenix V existed at the moment the campaign is set, but it's a minor detail and i might (and probably am) wrong.

Canonwise: The Phoenix V gets introduced to player in Freespace 1 during Act 2, I think for La Ruota dell Fortuna or Where Eagles Dare. Which would be two weeks after these events.

However it is here to give you a little firepower for mission 3 and mission 5 - you don't see it but LoA uses a variation of the P5 that tells the AI to use it specificially against ships that are cruisers and larger, instead of bombers.



In mission 2... Shouldn't Myrmidon start a bit damaged? I mean, it's mentioned in briefing that it sustained some damage during the run for Ribos node. Minor damage like havin only 90-80% of hull damage would be fitting, I think.

Which build are you using? - Because it was transfering the hull value of the Myrmidon from mission 1 to mission 2 in the 2007 original and I didn't change a thing about that.

I actually managed to... break last mission. By hiding in Temple hangar it is possible to destroy it even before the beacons start to jump in - especially that some fighters kept trying to attack me, and therefore haven't attacked Myrmidon battlegroup, just floating around the destroyer. Mission ended normally, but still with debriefing about heavy damage to Myrmidon... which went trough battle without a scratch.

Don't tell them about the exploit. ;)

As for the heavy damage, for sake of continuity it is assumed that the mission keeps going even after the Temple is destroyed.
Spoiler:
Two wings of Nephilims will warp in, flanking the Myrmidon, they can unleash a serious barrage on the destroyer if you are not good enough.
« Last Edit: May 01, 2019, 03:32:32 am by 0rph3u5 »
"When you work with water, you have to know and respect it. When you labour to subdue it, you have to understand that one day it may rise up and turn all your labours into nothing. For what is water, which seeks to make all things level, which has no taste or colour of its own, but a liquid form of Nothing?" - Graham Swift, Waterland

==================

"I am Curiosity, and I've always wondered what would become of you, here at the end of the world." - The Guide/The Curious Other, Othercide

"As you sought to steal a kingdom for yourself, so must you do again, a thousand times over. For a theft, a true theft, must be practiced to be earned." - The terms of Nyrissa's curse, Pathfinder: Kingmaker

"...because they are not Dragons."

 

Offline AdDur

  • 25
Re: [Re-release] Light of Antares, 2019 Update
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.

 
Re: [Re-release] Light of Antares, 2019 Update
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
« Last Edit: May 03, 2019, 04:04:12 am by woutersmits »

 
Re: [Re-release] Light of Antares, 2019 Update
Probably you should've use a nightly build instead of 3.8.0?

 
Re: [Re-release] Light of Antares, 2019 Update
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

 

Offline 0rph3u5

  • 211
  • I want to be here less...
    • Steam
    • Twitter
Re: [Re-release] Light of Antares, 2019 Update
Error: Error parsing sexp variables - unknown persistence type encountered.  You can continue from here without trouble.

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.
« Last Edit: May 03, 2019, 05:49:34 am by 0rph3u5 »
"When you work with water, you have to know and respect it. When you labour to subdue it, you have to understand that one day it may rise up and turn all your labours into nothing. For what is water, which seeks to make all things level, which has no taste or colour of its own, but a liquid form of Nothing?" - Graham Swift, Waterland

==================

"I am Curiosity, and I've always wondered what would become of you, here at the end of the world." - The Guide/The Curious Other, Othercide

"As you sought to steal a kingdom for yourself, so must you do again, a thousand times over. For a theft, a true theft, must be practiced to be earned." - The terms of Nyrissa's curse, Pathfinder: Kingmaker

"...because they are not Dragons."

 
Re: [Re-release] Light of Antares, 2019 Update
are you sure you tested probely it just crashes

 
Re: [Re-release] Light of Antares, 2019 Update
At which mission does it actually occur?

 
Re: [Re-release] Light of Antares, 2019 Update
second

 
Re: [Re-release] Light of Antares, 2019 Update
https://fsnebula.org/log/5cd547a0cb0d3341c5a14604
keep getting errors
crashes
Assert: "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_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_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_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20190415_4824428_x64_SSE2-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes
asame errors are you sure you tested good
https://fsnebula.org/log/5cd54aefcb0d3341c0a14604
« Last Edit: May 10, 2019, 04:57:26 am by woutersmits »

 

Offline 0rph3u5

  • 211
  • I want to be here less...
    • Steam
    • Twitter
Re: [Re-release] Light of Antares, 2019 Update
keep getting errors
crashes
[...]
asame errors are you sure you tested good


Pretty sure - that Beta-level mission 99% identical to the release version (the 1% is the adding Debriefing text)

... and it is still the same error - one, which I might add, have not been able to replicate yet. I can see where it supposed to happen in the log (it's around 2:30+ in the video), but no crash on my end.
« Last Edit: May 10, 2019, 05:35:32 am by 0rph3u5 »
"When you work with water, you have to know and respect it. When you labour to subdue it, you have to understand that one day it may rise up and turn all your labours into nothing. For what is water, which seeks to make all things level, which has no taste or colour of its own, but a liquid form of Nothing?" - Graham Swift, Waterland

==================

"I am Curiosity, and I've always wondered what would become of you, here at the end of the world." - The Guide/The Curious Other, Othercide

"As you sought to steal a kingdom for yourself, so must you do again, a thousand times over. For a theft, a true theft, must be practiced to be earned." - The terms of Nyrissa's curse, Pathfinder: Kingmaker

"...because they are not Dragons."

 

Online Goober5000

  • HLP Loremaster
  • 214
    • Goober5000 Productions
Re: [Re-release] Light of Antares, 2019 Update
Woutersmits and I did some debugging.  I believe there is a problem with the PVI Karnak model, caused by invalid model geometry, that shows up in rare cases... which somehow Woutersmits was hitting on every playthrough.

The problem occurs when testing for collisions between Theta 2 and the Luxor.  The collision happens when testing the Karnak's submodel 0, leaf_index 4516.  The magnitude of the plane normal is 0.998625040, which is not quite 0.999.  Here is the full debug stack trace...

Code: [Select]
Assert: "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_x64_AVX2-DEBUG.exe! SCP_DumpStack + 367 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! dump_stacktrace + 68 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! os::dialogs::AssertMessage + 628 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! vm_project_point_onto_plane + 118 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! fvi_sphere_plane + 420 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! mc_check_sphereline_face + 195 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp_poly + 829 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 230 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 264 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 264 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 264 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 264 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! mc_check_subobj + 1224 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide + 1158 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 + 162 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! SCP_DumpStack + 367 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! dump_stacktrace + 68 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! os::dialogs::Error + 250 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! os::dialogs::AssertMessage + 854 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! vm_project_point_onto_plane + 118 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! fvi_sphere_plane + 420 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! mc_check_sphereline_face + 195 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp_poly + 829 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 230 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 264 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 264 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 264 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 296 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide_bsp + 264 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! mc_check_subobj + 1224 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! model_collide + 1158 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! will_collide_pp + 268 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! will_collide_with_big_ship + 290 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! will_collide_with_big_ship_all + 278 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! maybe_avoid_big_ship + 139 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! ai_chase + 2481 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! ai_execute_behavior + 98 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! ai_frame + 2602 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! ai_process + 435 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! ship_process_post + 2356 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! obj_move_all_post + 883 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! obj_move_all + 933 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! game_simulation_frame + 1467 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! game_frame + 627 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! game_do_frame + 183 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! game_do_state + 348 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! gameseq_process_events + 265 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! game_main + 659 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! actual_main + 162 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! SDL_main + 47 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! main_getcmdline + 320 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! invoke_main + 50 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! __scrt_common_main_seh + 302 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! __scrt_common_main + 14 bytes
fs2_open_3_8_1_x64_AVX2-DEBUG.exe! WinMainCRTStartup + 9 bytes
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes

I can split the bug report out from the campaign thread if you like.

 

Offline 0rph3u5

  • 211
  • I want to be here less...
    • Steam
    • Twitter
Re: [Re-release] Light of Antares, 2019 Update
Thanks for doing the heavy lifting!  :yes:

On the subject of a topic split:
While it is not a problem unique to the campaign (e.g. I experienced a CTD on ST:R's "Blood of the Innocent" recently, which, in light of the explaination, might be the same issue) it is also a relevant issue until the FSPort MediaVPs recieve an update. So a split is not required.
"When you work with water, you have to know and respect it. When you labour to subdue it, you have to understand that one day it may rise up and turn all your labours into nothing. For what is water, which seeks to make all things level, which has no taste or colour of its own, but a liquid form of Nothing?" - Graham Swift, Waterland

==================

"I am Curiosity, and I've always wondered what would become of you, here at the end of the world." - The Guide/The Curious Other, Othercide

"As you sought to steal a kingdom for yourself, so must you do again, a thousand times over. For a theft, a true theft, must be practiced to be earned." - The terms of Nyrissa's curse, Pathfinder: Kingmaker

"...because they are not Dragons."

 

Offline Galemp

  • Actual father of Samus
  • 212
  • Current projects: GVCa Tanen, Vasudan Imperium
    • Steam
    • User page on the FreeSpace Wiki
Re: [Re-release] Light of Antares, 2019 Update
Hi. The Karnak is my model, and I'll take a look at this. It probably just needs an export, re-smoothing and normalizing, then reimported. Gimme a few days or weeks and I'll have a new POF for you to test.
"Anyone can do any amount of work, provided it isn't the work he's supposed to be doing at that moment." -- Robert Benchley

Members I've personally met: RedStreblo, Goober5000, Sandwich, Splinter, Su-tehp, Hippo, CP5670, Terran Emperor, Karajorma, Dekker, McCall, Admiral Wolf, mxlm, RedSniper, Stealth, Black Wolf...

 
Re: [Re-release] Light of Antares, 2019 Update
Yes! It seems I'm a bit late, but I've also had this CTD issue with collisions with the Karnak.

 

Offline 0rph3u5

  • 211
  • I want to be here less...
    • Steam
    • Twitter
Re: [Re-release] Light of Antares, 2019 Update
Hi. The Karnak is my model, and I'll take a look at this. It probably just needs an export, re-smoothing and normalizing, then reimported. Gimme a few days or weeks and I'll have a new POF for you to test.

Thanks very much!

Meanwhile, I added the Beta-Videos from my youtube-channel to the first post, so people can look at them if they are struck by that bug and the campaign does not progress.
"When you work with water, you have to know and respect it. When you labour to subdue it, you have to understand that one day it may rise up and turn all your labours into nothing. For what is water, which seeks to make all things level, which has no taste or colour of its own, but a liquid form of Nothing?" - Graham Swift, Waterland

==================

"I am Curiosity, and I've always wondered what would become of you, here at the end of the world." - The Guide/The Curious Other, Othercide

"As you sought to steal a kingdom for yourself, so must you do again, a thousand times over. For a theft, a true theft, must be practiced to be earned." - The terms of Nyrissa's curse, Pathfinder: Kingmaker

"...because they are not Dragons."