Issues with FFEdit...

[cmdrkoenig67]

Hi guys...I've been attempting to make some new maps...But...My biggest problem is BLUE SCREEN OF DEATH!  Every time I try to re-open a map in progress...My computer goes to BSOD!  What could be the problem?  It's doing it every time I make a new map and try to re-open it after closing it.  It's scaring me.

I appreciate any help.  Thanks guys.

Dana

[Previsionary]

ffedit would list all it's errors in one of the many log files, so check there. But, I would start making sure all my important files and info were backed up since the BSOD is a fairly large warning sign I wouldn't just shrug off.

[cmdrkoenig67]

Hi Prev,

Thanks for the reply...Where do I check these log files?...I'm not terribly computer-literate.

Dana

[Previsionary]

same place as the other logs:

Program Files\Irrational Games\Freedom Force vs The 3rd Reich

if you have extensions on, then you see ff.log, script.log, charactertool.log, etc. Otherwise they just look like text files.

[cmdrkoenig67]

Ah....The FFVTTR Edit log appears as a text file and the last few entries look like this...

00:12:26.66: FFVTTR Edit: CMissionEdPage::ReadDialog - WARNING can't find markersc_cub_AloeBush14
00:22:43.74: FFVTTR Edit: writing database: C:\Program Files\Irrational Games\Data\missions\ds_mp_atlantis\mission.dat
00:22:43.86: FFVTTR Edit: wrote 197 items
00:22:52.76: FFVTTR Edit: writing database: C:\DOCUME~1\Owner\LOCALS~1\Temp\mission.dat
00:22:52.93: FFVTTR Edit: wrote 197 items

[GogglesPizanno]

That looks like a pretty standard looking log file....
Between now and the last time it was working have you installed any updated drivers, MS updates, software utilites etc... anything that conceivably could have altered or updated the system in a dramatic way?

As Prev said, when you start seeing the BSOD its a bad sign, and the fact that its happeneing now when it didn't before means that its probably now conflicting with somethign that was changed or new in the OS. I'd second the advice about backing up any important data, files etc as your first action.

If it happens again, the BSOD will usually throw an error code or filename that caused the fault. Its often as generic as "NT kernel", but sometimes you might get reference to a graphics driver or something else that might point you in the direction of what caused it... so IF it happens again, in between panicking and restarting, read the output and note if it throws out any info that might be useful. You might get lucky.

[cmdrkoenig67]

Thank you, Goggles (and thanks to you too, Prev).  It's been like clockwork, every time I attempt to work on maps in FFVTREdit.

Dana

[cmdrkoenig67]

That looks like a pretty standard looking log file....
Between now and the last time it was working have you installed any updated drivers, MS updates, software utilites etc... anything that conceivably could have altered or updated the system in a dramatic way?

The only thing I've installed updates to are the AVG (Anti-Virus Guard) and Zone Alarm firewall....That's pretty much it.

As Prev said, when you start seeing the BSOD its a bad sign, and the fact that its happeneing now when it didn't before means that its probably now conflicting with somethign that was changed or new in the OS. I'd second the advice about backing up any important data, files etc as your first action.

If it happens again, the BSOD will usually throw an error code or filename that caused the fault. Its often as generic as "NT kernel", but sometimes you might get reference to a graphics driver or something else that might point you in the direction of what caused it... so IF it happens again, in between panicking and restarting, read the output and note if it throws out any info that might be useful. You might get lucky.

So this error would be listed on the BSOD somewhere, I'm guessing?....I told you I know little about computer workings.

Dana

[cmdrkoenig67]

Okay....I tried to open the map, got the BSOD and I don't know if this means anything...

ialmdd5.dll Address bfa5849e base at bfa1a000

[GogglesPizanno]

After a quick Google search, ialmdd5.dll is the Direct Draw component of Intel Graphics Drivers.
Apparently a lot of people have had issues similar to this with other games.
Although it always appears to have happened after an upgrade (game, windows etc...)

So a couple of things.

1. Have you recently upgraded Windows service packs or other major windows update?
2. Have you changed your video drivers recently?
3. Have you installed some new game that may have updated you DirectX install?

What you can try is to run a direct X diagnostic. It will run various graphic tests as well as give you any info about what model of graphic card and driver you have so that its easier to find proper drivers for it.

Go to "Start > Run" and then type "dxdiag" and hit enter.
It will then open up the application. Have it go through all the tests and see:

A) If anything errors
B) Model of the video chipset

My guess ultimately is that its just going to be an issue with finding the type of driver you need and downloading the most recent one from Intel...

[cmdrkoenig67]

After a quick Google search, ialmdd5.dll is the Direct Draw component of Intel Graphics Drivers.
Apparently a lot of people have had issues similar to this with other games.
Although it always appears to have happened after an upgrade (game, windows etc...)

So a couple of things.

1. Have you recently upgraded Windows service packs or other major windows update?

Nope.

2. Have you changed your video drivers recently?

No again.

3. Have you installed some new game that may have updated you DirectX install?

That's another negative...It seems to be only about two maps...I've tried a bunch of other older maps I've made and they all work fine.  The two maps that crash my comp both have an large amount of the dream fog (that's the only thing I could think of that might be doing it)....Maybe my Graphics driver can't handle that much?

What you can try is to run a direct X diagnostic. It will run various graphic tests as well as give you any info about what model of graphic card and driver you have so that its easier to find proper drivers for it.

Go to "Start > Run" and then type "dxdiag" and hit enter.
It will then open up the application. Have it go through all the tests and see:

A) If anything errors
B) Model of the video chipset

My guess ultimately is that its just going to be an issue with finding the type of driver you need and downloading the most recent one from Intel...

[Previsionary]

yes, it might just be graphic related and all the fog/objects/movement is overloading your card.

[cmdrkoenig67]

I ran the Direct X diagnostic (as you suggested, Goggles) and it didn't find any problems...It must be just too many fog objects on those maps.  Both maps were new FFVTTR underwater maps I was working on...They had many, many re-textured dream fog objects.  I deleted both of the maps and started over with a new one (with much less fog objects)...The new map seems to be working just fine, I've opened it several times and it hasn't crashed.

Thank you very, very much guys.

Dana

[GogglesPizanno]

And the curse of the Underwater maps continue....

[cmdrkoenig67]

LOL....Yup.  I'm still not happy with the looks (and fog FX) of the maps yet either (and I think this is my Fifth attempt)...Sigh.

Dana