fs9.cfg buggered...why?

[PH_AJH]

Hi all
The following happened to me twice before and I would really like to know why it happens.
The values in my FS9.cfg get changed to ridiculous numbers and as a result FS2004 crashes. I always keep a copy of a "good" FS9.cfg at hand so I can correct it but still....why does this happen and what can you do about it? Thanks
AJ

(just an extract of the buggered file)

LOADWEATHER=-1099710861
MAX_UNLIMITED_VIS=-1099710861
CLOUD_DRAW_DISTANCE=6
3D_CLOUD_PERCENT=30
DETAILED_CLOUDS=0
CLOUD_COVERAGE_DENSITY=6
CloudsImpostorRingRadius=28800.000000
DownloadWindsAloft=0
DisableTurbulence=0
[INTERNATIONAL]
ASLAT=-1099710861
ASLON=-1099710861
MEASURE=48755
[MISC]
COM_RATE=48755
LOG_TIME=1
FOREIGN_TRANSLATOR=-1099710861
LOG_FILE=s

[garymbuska]

What were you doing at the time it happened.
I have never seen this before.

[wji]

Well, I've seen worse. The logfile is hooped but that's probably FSUIPC not doing its work (outdated version?) To fix that (make it work) open Option/Logbookbefore or during the flight and see which logbook is in use. It will (usually in this case) show this garbage; select a functioning logbook or add new logbook.

Crashing to desktop is probably the spring-thing-bug in FS9.

don't fly in the spring . . . or,

Find the TERRAIN.CFG file in the FS9 folder, open it in Notepad and replace both
MaskClassMap=1
AND
MaskClassMap=3
to
MaskClassMap=0

fly hi
bill

[PH_AJH]

thanks for the replies.
It's not just the logbook-entry though. I know that is common and it's easy to correct.  
Look at the first line: load weather should be 1 or 0, not -1099710861. A lot of values that should be 1 or 0 get these strange  numbers.
What I am doing when it happens? Nothing really. It seems to happen after closing FS2004. I end a flight the normal way, next time I try to start FS2004 it hangs on startup or crashes when I start a flight. Check the FS9.cfg and bingo: this is what I find.
What is strange too is that it happens just every now and then.

[Bazza]

If that happened to me would seriously start looking at other options ...like suicide ?

[PH_AJH]

@Bazza:
Thanks, you're a big help. It crossed my mind too, all I needed was a little push
LOL

[garymbuska]

You really got a strange problem here.  ??? Have you ever checked the fs9 cfg file after a normal flight. It sounds to me like it might be time to uninstall or reinstall. And what spring bug or we talking about I was unaware of any problems with flying in the spring.But lately fs9 crashes for no reason I thought it had something to do with a video driver update.

[PH_AJH]

Garymbuska,
The problem I have is not unknown methinks. More people have the problem with the logbook name getting altered the way you see in my "buggered file". Other people also reported unexpected other changes to their FS9.cfg so it is not really new. Some of those changes do not immediately cause FS9 to crash but this one obviously does. A reinstall is a bit over the top as all you have to do is rename the FS9.cfg to FS9.bak and FS9 creates a new file for you. M$ suggest this themselves so obviously they are aware of the problem.
What I would like to know though is why it happens. As I said earlier, it happens every now and then (the last time for me was 2 months ago and I use FS2004 most every day) so I do not think there is something very wrong with my sim all the time. My FS9.cfg is in perfect order as we speak (after several flights)

The spring-thing is about some mesh/texture combinations causing a crash-to-desktop at certain geographical locations (there is one in Switzerland) when flying in spring. This is not the problem I am experiencing.

If you have CTD's yourself I suggest you take a good look at your FS9.cfg, chances are it is buggered too  ;).
You could create a new one the way I described and compare it to your fs9.bak

Cheers
AJ