[darkdaej]

Just when I thought I'd be problem free.

Ooookay.  For those not keeping up with my issues (i feel i'm doing a weekly show here), I have completely reinstalled retail and FSO with the installer.  I have manually redownloaded the mediavps and replaced them (using MV_Complete with MV_Music), and had a great time playing FSPort 3.1.1.  I gotta give kudos to the whole team for making FS2 look like it was released a year ago.  It now OFFICIALLY looks better than X3 (except X3 has better lighting but no differently coloured stars, and theres no antialiasing yet in FSO)

Anyway, I completed the FS1 campaign, and wanted to move on to Silent Threat Reborn.

I followed all install instructions in the release thread.  I manually redownloaded the vp's on sectorgame and replaced them with the installer's version in case it could have been causing the problem.

But I still have retail fs2 graphics, even though I followed all the instructions listed here:
http://www.hard-light.net/forums/index.php/topic,59120.0.html

I haven't tried all campaigns, but ST:R seems to be the only one affected so far.  FS2 works fine, so does FSPort. 
 

[Narvi]

Check your mod.ini to see if it's pointing towards the right folders.

[darkdaej]

NEVERMIND, PROBLEM SOLVED.

The original post did not list the command line actions to enter(-mod fsport-mediavps,fsport-str,fsport,mediavps), i scrolled down and someone asked about them, so...problem solved, please ignore this thread!

Thanks!

[General Battuta]

NEVERMIND, PROBLEM SOLVED.

The original post did not list the command line actions to enter(-mod fsport-mediavps,fsport-str,fsport,mediavps), i scrolled down and someone asked about them, so...problem solved, please ignore this thread!

Thanks!

Wait, wait, it totally does list those command-line entries. At least it did when I installed, which was practically the day ST:R came out.

[darkdaej]

well in the post on the thread i couldn't find it.  i had to go down the page.

I just reread it and the command line functions are nowhere to be found, except mentionned as a question near the bottom of the page.

[Vasudan Admiral]

That's because you don't need to use command lines if you followed the steps listed there.

These two steps have the exact same effect as the command line, but also mean that you can switch the mod you're playing with the mod folder tab in the launcher, rather than having to add and remove command lines every time:

2) - Open mod.ini in your "\freespace2\fsport_str" folder and replace everything from the "[multimod]" part with this:

[multimod]
primarylist = fsport_mediavps;
secondarylist = fsport,mediavps;


--------------------------------------------------------------------------------

3) - Open the freespace launcher and go to the mod tab. Select the 'fsport_str' folder as your active mod.

[darkdaej]

and if you had read my OP i said i followed all instructions listed in the ST:R thread

I did do those modifications to the mod.ini file.  I had the problem with those mods done to it.  it wasn't until i wrote those command lines in the launcher that i got the good graphics and effects...


EDIT:  I've been playin' FSO for over a year now, ive encountered the fabled mod.ini problem when Blue Planet was first released.  Trust me, when my OP said I followed the instructions, I did.  I train people in tech support for a living, i know what it is.  I often force myself not to include a dxdiag on such routine matters as this one.

EDIT 2: 

Known Issues: (green ones are bugs that have been fixed)


3) In str06, "He Who Rides the Tiger", Lambda 1 will not dock with the Ratna if you are using the mediavps and your mod priorities are not configured correctly.

I also had this bug when playing this particular mission earlier today, but as i said, I followed all the instructions to the letter and thus, my mod priorities SHOULD be configured properly...

what did I miss 

I'll try to put in a more recent build of 3.6.10, see if that works...I'm using the one that came with the installer.

[Vasudan Admiral]

Ah - from what you posted as the command lines, it looks like you've still got the dash versions of the folder names, which to my knowledge don't work correctly.

So try changing the foldernames to use underscores (and reflect those changes in the mod.ini) and see if that works using the mod folder method without the command line.

Specifically:

-> "fsport_str" - Should contain fsport-str.vp, fsport-str-voice.vp, fsport-str.bmp and mod.ini
NOTE: If your folder is named 'fsport-str' as the FSO Installer names it, you will need to rename it to replace the "-" with an "_"so the launcher can use it correctly.

-> "fsport_mediavps" - Should contain mv_fsport.vp.
NOTE: If your folder is named 'fsport-mediavps' as the FSO Installer names it, you will need to rename it to replace the "-" with an "_"so the launcher can use it correctly.

[darkdaej]

OMFG...  Ok i feel n00bish now...

Here's what was going on:

I had two sessions open on my computer, and it turns out that the mod.ini file was still opened in the other session.

Seems the file, even though it was saved, hadn't updated properly.

I re-saved the file, closed it, ran FSO on that session using the command lines (for effects) that were suggested to input for FSo's 3.6.10 release and the problem is now solved.

Man I feel stupid....

[Galemp]

And how in Sol are we supposed to diagnose something like that?