While in flight and on autopilot, if I go to make a change weather it be in views, options, aircraft or any of the choices, and then hit OK and go back to my flight, all my intial navigation input, lighting, auto pilot settings etc..have all gone away.  It's not remembering any of this. The plane noses way up and I have to adjust for that to avoid a stall and then reset everything.  I've done reinstalls, cleaned registry, deleted old flights. Nothing seems to help. this problem just came up and is now reoccuring everytime I fly. Anyone have have any idea?. The fun never seems to end.

As it turns out this problem was due to non functioning livery scripts that I added sometime ago in the aircraft cfg. folder. I deleted them out and all is back to normal once more with that problem. I am still having glideslope issue though. Cleaned out registry, reinstalled 1.3, using C172 as default before loading the 707 and still have the same issue. Glidesslope is staying at the bottom of the indicator not moving. Just on fligths more than 30 min. Oh well.

I have exactly the same problem:
"While in flight and on autopilot, if I go to make a change weather it be in views, options, aircraft or any of the choices, and then hit OK and go back to my flight, all my intial navigation input, lighting, auto pilot settings etc..have all gone away."
It started after I downloaded 1.3 and added the BOAC 300C. Prior to that, no issue. I have made no config changes nor have downloded anyother thing to my FSX and CS 707.
Any Ideas?

Kirt

Sorry, guys, I can't reconstruct the problem on my 1.3 installation.
I've changed the weather and the fuel and the AP holds the plane like before.

Can you describe your "entry points" in some more details?  :)

After installing 1.3 I added a few of Nathan's liverys and the dissappearing setting started. I deleted those additional liveries from the aircraft folder and aircraft cfg. and it's funcitoning fine again. Try deleting your BOAC and see if that helps.
Still having glideslope issues if anyone has any ideas there. Fine on flights up to 1/2 hr. but then on longer duration flights the glidescope goes on but just won't move up, down or anywhere. Cleared registry as per KB#685, did reinstall, and using a FSX default aircraft on initial load. Still no luck with the glideslope indicator.

CoolP,
When you say entry points, to what are you referring?

I was just speaking about a more detailed description of your setup and the steps your're undertaking to trigger the problem.
I'm running a lot of Nathan's fine paints too. Got nothing to report which comes close to your mentioned behaviour of the plane, sorry.

I don't have, nor have I seen, this happen.
The only thing that does happen in v1.3, that didn't in v1.2, is if I change the quantity of fuel, press OK to have the changes accepted, then I get my fuel transfer pumps close, External Air and Power turn off.

Mark

Thanks CoolP. As far as entry points, I just select a 707 model and place the plane at an airport and I see the problem. Very simple, nothing special. It sounds like Mark has seen an aspect of what is happening. Seems to be a bug where a inconsistent number of parameters are reset to default when you make changes to weather or fuel. I also find that if I have flaps down at the time, they will go up. I have reloaded 1.3 without the BOAC 300C and still see the problem. The inconsistency is interesting.

I can trigger the disconnecting external power (Mark's report) and the back to zero flaps (yours) too, when using the fuel or weather menu for example.

So far, the first item (ext. power reset) didn't harm me as I always set up my fuel load right after loading the plane, when no switch has been moved so far.
Losing the settings when altering the weather (hardly ever done by me so far) or the fuel load (never done) inflight might be an annoyance for some, agreed.
Maybe you guys can set up a ticket concerning the issue, so the thing gets on the list for the next SP.

Hmmm. Weird. I don't recall see anything happen when I changed the weather, only when I changed the fuel quantity. I shall take another look. ;)

Mark

[edit]Changing the weather and fuel, effects the following: Manifold Valve Switches, Flaps, External Power and External Air.
Using the 707-300 Cleared for takeoff (KSEA), the flaps return to the 14^o and not to the fully up position.[/edit]

I haven't had this problem reoccur again. I didn't do anything special to fix it. Seems it just fixed it's self.
I do have a problem with the whole FSX program closing with the fatal error message coming up however. This always occurs while running CS planes on FSX after about an hour of flight time. The program just shuts down while I'm opening up a new window from the menu selection.

BrianG wrote on Mar 29^th, 2011 at 2:24am:

I haven't had this problem reoccur again. I didn't do anything special to fix it. Seems it just fixed it's self. I do have a problem with the whole FSX program closing with the fatal error message coming up however. This always occurs while running CS planes on FSX after about an hour of flight time. The program just shuts down while I'm opening up a new window from the menu selection.

It is strange that your FSX crashes after about an hour of use with a Captain Sim aircraft. I can use any Captain Sim product, for FSX, for hours without any problems at all.

I did have FSX crash earlier today, but it was caused by another developers product. It was either the one I started FSX with, using one developers product, followed by switching to another developers product. I have had that happen quite often. I have found that it is better to restart FSX before switching between different developers aircraft. IF I can remember to that! ::)

