Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: rstrube on April 03, 2007, 10:49:49 pm
-
Hello Everyone,
I did lots of research on these forums to see if anyone else has encountered problems with the mission entitled "A Game of Tag". I found lots of posts
mentioning an issue where the last Shivan bomber squadron doesn't appear. This problem was apparently fixed in an RC of 3.6.9 and is now surely fixed
in the official release of 3.6.9.
The problem I'm having is much more overt. I start the mission without any TAG missiles. Its been driving me bonkers! I found one other post complaining
of this problem - but no answer was provided.
Any help would greatly be appreciated. This problem exists with and without the media VP's being installed. I am running 3.6.9 on Mac OS X.
Robert
-
could be thet either the tables are messed up or that the mission loadout is.
Check the ship.tbl and see if the Ulysses has TAG's enabled as secondaries, and check weapons.tbl to see if hte TAG is in there.
If both of those are ok then it is probably the mission file itself - check the player loadout and team loadout.
-
Thanks for the reply.
I can't seem to find the .tbl files that you are mentioning. Below is a diagram of the freespace2 directory structure and the contained files that I have on my machine. I find it suspicious that the data/ directory is virtually empty. I have played through most of the single player campaign (up until the "A Game of Tag" mission) just fine.
~/Games/Freespace2
------------------ Root_fs2.vp
------------------ smarty_fs2.vp
------------------ sparky_fs2.vp
------------------ sparky_hi_fs2.vp
------------------ stu_fs2.vp
------------------ tango1_fs2.vp
------------------ tango2_fs2.vp
------------------ tango3_fs2.vp
------------------ tango3_fs2.vp
------------------ warble_fs2.vp
------------------ FS2_Open.app (version 3.6.9)
------------------ data/
------------------------ multi.cfg
------------------------ cbanims/ (empty)
------------------------ effects/ (empty)
------------------------ fonts/ (empty)
------------------------ force feedback/ (empty)
------------------------ freddocs/ (empty)
------------------------ hud/ (empty)
------------------------ intelanims/ (empty)
------------------------ interface/ (empty)
------------------------ maps/ (empty)
------------------------ missions/ (empty)
------------------------ models/ (empty)
------------------------ movies/ (10 items)
------------------------ multidata/ (empty)
------------------------ music/ (empty)
------------------------ players/
----------------------------- hud_1.hcf
----------------------------- hud_2.hcf
----------------------------- hud_3.hcf
----------------------------- images/ (empty)
----------------------------- multi/ (empty)
----------------------------- single/ (empty)
----------------------------- squads/ (empty)
------------------------- sounds/ (empty)
------------------------- tables/ (empty)
------------------------- voice/ (empty)
I also have some files in the directory
~/Library/FS2_Open
----------------- data/
--------------------- cache/
-------------------------- a bunch of *.ibx files
--------------------- mulit.log
--------------------- players/
-------------------------- multi/ (empty)
-------------------------- single/
------------------------------- my pilots
----------------------Tcp.cfg
---------------- fs2_open.ini
Please note: I did not include the media VP files in the directory listing. I have experimented with installing the following VP's: mv_core, mv_music, mv_models, mv_effects, mv_textures, and the patches. This does not make the problem go away.
And that about does it. Do the *.tbl files exist inside of *.vp files? I would glady edit them if I could find them.
Any help would be greatly appreciated.
Thanks,
Robert
-
Sounds like you screwed up your pilot to me, did you switch campaigns partway through the game?
-
Yep, I'd say "Create a new pilot, Pilot!" :nervous: :D
-
Did you use Turey's installer? I notice you have Root_fs2.vp instead of root_fs2.vp, which was a recently-fixed installer bug.