Hard Light Productions Forums

Hosted Projects - FS2 Required => Inferno => Topic started by: radarheaf on May 03, 2006, 11:50:17 am

Title: Help- Noob getting attacked by friendly cap ships....
Post by: radarheaf on May 03, 2006, 11:50:17 am
I have inferno R1 + the SCP patch, plus shadow fix on an open 3.6.7 install. If I target next enemy it targets friendly ships also, and when friendly cap ships are in the area the open fire on not only me and friendly fighters, but also on each other with their main beams.... They show as green friendly, not totally sure what the problem is. Any advice?
Title: Re: Help- Noob getting attacked by friendly cap ships....
Post by: Woomeister on May 03, 2006, 11:54:08 am
Try a more recent build. That one sounds really buggy.
Title: Re: Help- Noob getting attacked by friendly cap ships....
Post by: Qwer on May 03, 2006, 12:39:56 pm
Well i saw something like that on some FS Port FS1 missions, but really i don't know what could be this. :doubt:
Title: Re: Help- Noob getting attacked by friendly cap ships....
Post by: Shadow0000 on May 03, 2006, 09:46:35 pm
If you have my Update as you say, use a newer build as specified on the 1st post of the Topic/Thread of the Update.

This is cause due to a new IFF feature, where all the $Team: xxxxx (ex: Friendly/Hostile/Neutral/Unknown) were erased if you saved the Mission with a FRED2 build around those dates...also this was caused if the Flag "All Team at Wars" at Mission Specs was ON, however in the last version of my update this happens only at Mission 06 (the blockade against the Kismat and the Diablo), I can't really tell if that option was activated by mistake by me or if it was already in the INF + SCP Patch missions...

I have already fixed those bugs months ago, but I still don't have upload the fixed update...
Title: Re: Help- Noob getting attacked by friendly cap ships....
Post by: StratComm on May 13, 2006, 08:26:45 am
That bug was caused by a misunderstanding of what "all teams at war" actually did when the IFF overhaul was done.  It should be fixed at this point, so if you're still seeing it in a recent build then something else is probably wrong.