[eiszo]

It appears to me that there are less guns to choose from when playing the FS2Open version( 3.6.7). In the exchange missions, flying with Vasudans Wings, I am limited in choosing guns. In the retail version I can choose the prometheus gun during that missions but not in de 3.6.7 version.
Is this a known bug or is something else going on?

[karajorma]

That's odd.

Are you playing the missions in the techroom or as part of the campaign? Are you making a like with like comparison (The weapons you get in the techroom aren't necessarily the same as the ones you would get when playing the campaign).

[redmenace]

create a new pilot maybe?

[eiszo]

I play the campaign. I know that in the retail version you get to choose the prometheus. I played that version last week.

[TopAce]

##--00--##

Sounds like a tabling problem to me. Any mods you are using?

[eiszo]

There are no mods installed. What is a tabling problem? English is not my native language.

[TopAce]

I don't know how I could explain it in a simple way.. I will let others do that for you.

Most of the guys here are better are explaining technical things.

[karajorma]

If he's not using mods it's unlikely to be a tabling problem. A bug in FS2_Open itself seems more likely. Still it's easy to check for table errors so lets start there

@Eiszo : Run the mission from the techroom and check if the loadout is the same as it was in the campaign. If so post again and tell me what weapons you have.

You may also want to try this procedure to check for rogue vp and table files.

Open up your Freespace2 folder and do a search for *.tbl. If you find anything change the name to *.tblDISABLED. That should remove any rogue tables you may have.

Second thing to check for is a rogue .vp file. The only files you should have are files starting with mv_ or the following files

# root_fs2.vp
# sparky_fs2.vp
# sparky_hi_fs2.vp
# stu_fs2.vp
# tango1_fs2.vp
# tango2_fs2.vp
# tango3_fs2.vp
# smarty_fs2.vp
# warble_fs2.vp

If you have anything else try disabling them in the same way as I mentioned above for tables.

If the tech room and the campaign room don't have the same weapons that makes it sound like a bug. Again I want to know which weapons you do have in which particular mission you are curently playing.,

[eiszo]

I checked upon *.tbl and all seems to be in order. The prometheus does show up in the weaponslist but there are no avaible. In the retailversion there are.

This is a small matter I know and like I said the 3.6.7 version runs so smooth in 1280&1024. I am just curious why it is this way.

[WMCoolmon]

Try making a new pilot, run fs2_open with the "-allslev" command line, and see if the mission does the same thing in the tech room.

Also, try clicking the 'reset loadout' button.

[eiszo]

I tried the resetbutton and it helped. Now I have 16 prometheus guns.
Thanks everybody for your help.

[karajorma]

Originally posted by eiszo
I am just curious why it is this way.

Me too. As it sounds like it could be a bug.

Glad you seem to have found a way round it. Tell us if it reoccurs though.

[eiszo]

I spoke to soon. The problem is back. Still no prometheus guns for my vasudan fighter.

[TopAce]

*worships the SCP*

[Kie99]

Originally posted by TopAce
*worships the SCP*

Very nice, but why this thread?

[karajorma]

No idea. Looks like spam to me.

Originally posted by eiszo
I spoke to soon. The problem is back. Still no prometheus guns for my vasudan fighter.

Tell me which mission you're on and I'll make you up a new campaign file that should solve the problems.

You could also try restarting the campaign but I don't know how annoying it would be for you to play through all the missions you've done so far.

[eiszo]

It is strange. Just now I started the FS campaign en there were the prometheus guns ( techroom). But this afternoon there were none. So sometimes they're there and the next time around...

Could it be that the loading proces is sometimes not completed?

The mission I was playing was speaking in tongues.

[Goober5000]

Originally posted by TopAce
*worships the SCP*

*smacks TopAce*

We can't even manage a proper code freeze so don't go worshipping us.

[Timerlane]

Interesting.

As of a day or so ago, I'd been having some minor issues with playing "Speaking in Tongues" in the Tech Room, myself. (I'm running the recent "White Squares" 3.6.7 build, and only the FSPort for mods.) I assumed I just did something I wasn't supposed to("broke" something, somehow).

I was most of the way through the campaign in my current pilot, and after installing the latest version, I thought I'd go to the Tech Room and play one of my old favorite missions, "Love the Treason..." (mostly as it's one of the few campaign missions you can use a Herc I on). I restarted it a couple of times(due to Snipes dying, or the Hamako getting eaten by flak), then exited from the mission(ESC menu). I then wanted to see if the nebula performance was improved on this version, so I went to the last mission I was up to in the Tech Room, which was "Speaking in Tongues".

Things seemed normal at first, but when I got to the Ship Selection screen, the inventory icons on the ship list were missing, and I had a Herc I for myself and Lokis for my Alpha wingmen, plus Beta Wing was all Herc IIs. When I went to the Loadout screen, I found a drastically limited selection of weapons, and I believe I  saw that I had the same default loadout set up as I'd had for "Love The Treason". I decided to play the mission regardless, and I completed it normally(albeit with my wings having the listed Terran fighters).

I loaded the mission again in the Tech Room, and found the same ship/loadout situation. I then checked my current campaign mission ship/loadout; everything was normal there, but "Speaking in Tongues" was still showing the odd ship/loadout setup. I tried playing "Love the Treason" all the way through(everything normal there, as well), to see if completing it might somehow cause the game to "unload" the apparent problem, but to no avail.

I tried restarting FSO to see if that cleared it. Nothing. By that point, I was tired of trying to fix the problem, and decided to just go play some more campaign missions and forget about it. I also ran a few other custom missions after that, which also ran normally.

Today, I decided to check "Speaking in Tongues" again to see if things were still off, and it appears the normal Vasudan ships and loadouts are back.

[Goober5000]

If you install or remove a mod partway through a campaign, the ships and weapons get all messed up.  This might have been what happened.