[EBass]

I'm getting an instant crash on the mission "The Great Preservers" known issue or just me? Annoying if its unresolveable because I'm really enjoying the campaign so far.

[Jeff Vader]

Happens with 3.6.10 builds, unfortunately. Switch to 3.69 temporarily.

[EBass]

Wow, fast responce, tbh I'm a bit of a noob at this stuff. Media VPs came with a big pack I downloaded yesterday (SCP v2.0 I think) so how would I swap back to an older Media VPs? Obviously at the moment I'm running the "Blue Planet" mod, so is Media VPs automatically run for any mod? So what I'd just need to ship the latest version out of my Freespace folder and copy across an old one? Have you got a link please? thanks.

[General Battuta]

You don't need to switch to the 3.6.9 MediaVPs; you need to switch to a 3.6.9 build in the launcher.

Do you have one handy?

[EBass]

Well I have the Launcher, I basically have FS2 with the SCP latest version on it. A way to switch to an earlier version of MediaVPs doesen't seem immediatly obvious?

[Jeff Vader]

When attempting to harness the full power of FreeSpace, it is important to learn the difference between a build and the MediaVPs.

A build is a version of the FSO engine. Builds are always .exe files beginning with "fs2_open_". They make the game run.

MediaVPs are a collection of graphical (and occasionally audio) improvements. They are .vp files that contain textures, models, effects and what not. The MediaVPs rely on FSO builds in order to work.

In this case, you simply need to open the Launcher, click "Browse", select "fs2_open_3_6_9.exe", apply the changes and play the game. This issue is not caused by the MediaVPs. It is caused by the game engine.

[General Battuta]

You don't need to switch to any earlier MediaVPs. You need to switch to an earlier build. Change the actual Freespace executable you're running.

Fortunately, this is really easy. I think you can get one off Turey's installer, or from the forums. Then simply select it in the launcher (click the 'Browse' button at the top and select it there.)

If you did ever need to switch to the 3.6.9 MediaVPs, that'd be really easy too: download them, put the 3.6.10 MediaVPs into a folder called '3.6.10 mvps backup' or somesuch, and put the 3.6.9 MVPs into the 'mediavps' folder. Then you could swap them back whenever you wanted.

[EBass]

Well I have four VP versions

fs2_open_3_6_10d-20081225_r5020
fs2_open_3_6_10d-20090203_r5063
fs2_open_3_6_10r-20081225_r5020
fs2_open_3_6_10r-20090203_r5063

None appear to be the version I want correct? So that being I'll need a new one yes?

Sorry to bother you, I'm fairly new to all this (Big FS2 fan, but this is the first time in years I've played)

[General Battuta]

It's fine, don't worry.

Those aren't MediaVP versions at all. Those are builds. The MVPs are files contained within the 'MediaVPs' folder in your Freespace directory.

You're going to need to get a 3.6.9 build. Try the 'Freespace Open Installer' in the top bar of HLP. I believe that if you only check 'install 3.6.9' or something like that, it'll give you 3.6.9 builds. Lobo might have a better idea.

[Jeff Vader]

I do think Turey's Installer still downloads 3.6.9, since it is the latest "official" release. But you can also download it from here. Extract the .exe file to your \freespace2\ folder, then do what I told before. If you get warnings about unrecognized command-line parameters, just click Ok on them.

[EBass]

Ok I'm downloading now, as an aside we're probably clogging up the thread, so if you want to switch to the thread for this specific issue (which should be near the top as I just posted in it) thats fine by me, I'll make my next post there.

[Jeff Vader]

We should preferrably discuss this in one place. If Darius deems it necessary, he'll split this discussion from the release thread.

[EBass]

Ok we'll stay here. Continuing on......................

Upon putting the "fs2_open_3_6_9" file in my freespace 2 dir and then using it as my launching exe by browsing to it in the launcher I get the error

"Failiure to create the command recognition context"

So er yea, I don't know what thats about.

[EBass]

Ok, I'm assuming having run Turkeys installer that the reason I get this error is because I'm running the executable without the Media VPs files to back it up. So having run the installer I am selecting.

"Freespace 2 Open 3.6.9 with MediaVPs - The minimum plus some shiny graphical updates"

Yes?

[General Battuta]

 Noooo. You don't need the 3.6.9 MediaVPs and it'd be a waste of bandwidth.

Lobo? Any idea what this 'command recognition context' thing is on about?

[Wobble73]

Ok, I'm assuming having run Turkeys installer that the reason I get this error is because I'm running the executable without the Media VPs files to back it up. So having run the installer I am selecting.

"Freespace 2 Open 3.6.9 with MediaVPs - The minimum plus some shiny graphical updates"

Yes?

His name is Turey! And no you don't need the 3.6.9 mediavps, that may actually cause more problems than before.

[EBass]

Right well in that case I don't know whats going on, I've got the "fs2_open_3_6_9.exe" in the FS2 directory with my other executables and I did get the "unrecognized command-line parameters" as foretold and ignored them, but this "Failiure to create the command recognition context" stops me booting the game.

[General Battuta]

Well. Um. Maybe it is a problem with using the 3.6.10 MVPs and a 3.6.9 build.

This is a lot of effort to get through one mission. Unfortunately, it's completely worth it.

[Jeff Vader]

1. I'd like to remind people here that before 3.6.10 there was the 3.6.9 build and the 3.6.8 MediaVPs.

2. That error is new to me. Perhaps you should run a debug build and then post the fs2_open.log from your \freespace2\data\ folder so we could make sure there's nothing wrong in terms of .vp files and things like that.

[EBass]

Please remember I am new to this and thus if I need to do something its probable I have no idea how to do it and will need to be told. In this case I have no idea how to run a debug build.