[-Norbert-]

I just downloaded ST:R and installed everything like the first post showed it. The only thing I don't have is the fsport_hi_res.vp, since I couldn't find it, but FS_Port itself is running fine wihtout it.

Now the problem I have is, that when I go to the Tech Room some ships are missiong parts or the complete model.
The Faustus for example is completely gone, while the Centaur has no cockpit and the Imothep is a collection of free flying parts that don't even touch.

Doesn anyone have an idea what's wrong?

Edit:
Ok, I just found something like a solution to my problem. I originally put the fsport_mediavps folder in my mod.ini, which apperently caused the errors. Now that I just have fsport in the mod.ini it workes.
Is there a way to use the 3.6.10 mediavps with ST:R?

[Jeff Vader]

Ok, I just found something like a solution to my problem. I originally put the fsport_mediavps folder in my mod.ini, which apperently caused the errors. Now that I just have fsport in the mod.ini it workes.

lolwut

Is there a way to use the 3.6.10 mediavps with ST:R?

Put STR stuff into \freespace2\STR. Put FSPort MediaVPs to \freespace2\fsportmediavps\. Put Other FSPort stuff to \freespace2\fsport. Put the regular 3.6.10 MediaVPs to \freespace2\mediavps\. Use the following custom command-line:

-mod fsportmediavps,STR,fsport,mediavps

Folder names can be changed, but the command-line must then be changed accordingly.

[-Norbert-]

lolwut

What I meant was something like this:

Code: [Select]

[multimod]
primarylist  = FS_Port ;
secondarylist = fsport_mediavps, mediavps;I tried it with fsportmediavps in primarya and fs_port in secondary, both with and without putting the folder of the 3.6.10 mediavps in the secondary wihtout it working...


And thanks for the help, it now works (at least in the Techroom, havn't started a mission yet, but I'm confident).

But I still don't get, why the mediavps work in the custom flags, but not in the mod.ini ...

[chief1983]

I was thinking it needed to be something like:

Code: [Select]

[multimod]
primarylist  = ;
secondarylist = STR,fsportmediavps,fsport,mediavps;
This would be in a mod.ini ina separate mod folder called STRmediavps, or something like that.  I copied and pasted the mod.ini and the bitmap from STR and put them in a new folder, with that change made to the mod.ini.  However, some ships end up not being the HTL versions, for instance the Amazon Advanced.   But I'm pretty sure it has to be in that order or the table files from FS2 (included with the mediavps) would conflict with those from the fsport.  Is there a better way to be doing this?

[Goober5000]

Vasudan Admiral has a tutorial in the first post of the release thread.

[-Norbert-]

As I mentioned in my first post I did it exactly like it was described in the Tutorial, but only ended up with misssing and incomplete ships.
The only thing that worked for me was setting the custom flags in the launcher.

I just now tried to put the line from the custom flags field in the mod.ini like this:

Code: [Select]

[settings]
flags = -mod FS_Port,Silent_Threat_Reborn,FS_Port_Mediavp,MediaVP3610;
but that didn't do anything at all, but at least it's a good place to "store" that line when playing some other mod or campaign.

[Grimper]

Put this in your ST:R mod.ini, then select ST:R as your mod:

[multimod]
primarylist = FS_Port_Mediavp;
secondarylist = FS_Port,MediaVP3610;

[-Norbert-]

As I said twice before I tried that first, but it didn't work.

[chief1983]

The important thing seems to be that the load order is fsport_mediavps, fsport_str, fsport, mediavps.  If you modified your mod.ini for ST:R, it should be in the order that grimper stated.  The order that you tried in your previous posts was incorrect.  Here's what to do.  Put the default mod.ini file back in the ST:R folder.  You'll be able to play it without the mediavps and as you said, it should work just fine.  Then, copy (not move) the fsport-str.bmp and mod.ini from ST:R to a new mod folder called fsport_str_mediavps.  Edit the mod.ini to be something like this:

Code: [Select]

[launcher]
modname      = Silent Threat: Reborn v1.0 MediaVPs;
image255x112 = fsport-str.bmp;
infotext     = As the Great War rages on, you've been commissioned by Galactic Terran Intelligence for special intelligence operations.  Your objectives are to contain the Shivan onslaught and preserve the fragile Terran-Vasudan alliance.  But a series of suspicious events cloud the GTI's spotless record.  Is the GTI setting you up or are the Shivans spreading their evil rage?;
website      = http://fsport.hard-light.net/website/str/;
forum        = http://www.hard-light.net/forums/index.php/board,140.0.html;

[multimod]
primarylist = FS_Port_Mediavp,Silent_Threat_Reborn;
secondarylist = FS_Port,MediaVP3610;

This is my exact setup and I know it works.  If it doesn't work you've goofed something else up that's yet to be revealed.  Try running a debug build and grab the fs2_open.log file from the data folder and post it here if you still have trouble.

[FSW]

I appear to have a similar bug, but only on one object. The Karnak looks like this both in-mission and in the tech room. It looks the same from any angle - even from in the core.

At first, I thought this was some very cool intentionally modelled battle damage. Then I flew into invisible walls.

I wonder what happened here. I installed ST-R with Turey's downloader, and used Vasudan Admiral's mod.ini changes for mediaVPs.

[attachment stolen by Slimey Goober]

[Jeff Vader]

Your fs2_open.log should reveal any fails that occur when running STR.

[-Norbert-]

Thanks chief1983, your solution worked for me too.
And even better than the custom flag solution.
For some reason some of the models weren't the latest ones with the "flag-method" (the Apollo and the Valkyrie among them).

[chief1983]

Yeah I didn't really want to mess with the default mod.ini if I didn't have to.

[CaptJosh]

Um, chief, why would you need the STR directory in the multimod section when it's already the selected mod?

[chief1983]

Sorry, read closer.  I created a new mod folder, with only the bitmap image and a new mod.ini in it.  That keeps you from  having to edit the mod.ini that comes with ST:R and still play it in retail mode with changing the file back.

[CaptJosh]

Ah. That certainly would work. It's kind of like creating a symlink in a *nix filesystem. Not going to be something I'll do. I have no need to play this in retail mode. *chuckles*

BTW, does anyone know if that Radar Icons deal has made it into the trunk yet? I want to correct the Vasudan Command error, but I don't want to lose my radar icons. I like the idea that I get silhouettes on larger targets.

[chief1983]

Not for 3.6.10.   Soon though hopefully.  Just a couple major bugs to go...unless more get found.