Hard Light Productions Forums

Hosted Projects - FS2 Required => FreeSpace Conversion => Topic started by: Topgun on September 21, 2007, 09:39:31 am

Title: media vps for fsport
Post by: Topgun on September 21, 2007, 09:39:31 am
I want htl graphics on fsport.
How?
Where?
Title: Re: media vps for fsport
Post by: Wobble73 on September 21, 2007, 09:43:06 am
Umm.......mod.ini???  :nervous:  :confused:
Title: Re: media vps for fsport
Post by: jr2 on September 21, 2007, 06:58:05 pm
Ya, open fsport's mod.ini .. it should have "secondarylist = mediavps" (without quotes).

Here's mine (the one Turey's Installer uses):

Code: [Select]
[launcher]
infotext     = FreeSpace 1, now ported to run on the FreeSpace 2 engine.;
website      = http://fsport.hard-light.net/;
forum        = http://www.hard-light.net/forums/index.php/board,39.0.html;

[multimod]
primarylist  = ;
secondrylist = ,mediavps;

[settings]
Title: Re: media vps for fsport
Post by: Edi on September 23, 2007, 03:46:20 pm
In the mod.ini files, should that be
"secondarylist="
OR
"secondrylist="

??

Because right now it's using the latter one, "secondrylist=", which might be the reason behind various problems in training missions and the "Enter the Dragon" one where you don't have the primary weapons you should and they get reset to Aveger + ML-16 if you call support.

The same spelling error, is it is such, is also in the Cardinal Spear, Awakenings and possibly other mod.ini files on FSOpen.

Oh, and name's Edi, nice to meet you all. Been a Freespace fan since it came out.
Title: Re: media vps for fsport
Post by: Jeff Vader on September 23, 2007, 03:50:50 pm
Secondary is the way to go. With the a.
As for the training mission, you'll find a fixed version behind the Useful stuff for FSO link in my sig. Extract it to \fsport\data\missions.
As for loadout problems, make sure that you have all of your mods in their own folders. Don't install any mods directly to \freespace\ or \freespace\fsport\.

Oh, and
:welcomered:
Title: Re: media vps for fsport
Post by: Edi on September 23, 2007, 11:45:37 pm
Thank you. :)

I haven't moved files around, so everything is where the installer put it, which is presumably the correct place.

Being new to these forums, I don't know who's in charge of what, but all of the mod.ini files that come with the game when using the OpenInstaller should be fixed as soon as possible. With one exception they all had the "secondrylist" spelling error, which may cause problems for new people. Looks like somebody just copy-pasted the line and then added whatever vps file was needed for that particular mod. IF you aren't the right person, would you let the right person know?
Title: Re: media vps for fsport
Post by: Jeff Vader on September 23, 2007, 11:52:57 pm
... what... huh? You talkin' to me? 'xcuse me, I'm a little trippin' since it's 7:50AM on this side of the world. Well, the person ultimately responsible for the Installer is Turey (hence the name Turey's FSO Installer), so you may want to consult him about this issue. I wouldn't know anything about this since I persistently install my FSOs manually.

Also, I thought about your missing weapons issue while asleep and a thought occurred to me. If you've been changing campaigns and particularly mods with a single pilot file, the file might have corrupted. Creating a new pilot and starting from scratch fixes that.

Edit: Oh wait, you're on my side of the world. Great! Never hurts to have more Finns here at HLP.
Title: Re: media vps for fsport
Post by: Wanderer on September 24, 2007, 12:40:04 am
Well... secondrylist was originally typo in code so earlier secondarylist didnt work but secondrylist did. And it still is supported. So it doesn't really matter.
Title: Re: media vps for fsport
Post by: Edi on September 24, 2007, 01:40:52 am
... what... huh? You talkin' to me? 'xcuse me, I'm a little trippin' since it's 7:50AM on this side of the world. Well, the person ultimately responsible for the Installer is Turey (hence the name Turey's FSO Installer), so you may want to consult him about this issue. I wouldn't know anything about this since I persistently install my FSOs manually.

Also, I thought about your missing weapons issue while asleep and a thought occurred to me. If you've been changing campaigns and particularly mods with a single pilot file, the file might have corrupted. Creating a new pilot and starting from scratch fixes that.
Haven't gotten around to playing anything other than the basic fsport campaign or using any mods, so that shouldn't be an issue. A friend of mine who introduced me to FSOpen warned me about the issue of pilot file corruption, so I do have backups. We'll see what happens when I get back to that particular mission.

Wanderer, thanks for clarifying the typo issue. :)
Title: Re: media vps for fsport
Post by: Topgun on September 25, 2007, 04:26:58 pm
what I meant was that the htl ships are not in the media vps. were can I get them? and also the shockwaves are overridden, I want to use the MV_advanced effects one.
Title: Re: media vps for fsport
Post by: jr2 on September 25, 2007, 07:25:50 pm
You mean that the low-quality fsport ships are overriding the HQ mediavps ones?
Title: Re: media vps for fsport
Post by: Topgun on September 26, 2007, 01:16:10 pm
yes.
and where are the htl apolo and athena ECT?
not only that I want the 3d shockave, not the FS1 one.
Title: Re: media vps for fsport
Post by: jr2 on September 27, 2007, 01:58:49 am
Goober5000 is the FSPort guru.  Get him in here.  ;)
Title: Re: media vps for fsport
Post by: Goober5000 on September 28, 2007, 11:13:01 pm
Why?  My minions are handling the situation perfectly fine.  I have important overlord-type-stuff I need to be doing. :p
Title: Re: media vps for fsport
Post by: jr2 on September 29, 2007, 02:21:16 am
Someone's been playing Overlord... :nervous:  The world is doomed!  :shaking:
Title: Re: media vps for fsport
Post by: Agent_Koopa on October 07, 2007, 04:55:52 pm
Well... secondrylist was originally typo in code so earlier secondarylist didnt work but secondrylist did. And it still is supported. So it doesn't really matter.

Wait, so that's not the problem? So we have no idea what causes it?