[DarthWang]

I lost my original Freespace and Freespace 2 files a while ago, but I recently managed to get FS2 working again, so I followed the instructions to get the new downloader, but when I configured the launcher I got an error, I then found and downloaded the OpenAL program, but when I started the launcher again I got the same error "Launcher must be in the same directory as the binary file you are trying to run". Still it let me set it up and start it anyway, I decided to start with FSport, and selected the FSport-mediavps under the mod tab. When I ran the program and tried to fly a mission, however, I got an error that several ships were not found in the files so the mission might have errors. I decided to abort loading it. Trying to run the launcher again just now, I noticed that the first error no longer showed up, but I still need help.

[headdie]

"Launcher must be in the same directory as the binary file you are trying to run".

check that the launcher exe is in the same folder as the freespace exe you are using.

I decided to start with FSport, and selected the FSport-mediavps under the mod tab. When I ran the program and tried to fly a mission, however, I got an error that several ships were not found in the files so the mission might have errors. I decided to abort loading it. Trying to run the launcher again just now, I noticed that the first error no longer showed up, but I still need help.

You need to select FSPort, the FSport-mediavps (and for that matter where applicable MVP) are referenced by the Port mod not the other way round

[The E]

Also, make sure you have the FS1 campaign selected in the campaign room.

Oh, and please post an fs2_open.log.

[DarthWang]

Okay, I got it working (I had the wrong campaign selected, silly me), and I was able to play FSport basically fine, although the game did CTD once during the campaign, but I reloaded it and finished it.

Next I selected Silent Threat Reborn in the mod section, but I got an error message saying that there were 68 errors detected in the vp files, and the program could try to compensate for them if I wanted to go ahead, so I did, but as soon as I started the first mission, it crashed and I got this error:

Can't open model file <S_Rockeye.pof>
ntdll.dll! KiFastSystemCallRet
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_12r_INF.exe! <no symbol>
fs2_open_3_6_12r_INF.exe! <no symbol>

[General Battuta]

Oh, and please post an fs2_open.log.

This will allow us to fix all your problems.

[DarthWang]

I'm sorry, I don't know what that is

[The E]

Please read the FAQ stickied here. You know, the thread labeled "READ BEFORE POSTING".

[General Battuta]

Yes, please read the giant stickied support FAQ. 

[DarthWang]

Okay, I did the stuff it said, and it crashed when it was loading the mission in the debug build (unlike the regular version which let me start the mission then crashed), and it created a file, I think it's the right one, I attached it to this post

[attachment deleted by admin]

[The E]

Gah. Bloody ST:R.

Please go to the fsport-str folder. Open the file called mod.ini. Edit the secondarylist entry to use "mediavps_3612" in place of "mediavps". Then try again.

[DarthWang]

Thanks, that seemed to work! I played the whole campaign just to make sure, though.