[darkdaej]

Interesting issue.  I have this problem (in ST:R, so far) which is rather annoying...  I cannot see any "laser" fire.  Missiles will appear, but I can't see my own shots nor anyone else's.

In FSPort (recently updated thanks to turey's installer to 3.1.1), I finished Avenging Angels but I cannot get to the next mission.  I get this crash to desktop with an error message which says

Error: Can't open model file <S_Rockeye.pof>
File: ModelRead.cpp
Line: 1905


Call stack:
------------------------------------------------------------------
------------------------------------------------------------------

Breaking into debugger causes Freespace.exe to crash, cancelling quits...

Now to clear the n00b questions
this isn't my first post here anyway, although it's been eons...

I have retail FS2 installed, added the SCP via Turey's installer, installed everything(checked everything except the mac and linux files...pretty much)
I have Vista Ultimate x64 SP1.
All Campaigns worked perfectly before I installed the updated version of FSPort, including my old version of the 3.6.10 build
I have several versions of the 3.6.10 builds, tried 'em all, same problem.
Yes I did pick the /fsport-mediavps folder in the mods tab.
All the grafx options are set to their highest.


Hmm, I'd need some assistance in solving this...(even if the explosions do sound corny, its part of the charm of it )

Thx in advance to the Gods of FS2's revival

[FUBAR-BDHR]

Run a debug build and attach the log or post it using the code tags. 

[Jeff Vader]

You are using the FSPort MediaVPs without the regular 3.6.10 MediaVPs. Put the FSPort MediaVP to \freespace2\fsport-mediavps\ , the rest of the FSPort stuff to \freespace2\fsport\ and the 3.6.10 MediaVPs to \freespace2\mediavps\ . Make sure that the mod.ini in the \fsport-mediavps\ folder has a line that says "secondarylist = fsport,mediavps;" without quotations. Select the \fsport-mediavps\ folder as your mod. Play.

[darkdaej]

You are using the FSPort MediaVPs without the regular 3.6.10 MediaVPs. Put the FSPort MediaVP to \freespace2\fsport-mediavps\ , the rest of the FSPort stuff to \freespace2\fsport\ and the 3.6.10 MediaVPs to \freespace2\mediavps\ . Make sure that the mod.ini in the \fsport-mediavps\ folder has a line that says "secondarylist = fsport,mediavps;" without quotations. Select the \fsport-mediavps\ folder as your mod. Play.

I'll check the mod.ini file to be sure, but i'm pretty certain I DID the mods to the .ini file.

all the rest was already done, and mentionned in my post (i.e: used turey's installer and picked the fsport-mediavps folder, thus the fsport mediavp was already in folder, and ive use SEVERAL builds of 3.6.10 (including the regular, bundled with my download through turey's installer.

I'll verify the mod.ini file and get back to you, though i'm pretty sure its already done there...  i did follow install instructions in the mod's folder in the forums.

[Jeff Vader]

Run a debug build ans post the fs2_open.log that is generated to \freespace2\data\ . It will know.

Edit: Though I suppose this could also be a case of corrupt MediaVPs. If that's the case, a simple (manual) redownload should do the trick.