Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Kobnar on April 23, 2006, 03:01:59 pm
-
I was wondering if there is a way to unlock the next level or all levels so that I can skip what's left of this one...
The level I'm stuck on is the level where you use the prototype weapon the "TAG"..
everything goes fine until Virgo wing shows up, I waist them but then I still have "Distroy Virgo [4]" under my directives list and the level will not progress.
Oh and BTW I'm using Linux and building with the CVS.
thx.
-
This is a known bug. Virgo wing are out there somewhere but for some reason they don't fly in to attack the Warspite and so no one can find them easily in order to kill them.
-
Well I've actually enganged and destroyed virgo wing... I watched them die and the counter go down to 1 then once the last bomber was destroyed it jumped back up to 4.
-
That is due to virgo wing having two waves, and not a bug.
-
well I guess the question still stands... how can I skip the rest of this level?
-
Fail a mission enough times and you're allowed to skip it. Think it's 4.
Otherwise, I suppose you could create an empty mission in FRED, add a primary goal that becomes true after 10 seconds, then save it as SM2-02.fs2 and stick it in the data\missions folder. If I'm not mistaken, it should then override the mission in root_fs2.vp and let you continue the campaign after doing the "mission".
-
Unrar and dump this in your mediavps/Data/Missions folder (or Data/Missions if you don't have one).
Virgo wing should now have vague orders to head in the general direction of the Warspite.
Incidentally Virgo Wing have no orders to attack the Warspite or Lucidity. Instead the individual ships in Virgo wing have orders to do that. Has anyone altered anything recently that could make that a problem?
[attachment deleted by admin]
-
I think this could be related.. I had some time ago (until today infact) problems with different AI controlled wings.. Initial wave operated as it should but follow up waves operated in a bit odd way.. Only wing leaders acted and wingmen only followed the wingleader until the leader was killed and then 2nd ship started fighting etc. all the time only 1 ship per wave was actice and rest were just hanging around. I got it fixed by (removing invidual ship initial orders and) giving wing initial orders instead.
I thought it was just me with fred doing that... didnt really give any second thoughts about it.
EDIT: All with fairly recent cvs builds (from 20060327 to 20060421)
-
Unrar and dump this in your mediavps/Data/Missions folder (or Data/Missions if you don't have one).
Virgo wing should now have vague orders to head in the general direction of the Warspite.
I like a challenge and all, but don't you think making Cancer 1 invulnerable was a bit much? :D
-
I didn't alter cancer wing at all. If they are now invulnerable that's a FRED bug.
Yep. Definitely a FRED bug. I'll have to check if it's something I introduced or if it's older.
-
I thought it was a bit weird :) It's just Cancer 1 though, the other 3 are normal.
-
Recreated what I did and it did it again. Definitely a bug. Probably related to whatever is setting Alpha 1 as Targetable as bomb in every mission I make. I'll have to track this one down and see what caused it.
-
So should we download that file in the meantime or what ?
-
Updated to the working version. Sorry, forgot to do that earlier.
-
I'm having a similar problem with "A Game of TAG".
The bombers DO appear, but a while after I've destroyed them, I get a radio message telling
me a new wave whave jumped in, and the VIRGO [4] mission indicator goes back to "not completed"...
Any idea's on how to solve this?
-
Ummmm. I linked you to this thread cause there's a fixed version of the mission attached to my post :)
It should solve the problem for you.
-
Sorry :D.
-
Got it right this time :)
That fixed file worked like a charm!
Thanks mate! :)
-
Hi,
I'm stuck on this mission now - is the fix still available?
TIA
Guido :confused:
-
It's ok - flew towards the sun and found the little buggers!
Cheers
Guido
-
Best fix is to update to a newer version :) The problem should be gone in 3.6.9 RC4 and 5 at least.