I bumped up my hardware to run at 200mhz. fsb, and effective 400mhz. on my dual channel memory, and my system runs fine, no hangs, no heat problems, no voltage issues....BUT my PIC is acting quite strangely! I start the sim using a saved flight ( i start using fsautostart utility), then I switch to whichever other saved flight I want to start my flight with, and none of the settings come up right. In other words, if I choose a saved flight at the gate at another airport, my panel comes up in "dark" status - unlike it was saved using a typical parked at gate setting with power/apu running, just no start up actions taken. Also tried picking one of my saved flights, which was in the STAR to KPHX, and it loaded totally "dark" on me, so I fell from the sky trying to get the darn thing up with engines running. If I use the defualt flight that the sim starts up with, I am good to go, and the flight is smooth as silk. Only when I try and choose one of my other saved flights does the fun begin. If I switch to my default settings for my cpu/mobo/memory..everything works fine.. I am not so much looking for a resolution, just wondering if anyone else ever experienced this when changing their system settings, and bumping up speeds. Good day to all,Neil :-wave

Try saving a flight with the new hardware settings. Then see what happens with this new saved flight.

Mark,Tried it a couple of times over the last few days with no luck - it's just plain screwy! I can't figure why this is happening, but I do know I am going to turn my system down to 166 fsb, and 333mhz memory speed, and see if it tames the lion. Nothing else on my system is wigging out, just my saved flight parameters in PIC. I have made NO changes to PIC settings or anything else, so I can only assume the system changes are driving the issue. Weird!!! :-hmmm Thanks Mark,Neil

Are you actually overclocking the system doing that or is you CPU, RAM, and mobo rated to run at 400? If you're OC'ing, things can *seem* fine, but when you start doing certain apps, games, you'll get instability.

Actually, the XP3000+ is rated at 333mhz, the mobo - nvidia nForce II Ultra 400 (A7N8X) can handle the 400mhz dual channel PC3200ddr. I have like 3 different monitoring programs running and everything has been rock steady. But I will try clocking it back down a bit as I mentioned earlier, and see what happens...Neil

I have an overclocked system, on which EVERYTHING runs fine.From FS, to SuperP.For days.FS can't be smart enough to save a flight: each time i save and reload a flight something is always screwed up.And i am not talking about some fancy addon, but default aircrafts!Eighter engines off, screwed lat/long coords (ending up in a different point)...Never never what i saved.Bringing the cpu down to its default clock speed did nothing.I don't have a solution, just saying you're not alone :(

ERUPS,WOW! You too? :-eek Not to make my post lengthy, but I do want to explain. I too tried to bring the clock back down to defualt, but it's too late. ALl of my saved flights are corrupted in some way. They all start me in the right place, whether it being at one of my 30 start locations at an airport gate, or one of my STAR startign points - BUT my panel set-ups are not as they once were. My saved flights that are set as parked at a gate - the cockpit is dark, with the overhead strangely all switched ON..Or..the saved flights begining in a STAR are not dark, but my overhead is all switched OFF, so I fall from the sky. Damn strange. Only a few of my saved STAR flights are ok, but don't have the flightplan loaded any more as it was saved. All this happened because of resetting my machine speeds? What is it that exactly got corrupted? How? Why? Never thought this could happen. BUT,,,if I load a copy of my saved flights from a backup CD taken a week or so before I made system changes, you think that will work ok??? This just boggles my mind, since every other aspect of flightsim, flying, and other PC operations show no sign of corruption in any way....:-rollHappy Flying,Neil

I would not account for the overclocking.Otherwise it would mean that MS has put some overclocking detection code in FS:my system saw 2 different cpus, overclocked to different speeds, and clocked to default too.Never had a decent save.In my particular case it is not a problem as i almost never save, but the problem is there nevertheless.I doubt we are the only 2 in the world overclocking their systems, so it may well be something else :(