[Akalabeth Angel]

I changed a weapon on a small ship to a AAAf beam, and it worked the first few times I test the mission but now it just fires the same ol plink gun that it comes with standard even though it still shows AAAf in fred. What gives?

[Blitzerland]

Possible Issues.

1.) Testing wrong version of mission. Absurd? Possibly, but perhaps you accidently saved the newer version to the wrong location? If so, just overwrite the old one with it.

2.) Again, possibly absurd, but ensure you're looking at the right turret. I wouldn't be surprised if you're looking at the wrong side of the ship.

3.) Your CPU has turned on you. I suspect rabies.

[WMCoolmon]

Make sure the ship can mount the gun too. That might cause problems.

[Akalabeth Angel]

Uh, I've only got one version of the mission plus the accompanying back up so it shouldn't be a problem.

The ship only has one turret, so I'm pretty sure its the right one

As for the ship mounting the gun, well it worked the first time, I'm not sure why it shouldn't work the second.

[Akalabeth Angel]

I slapped a Flak Cannon and a Kayser in place of the Subach HL-7 on the turret, and NEITHER of those worked either. I don't know wtf is wrong with it. Erg

[Cobra]

FRED vanilla or FRED_Open?

[Akalabeth Angel]

vanilla
And the ship in question is an Elysium transport.

[Cobra]

yeah, it's probably vanilla playing tricks on you.

[WMCoolmon]

Try Goober's most recent build of FRED2_Open.

[Akalabeth Angel]

Computer not good enough for Open.
And I'm not going to upgrade.

But has anyone else had this problem?

[Cobra]

nope.

[StratComm]

I don't know how secure you feel with FS missions, but you may try opening the mission in question in Notepad and make sure that the turret in question does, in fact, have the weapon changed.  Open the mission with notepad, find the entry for the Elysium in question, check the turret, and make sure it has "+Primary Banks: ( "AAAf" )" or whatever after the turret subsystem declaration.  If it does, then it's FS that's acting up.  If not, it's FRED.  But that should be the first thing you should check, just to make sure you do, in fact, have it in there correct.

Also, some other general things:

• I know you say you've only got one copy of the mission, but make absolutely sure that you don't have another copy lying around in root that could be causing it to not work properly.  You wouldn't believe how much time I've wasted trying to debug something because of this or similar errors.
• Assuming you're running FSO, you're NOT using -mod, right?  There's a possibility that there is a weapons table override in a -mod directory that's taking the AAAf away, and that said table is causing the turret to default to its standard weapon.  Missions from below the current Mod level are displayed as well as those in a Mod directory, so you may be running with that on and not even realize it.
• For that matter, make sure you don't have any weapon.tbl entries lying around in general.  Though if FRED sees it, that's not likely to be the case.

Originally posted by Cobra
nope.

Generally not helpful.

[Akalabeth Angel]

Hmmn, it says AAAf in the wordpad too. I think I'm just going to scrap it from my mission anyway as it wasn't all that critical.

[StratComm]

Yeah I didn't think it was in FRED.  You're running this through retail FS2?

[Akalabeth Angel]

Yup, retail FS2. Though, it's interesting to note I changed the elysiums to Isis transports, and then the AAAf worked fine on those. Who knows.

[Cobra]

Originally posted by StratComm
Generally not helpful.

if goob replied to this thread, he'd probably say it's a vanilla problem that was fixed in SCP...

[StratComm]

But if Goob said that, he'd be informing us of a fix and explaining why it doesn't work.  Much different than saying "nope".


Akalabeth Angel, have you made any table modifications at all?  Or are you running with the stock tables?  Because this really sounds like a table glitch more than anything else.

So if changing them works, (and this is truly random) do they work if you change them back to Elysiums?

[Akalabeth Angel]

Well if no one else has had the problem, how could it be fixed in FS Open? Someone needs to know about it before they can fix it. Or are the SCP coders inspired through some divine force to fix the malevolent unseen forces known as bugs who dwell amongst the code waiting to pounce on some hapless FREDer?

[Akalabeth Angel]

Originally posted by StratComm
But if Goob said that, he'd be informing us of a fix and explaining why it doesn't work.  Much different than saying "nope".


Akalabeth Angel, have you made any table modifications at all?  Or are you running with the stock tables?  Because this really sounds like a table glitch more than anything else.

So if changing them works, (and this is truly random) do they work if you change them back to Elysiums?

       Yeah I'm using Table mods. Weapon table has I think two new entries, the ship table has quite a few more and the entire thing has been re-arranged alphabetically and by class. Changing them back to Elysiums causes them to be pieces of crap again. So maybe its a problem with the Elysium itself, I dunno.

[WMCoolmon]

Does it still have the problem if you modify the ship in ships.tbl, or use the newest builds available (Goober or mine)? There was some code I modified that looked like it was always using the ship class's turret info rather than the specific ship in the mission.