Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: Question on July 27, 2006, 04:46:19 am
-
The fleet that warps in to attack the freighters have bugged AI or somehting. The beam canons NEVER fire.
It takes ages for them to kill the freighters with their normal turrets.
And its ridiculous watching the cain class cruiser rape a sobek, aeolus and that other corvette because their beam canons wont fire.
What is up with that?
-
Was this a once off or can you reproduce it again?
What version of FS2 or FS2_Open were you using?
-
It happens -every time-.
Im using the 1.9 version as here :
1.8 to 1.9a:
-------------
(24MB)
-Oxyshare: -See this if you have problems to locate the download link-
http://galeon.com/shivansps/oxyshare.JPG (http://galeon.com/shivansps/oxyshare.JPG)
-
Just confirmed it's occuring using the latest CVS so I can't suggest upgrading in any way.
I'll put it in Mantis for now and someone will look into it. Possibly me again but beams aren't my speciality.
-
Have those ships been beam-freed at all in that mission?
-
You mean in the original FS2? Cant recall, and either way its quite clearly a bug if it was.
One more thing, when one of the vasudan ships goes to critical, they will say they are evacuating non-essential personnel. But the "voice actor" potrait they are using is a terran one.
-
They will use beams, but not reliably. It does the exact same thing in retail.
-
I went through the entire mission 3 times and they never fired a single beam....
-
They never worked for me in Retail either, just took it as normal GTVA ineptitude.
-
This is odd. They are definitely beam free
$Formula: ( when
( has-time-elapsed 20 )
( beam-free-all "Colossus" )
( beam-free-all "Stalwart" )
( beam-free-all "Heket" )
( beam-free-all "Khepri" )
)
+Name: Allied Fleet Armed
+Repeat Count: 1
+Interval: 1
I'm pretty much mystified as to why they aren't firing. It seems odd that every single beam could have bad firing arcs and the Colossus definitely does uses it beams even though it is beam-freed in the same mission.
If this is the same behaviour as retail then I guess it's not a bug though.
-
Well, the Khepri arrives at t=20, the Heket at t=21, and the Stalwart at t=32. Beam-free-all doesn't work for ships that aren't in the mission. ;)
Theoretically the Khepri could fire beams, but perhaps the events are evaluated before the arrival cues. Thus, although they both happen "simultaneously", the beam-free-all would happen first.
-
Goober hit the nail on the head here. I remember actually going into FRED to check this out one time, and after simply changing the BFA cue, I had an Aeolus and a Sobek using the weapons that they should've been using to make the cruisers a lot more bearable in that mission.
-
Ah. That explains it. I'm so used to using all ships beam-free-all by default that I forgot to check the arrival times :)
I suspect this change was part of the giant mission-****age that took place when they disabled the Colossus to stop it wandering about all over the place. If you open the mission in FRED there are all kinds of ai-waypoints orders for the Colossus in that mission :)
-
That mission might even be too easy with all those beam enabled ships...
Sounds fun ;7
-
"nobody wants to play with me" -wandering colossus-
-
Seriously. Undisable the colossus in FRED and it wanders all over the place :)
-
Someone should make it so that the colossus wins, so we can watch it wander around.