Difference between revisions of "Talk:Is-iff"
(Is-Iff used in FS1) |
Goober5000 (talk | contribs) |
||
| Line 6: | Line 6: | ||
I remember playing a mission in FS1 that used is-iff and there were no problems. - [[User:Supernova|Supernova]] 11:26, 1 August 2007 (EST) | I remember playing a mission in FS1 that used is-iff and there were no problems. - [[User:Supernova|Supernova]] 11:26, 1 August 2007 (EST) | ||
| + | |||
| + | I remember that is-iff crashed every single time I used it, in both FS1 and FS2. It's been fixed in FSO, but we never found the original cause of it. We just ended up rewriting it. [[User:Goober5000|Goober5000]] 20:56, 7 August 2007 (CDT) | ||
Latest revision as of 01:56, 8 August 2007
The retail version of this SEXP doesn't work, period. Running a mission with an is-iff call will crash retail FS2 every time. -- BlueFlames 16:46, 31 July 2007 (CDT)
Works for me. Just made a test mission in retail FRED2, using is-iff, and played it no problems in retail FS2. Are you sure you didn't make your test mission in Fred2_open instead of retail FRED? Shade 17:01, 31 July 2007 (CDT)
Last time I tested it, there wasn't a FRED2_Open to get confused with. Since then, I've been in the habit of checking if an event to change a ship's IFF had come true, instead of directly checking the ship's IFF. Anyway, it could just be a bug in a specific usage of is-iff that I thought was a general bug with the operator. -- BlueFlames 18:23, 31 July 2007 (CDT)
I remember playing a mission in FS1 that used is-iff and there were no problems. - Supernova 11:26, 1 August 2007 (EST)
I remember that is-iff crashed every single time I used it, in both FS1 and FS2. It's been fixed in FSO, but we never found the original cause of it. We just ended up rewriting it. Goober5000 20:56, 7 August 2007 (CDT)
