[Fmstrat]

So I installed FS2Open, and I like it.. BUT

I don't have enough RAM to handle these high resolution explosions and such.  Even when I set the launcher to play "normal Freespace" the explosions seem to slow things down, so I'm thinking it's still using the high res ones.  Is there an easy way to turn them off without copying my old directory back over and reinstalling FS2Open?

[Swamp_Thing]

In the FSO interface, search for the FEATURES tab, deselect all the effects. Remember to have the FSO point to your FS_Open.exe, if you want to use FSO. Chances are you had it still running in retail FS.exe. If FS ran good in retail in your system, FS_Open will run smooth aswell. You just need to find the right combination.

[Fmstrat]

I had it pointed to fs_open (3.6).  I'll check that features tab when I get home.  Thanks!

[Dekzar]

Quick question: Did you download 3.6 because it was stickeyed on the main forum and appeared, for all intents and purposes, to be the latest stable release?

[Fmstrat]

Yup.  Should I have done otherwise?

I noticed there is an 8/22 release hosted on a website other than the place I got mine (hosted on icculus.org, I got mine at fs2source.warpcore.org).   Should this be the version I use?  I got the impression from that thread that it wasn't tested very much.

[karajorma]

The problem appears to be that the media.vp files you have contain the high performence versions of the explosions.  

The problem is I'm not certain of the name of the offending media.vp for 3.6. My bet is that it would be called something like mv_effects.vp but I can't be certain. If that isn't good enough try this. The following vp files are the official [v] ones. The problem does not lie with any of them.

# root_fs2.vp
# sparky_fs2.vp
# sparky_hi_fs2.vp
# stu_fs2.vp
# tango1_fs2.vp
# tango2_fs2.vp
# tango3_fs2.vp
# smarty_fs2.vp
# warble_fs2.vp

Move all the other .vp files into a new subfolder. You can then either

a) Put them back one at a time until you find the culprit.
b) Get hold of VPView (Look at the FAQ I link to below) and search through the extra .vp files for anything with a name like exp0x.ani. Leave that one where it is and put the other vps back.


As for which build to choose that's a bit of a dilema. 3.6 is the last official build. It should have less bugs than the latest builds which are available. However the latest builds have fixed bugs which are present in 3.6.
 The best thing to do is to download 3.6 and one of the latest builds and try them out to see what works for you.

However I still think your problem is caused by the media.vp files rather than the builds so I doubt that a new build would fix this particular problem.

[Hippo]

Originally posted by Fmstrat
Yup.  Should I have done otherwise?

*sigh* You aren't the first to be confused by that... I'm going to go register a complaint...

[Goober5000]

3.6 is the latest, stable, official release.  Any build later than that is neither official neither supported.  Thus, you use the later media vp stuff at your own risk.

[Liberator]

But the official 3.6 release in the installer has a memory leak doesn't it?

[Setekh]

Welcome to HLP, Fmstrat.