Author Topic: Nebula problems and problems with "A Flaming Sword"  (Read 1465 times)

0 Members and 1 Guest are viewing this topic.

Nebula problems and problems with "A Flaming Sword"
Okay, I do have some issues with the nebula graphics in SCP.  The screen flashes each time each "fog" passes by.  Once I check "stops fog intersect hull", it is just a mist more than a fog.  That is livable until you can fix this.

But what's bugging me right now is "A Flaming Sword".  You are supposed to lure the Shivan Astaroth Fighters to the GVCv Renenet.  I do lure them, but the "Engage Hostiles" directive never gets completed.  This then leads to an incomplete secondary objective ("Keep the Shivans away from First Meson Bomb"), which then nets me a scolding by Command afterwards (for not protecting the first transport).

Any ideas?

 

Offline Goober5000

  • HLP Loremaster
  • Moderator
  • 214
    • Goober5000 Productions
Nebula problems and problems with "A Flaming Sword"
It's due to the cumulative effect of several modifications to the AI that we're trying to roll back.  It makes the mission (and subsequent missions - especially Dunkerque) much harder than they should be.

If you annoy one of the fighters enough, it'll follow you back to the Renenet.  Wait until it's in range and the directive is complete before shooting it down.  Your wingmen will get slaughtered, but you can call in reinforcements afterward.

 

Offline Kosh

  • A year behind what's funny
  • 210
Nebula problems and problems with "A Flaming Sword"
I also had a problem with "A Flaming Sword". The Renenet would do absolutly nothing to defend itself until all of my wingmen die.
"The reason for this is that the original Fortran got so convoluted and extensive (10's of millions of lines of code) that no-one can actually figure out how it works, there's a massive project going on to decode the original Fortran and write a more modern system, but until then, the UK communication network is actually relying heavily on 35 year old Fortran that nobody understands." - Flipside

Brain I/O error
Replace and press any key

 

Offline Lightspeed

  • Light Years Ahead
  • 212
Nebula problems and problems with "A Flaming Sword"
I played through the main campaign a few months ago and can confirm it's beatable at hard difficulty.
Modern man is the missing link between ape and human being.

 

Offline magatsu1

  • 210
Nebula problems and problems with "A Flaming Sword"
Tell your wingmates to guard the Renenet while you lure the hostiles to it. Works for Feint!Parry!Repoiste! too.
Blitzerland: Knows what he's talkin' about

 

Offline Kosh

  • A year behind what's funny
  • 210
Nebula problems and problems with "A Flaming Sword"
Quote
Originally posted by magatsu1
Tell your wingmates to guard the Renenet while you lure the hostiles to it. Works for Feint!Parry!Repoiste! too.




I did. The Renenet would still not shoot its laser turrets, beam guns or even flak guns at the fighters. Despite the fact that it was taking some damage. My wingmen all died. I was able to beat the mission, but it wasn't until the second wave of Shivan fighters came that the Renenet did something other than be a target practice backstop.



EDIT: I just remembered that I had the same problems under retail FS2. I'm pretty sure it is the mission.
"The reason for this is that the original Fortran got so convoluted and extensive (10's of millions of lines of code) that no-one can actually figure out how it works, there's a massive project going on to decode the original Fortran and write a more modern system, but until then, the UK communication network is actually relying heavily on 35 year old Fortran that nobody understands." - Flipside

Brain I/O error
Replace and press any key

 

Offline magatsu1

  • 210
Nebula problems and problems with "A Flaming Sword"
Friendly ships are initially orered not to engage, IIRC.
Blitzerland: Knows what he's talkin' about

 

Offline Kosh

  • A year behind what's funny
  • 210
Nebula problems and problems with "A Flaming Sword"
Well they shouldn't let my wingmen be slaughtered like that. :p
"The reason for this is that the original Fortran got so convoluted and extensive (10's of millions of lines of code) that no-one can actually figure out how it works, there's a massive project going on to decode the original Fortran and write a more modern system, but until then, the UK communication network is actually relying heavily on 35 year old Fortran that nobody understands." - Flipside

Brain I/O error
Replace and press any key