[Mongoose]

When I have the SCP and the latest version of Fred_Open installed, the original version of Fred2 refuses to open; it always gives me that standard Windows "This program has encountered a problem and needs to close" error.  Is this a problem, or is it normal with the SCP installed?

[Night Hammer]

what does the error say?

[Goober5000]

It's not normal, but it could be a memory leak.  Try rebooting.

[Mongoose]

It's happened to me on several occasions over several different reboots.  I don't know if I remember it happening right after I first installed the SCP, but I'm pretty sure it didn't.  Just to make sure we're on the same page:  the error is occurring with the original, vanilla, Volition release of Fred 2.  I have 3 versions of Fred_Open installed in the same directory:  one for Inferno, the 3.5.5 version, and a recent HTL release.  I also have the VP files for the Freespace Port in the same directory.  My initial thought was that one of the above was simply interfering with the original Fred2; I can't see how it can be a memory leak, since that program hasn't been changed in any way with the installation of SCP.

The error message doesn't really say anything; it's the standard XP window when a program has an unexpected error, asking if I want to send the error data to Microsoft or not.  There is a link to get more technical information about the error report, but it's just miles worth of code that probably doesn't do anyone any good .

Edit:  I haven't yet tried moving all of the SCP stuff out of the FS2 directory, mainly because I've been too lazy .  I'll give it a shot tomorrow, though.  I'm also aware that simply uninstalling everything FS2-related and reinstalling without the SCP will fix the problem, but it's not worth the effort.

[karajorma]

I find that FRED2 craps out on me if I ever try to run it with the media.vp's in place. Obvious it's choking on the high-poly models, altered tables etc.

Quite frankly I couldn't care less really. I only FRED for FS2_Open these days.

[Mongoose]

I would really like Fred2_Open if there was one version that didn't crash at all, no matter what mission you tried to open .  Both of the versions I have, 3.5.5 and the HTL one, have crashed when opening certain missions; using the other one always works, though.  I remember hearing that development of Fred2_Open was lagging behind FS2_Open; it would be a great help to all mission designers if some progress were made on this front .

P.S.  While I'm asking, is there any way at all to fix the problem with opening missions that has been around since the original FRED?  I'm referring to the fact that, when you double-click on a mission file, FRED simply opens up without actually opening the file, forcing you to use File->Open instead.  It's been a source of annoyance to me, and I'm sure many others, since FS1 .

[Goober5000]

Originally posted by Mongoose
I also have the VP files for the Freespace Port in the same directory.

Including fsport_music.vp?  That crashes retail - both retail FS2 and retail FRED2.

[Mongoose]

That would probably be it, then.  Thanks for the help .