Mark

Hi Mark,
There are alot of user out there who have the same problem with Payware planes running on FSX.  The default planes work fine.
Here's one solution that I'm a little hesitant to try but really want to resolve this. Check it out and let me know if you have any thoughts. I'm running Windows 7 64bit.
http://answers.microsoft.com/en-us/windows/forum/windows_7-gaming/win-7-64-bit-fsx-fatal-error-ctd-restart/14fc20fa-9dca-465b-be42-146414087ec5

Yes have also experienced FSX crash, when using the 707-300, usually  after 2 hours flighing, at anytime when changing weather, looking at the map etc. Although FSX crashes is far more frequently, when using the 727-100/200. FSX never crashes when using C-130.

That's it. do you have any ideas on a fix for it or have you researched that.

I'm almost wondering if powerful systems mess with FSX. I use FSX on a laptop, and FSX always works smoothly for me. I can set autogen at "Dense" and everything else at maximum, and the only time FSX crashes is when I take off from New York with a complex plane--pretty much anything from Captain Sim (but they work just fine elsewhere).

BrianG wrote on Mar 31^st, 2011 at 2:09am:

Hi Mark, There are alot of user out there who have the same problem with Payware planes running on FSX.  The default planes work fine. Here's one solution that I'm a little hesitant to try but really want to resolve this. Check it out and let me know if you have any thoughts. I'm running Windows 7 64bit. http://answers.microsoft.com/en-us/windows/forum/windows_7-gaming/win-7-64-bit-fsx-fatal-error-ctd-restart/14fc20fa-9dca-465b-be42-146414087ec5

Hi Brian.

That solution sounds quite good really. I might give it a try myself later (I'm in the early stages of a flight from Honolulu to Melbourne in my CS767-200).

As I said earlier, I only seem to get fatal errors when switching between payware aircraft. Before my current flight, I flew from Seattle to Honolulu in the Other 747-400, switched to the Captain Sim 767-200 without any problems. FSX has now been running for roughly 7 hours without a problem.

Mark

Hi Brian.

I have now given this a try for a couple of days and a few long haul flights. I don't recommend it. It worked OK with swapping add-on aircraft without causing a fatal error, BUT, it caused major problems for my more advanced payware add-on aircraft. I found some aircraft systems just weren't working correctly. For example:

On one flight, I was doing an autoland, I had the Autoland 3 lights up and all looked great. But as I got closer to the airport, something was really not right. I came screaming in for a landing at about VREF+40, hit the runway hard (no flare or thrust reduction). I then continued along the runway, Autobrakes were not working, reverse thrust not working, and in the end just stopped shy of the end of the runway.

Anyway, that's how I found it. I replaced the files and flew an identical flight without any problem.

Mark

Sounds like one of my normal landings!  :D

Don't say such things, Lou. Makes me think about all the TWA passengers from back in the days.
Remember that video with the bumping plane lately?  ;D

By the way, did you ever fly that old Kai-Tak approach in your career, Lou? Must have been pure fun for the residents with the loud 707 stuff passing by.

Thanks Mark,
I'll always a bit leary to try these things I read about. I was also concerned about instability that might cause on my system outside of flight sim. Anyway, I keep searching for solutions to this problem. It really takes a lot of the fun out of using these great CS planes.