[TotoGuy]

I'm sorry to post about this here, but for some reason Mantis never sent me any confirmation mail after registering with 3 different emails (including gmail).

I seem to be having the same issues as reported in bug ID 0001271 - whenever I click either option in the FRED2 Open Import menu (FS1 Mission or Weapons Loadout), FRED2 just crashes with the generic WinXP crash message.

Was there any progress with that issue? Seems there were no new updates for that bug for more than 6 months.

I've tried using builds 3.6.9 and 3.6.10, both normal and debug versions, happens all the time.
Rest of FRED2 seems to work just fine, as well as the game itself.

I would really like to resolve this issue, since I was about to start converting several FS1 campaigns. If there's any more info you'd like to know, or some way for me to register in Mantis to continue the discussion in there, let me know

[karajorma]

Problem is that none of the coders can reproduce this error. It simply doesn't crash for us.

[TotoGuy]

Don't suppose there's something they can figure out from the WinXP error report eh?

Was hoping the debug version would give me something to work with...

Guess I'll need to try it on a different computer or something...

Can you tell me what's the oldest FRED2 version featuring the Import option? And where I could get it?


EDIT: Actually, I have a better idea. Is there a free compiler (with IDE) I could use to just debug this issue myself? I'm a programmer, but it's been a few years since I've programmed under windows (I work on a completely different platform), so I don't really have anything installed for that.

I saw the sticky for the VC++ Express free trial, but it mentioned something about not supporting MFC so FRED2 wouldn't work with it. Any other suggestions?

[Goober5000]

D'oh.  I think I may have discovered the problem.

Is your FreeSpace2 folder called something other than "FreeSpace2", perhaps?

EDIT: If so, try this build: http://fs2source.warpcore.org/exes/latest/20080708-Goober5000.zip

[TotoGuy]

Woo! It works!

Browsing through the code yesterday in notepad, I reached the part with the stristr function looking for the FreeSpace2 string in the path, but I assumed it uses a proper default path otherwise. My angle instead was an MFC related error while doing the DoModal() so I wanted a debugger to check the exact input to the CFileDialog object creation, or maybe some MFC trace messages.

Guess the default wasn't quite proper after all

So like I said, it works with the supplied build, though only the mission import, not the weapons loadout import - I'm guessing you only changed the mission routine?
Renaming my folder as FreeSpace2 fixes both of them.
Funny how rare this issue is... one would think that more than 2 people picked a non-default folder name

Many thanks to both of you! Glad to see another bug dusted.

[Goober5000]

Cool.

The weapon loadout import is now also fixed.