[lolplayer]

Hi there,

I just recently downloaded Shrouding the Light campaign - the 122MB archive containing Shrouding the Light/Shrouding the Light Origins Repack (2007-07-29)".

The problem I have is that I can't figure out how to make it play nice with fsport and mediavps. Maybe someone can offer a hint?

I can play the campaign from the mod with no serious problems so far, so there is no issue here. However, the default mod.ini contains

Code: [Select]

[multimod]
secondarylist = fsport,mediavps;
Which I obviously (?) change to

Code: [Select]

secondarylist = fsport,mediavps_3612;Now I get the nice models of ships except the select few, for instance the PVC Aten, which uses this model instead of the nicer one.

So then I try

Code: [Select]

secondarylist = fsport-mediavps,mediavps_3612; which gives me all sorts of problems - from startup warnings, through wrong "main hall" (terran instead of vasudan) to missing HUD reticles. The models look nice though.

Then I try (I am obviously doing an uninformed trial-and-error here)

Code: [Select]

primarylist = fsport-mediavps;
secondarylist = fsport,mediavps_3612;which seems to bring the best of both worlds - nice looking models with no additional headaches except initial 18 warnings, which I am pasting below:

Code: [Select]

WARNING: "Unable to find WEAPON_LIST_TYPE string "Interceptor#Weak"  in ship: GTF Ulysses's secondary banks." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Interceptor#Weak"  in ship: GTF Ulysses's secondary dogfight banks." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Interceptor#Weak"  in ship: GTF Apollo's secondary banks." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Interceptor#Weak"  in ship: GTF Apollo's secondary dogfight banks." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Vasudan Light Laser"  in ship: PVB Sekhmet's primary banks." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Interceptor#Shivan"  in ship: SF Dragon." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Phoenix V#Shivan"  in ship: SF Basilisk." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Interceptor#Shivan"  in ship: SF Manticore." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "MX-50#Shivan"  in ship: SF Manticore." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "MX-50#Shivan"  in ship: SB Nephilim." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Synaptic#Shivan"  in ship: SB Nephilim." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Phoenix V#Shivan"  in ship: SB Nephilim." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "MX-50#Shivan"  in ship: SB Nephilim." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "MX-50#Shivan"  in ship: SB Seraphim." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Synaptic#Shivan"  in ship: SB Seraphim." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "Phoenix V#Shivan"  in ship: SB Seraphim." at parselo.cpp:2707
WARNING: "Unable to find WEAPON_LIST_TYPE string "MX-50#Shivan"  in ship: SB Seraphim." at parselo.cpp:2707

So therefore I have two questions:
 - is there a way to get rid of these warnings and keep the nice models of mediavps_3612?
 - are these warnings anything serious that will bite me later on or should I just blast away with the campaign and ignore them happily?

[AdmiralRalwood]

Unless I'm very much mistaken, the arrangement you want is

Code: [Select]

[multimod]
secondarylist = fsport-mediavps,fsport,mediavps_3612;

I've never played Shrouding the Light, however.

[niffiwan]

I don't have STL here either, but ST:R has this in its mod.ini, so I thought this would be the correct config?

Code: [Select]

[multimod]
primarylist = fsport-mediavps;
secondarylist = fsport,mediavps_3612;

I'm not sure exactly what the warnings mean though, I'd probably need to have a look at STL to figure it out.

[lolplayer]

Thanks niffiwan and AdmiralRalwood for your suggestions. It seems that both of the configurations you proposed have the same effect and produce the same warnings. Again - I am perfectly fine with such a setup so far; I am just worried that something might explode later on...

The one with primarylist defined is the one I've been using so far. And indeed, I also took this idea from ST:R setup.

BTW. Can you point me to the explanation of each of the [multimod] entries' semantics? I mean the differences between primary and secondary, the ordering etc...

[Yarn]

The multimod format is explained here: http://www.hard-light.net/wiki/index.php/Mod.ini#Multimod

The line that AdmiralRalwood gave is the one that most FSPort mods should use. Silent Threat: Reborn is a rare exception to this; don't use it as an example for configuring other mods! (And once FSPort uses the 2014 MediaVPs, you'll have to change mediavps_3612 to mediavps_2014.)

Shrouding the Light's mod.ini is configured the way it is because it was released before FSPort 3.1, the first version to have its own MediaVP package.

[Macfie]

Because of the age of STL it probably has it's own Ship and Weapons tables.  Starting with FSO 3.6.12 and the 3.6.12 mediaVPs this caused these type of warnings to be displayed.  However it should not prevent you from playing the campaign.  Make sure the folder names that the mod.ini refers to are the same as the ones containing your FSPort files and FSPort media VPs.