Okay, this is kind of odd. My 707 was working perfectly, I even stopped the blurry text in the menu (Blurry Text thread), I needed to do something outside of FSX, so I saved the flight and then loaded it when I came back to flight simulator. However, when I loaded the flight, my flight plan had un-loaded (it was replaced by the last flight plan I had used with a different airplane), autopilot was turned off and reset, all the lights (which I had turned on) were off, and both the ground textures and the menu text was blurry. What happened and what should I do?

Your flight plan was changed because the DNS automatically loads the dns.PLN every time the 707 is loaded into FSX. The 707 also seems to be returned to a Cold-n-Dark situation when it is first loaded into FSX. Other than that, I can't help you.

Mark

Thanks. This may be kind of a newbie question, but what's DNS?

DNS = Doppler Navigation System

When you first load the 707 into FSX, open the Flight Planner and you will see that there is already one loaded (KSEA - KSFF). This plan ALWAYS loads when you load the 707. Reloading the aircraft WILL reload the KSEA - KSFF flight plan and whichever other one you had will be gone. The DNS doesn't actually use the plan itself, but the plan is a MUST HAVE for the DNS to work.

My suggestion would be to pause the flight (save one included) and put everything where it needs to be for the flight to continue and load your flight plan. Once that is done, unpause FSX.

These are the main ones that you will need so your engines don't shut down:
Battery Switch ON
Bleed Air Switches ON
Manifold Valve Switches OPEN
Transfer Valve Switches OPEN (just in case you need fuel from them)

Load your flight plan. This won't be a problem if you are flying VOR to VOR. If you are flying an FS Flight Planner flight plan, you really need the default GPS 500 so you can use the menu to change the waypoint you need to head for, or it will return to the first leg of the Flight Plan, which could be a LONG way behind you.

Mark

Okay, thanks! Though it wasn't that the aircraft shut down, it was just that the lights turned off and so did autopilot. Those weren't really a problem, but I thought it was bizarre and it might have something to do with the blurring of textures, so I figured I might as well mention it. By the way, do you ever have these problems, or is it just my system/simulator/plane?

Here is how to add the default GPS 500 to the panel.cfg

[Window Titles]
Window00=Simicons
Window01=Animations Control
Window02=CS Weather Radar
Window03=Map
Window04=Autopilot
Window05=Crew Messenger
Window06=GPS

Add that line to the bottom of the list blue text

[Window06]
background_color=0,0,0
size_mm=456,378
position=2
visible=0
ident=GPS_PANEL
gauge00=fs9gps!gps_500, 0,0,456,378

Add that to the panel.cfg (putting it at the very bottom is fine (I would put it below [Window05] directly above [VCockpit01]).

To change the next waypoint in the flight plan:
Open the GPS 500 (SHIFT+7)
Click the FPL button.
Click on PUSH CRSR to turn on the cursor
Scroll down the list of waypoints until you reach the one you want to go to. Make sure it is the one that is HIGHLIGHTED!
Click on the MENU button.
Move the curser to ACTIVATE THIS LEG (I think that is what it says) if it is not already on it.
Press the ENT to activate the leg.

If any of the instructions for changing the waypoint are wrong. I will edit this post. ;)

Hope this helps.

Mark

NOTE: These changes are for the default 707 panel.cfg and NOT for the panel that uses the CIVA INS

Super, but I was wondering if you had ever encountered the problems that I'm having. I just want to be sure it's just me so that I can start digging around my computer. Thanks!

Yes I did encounter those problems. I no longer save in the middle of a flight (I only did do that once in the 707 anyway).

If I'm flying from SYD - HNL and it's going to take 10+ hours, I'll fly it for those 10+ hours. I do that with all my CS aircraft. I have flown many flights of 10 hours or more without saving mid flight. I can never get them going properly after reloading, although I think I could with the 707 if I did what I said above.

Mark

Well, I it's not only my machine, so I guess that's good and bad (bad because I can't just update my computer). I'm flying from DC to London, so I guess I could do that in one sitting. By the way, I've heard that your graphics card can overheat? Do you think that that might be happening?

No. It's not that. Although my GTX470 gets hot, I have never had it overheat. Even on hot summer days (30^oC+) it just keeps on going. And I don't have air con in my house to help keep it cool. In that situation, I'm the only thing that gets overheated. ;D

Mark

Talk about long flights...

I used to fly the 767-300 from New York to Cairo which takes around 12 hours eastbound and near 15 hours westbound.

One night I filled the CS 767 up with fuel and took off for Egypt.
After I got to cruise and set the power and checked the flight plan, I turned off the monitor and went to bed!  8-)

Next morning, I turned on the monitor and checked on my progress. Looking good! So after breakfast I got back in the seat and finished the flight.  :D

Boy, how I wish flying in the real world was that easy!

Soon, I'll give you a story about flying Cairo to JFK on a not so nice day of weather in New York.

Lou

Quote:

After I got to cruise and set the power and checked the flight plan, I turned off the monitor and went to bed!

I think I saw you on Vatsim with that one.  ;D

Hmmmm... How long would a flight from DC to London take... New York to London is 6 1/2, so I guess 8 maybe? 7? 7 1/2 If I sleep in, that's not long enough for me to leave it overnight... Does anybody know the range of the 707-300?

Anyways, thanks, all! Oh, by the way, LOU, I found your ventubo link on another forum, and that's helped a lot of the problems (it fixed everything [the original problems] until I loaded the flight  :))

It is curious why everything worked perfectly until the flight loaded. Since it appears to be not only me, I put a post in the It would be nice if... section about possibly fixing the problem.  ;D

I think the problem is saving, leaving fsx open, then loading. I just tried a few minutes ago after just opening fsx and it worked great:

---

It's odd. The problem comes and goes. It seems to get progressively worse throughout the day...

Nice pic. It depends on system, and teh editing you've doen to the product.

---

Have you ever had this problem?

Markoz wrote on Feb 26^th, 2011 at 2:58am:

DNS = Doppler Navigation System When you first load the 707 into FSX, open the Flight Planner and you will see that there is already one loaded (KSEA - KSFF). This plan ALWAYS loads when you load the 707. Reloading the aircraft WILL reload the KSEA - KSFF flight plan and whichever other one you had will be gone. The DNS doesn't actually use the plan itself, but the plan is a MUST HAVE for the DNS to work. Mark

Thank you Mark,

Captain Sim,
I submitted a ticket on this issue after upgrading to V1.3 a few days ago and not finding any information in the KB or manuals. Your reply was in no way referenced to this fact. Why not?

The 2nd issue (undercarriage) was not addressed either and finished up getting that sorted after my 4th install attempt after clearing the registry, as I had been doing, but this time using CrapCleaner as well.

Your support system really needs a makeover!

Lost in Isaan wrote on May 10^th, 2011 at 5:04am:

The 2nd issue (undercarriage) was not addressed either and finished up getting that sorted after my 4th install attempt after clearing the registry, as I had been doing, but this time using CrapCleaner as well.

In any case reinstall was the thing that helped, and this was what we asked you to do. Unfortunately we cannot forsee all problems which may arise on each particular computer.

And speaking of DNS, every time I run it ( it works great) and it comes time to land and I pick out a ILS approach, the localizer works great and the glideslope comes on but stays at the bottom of the scale and does not move up in relationship to the plane approaching the runway. This only happens when I have previously used the DNS. When i don't use the DNS, the glideslope indicator works fine. Does anyone have any insight into this problem. Thanks so much.
BTW. I've done a reinstall and cleaned out the registry but I still have the problem.

Have you turned the DNS OFF (Function Selector Switch) on the OH panel?

On the DNS panel on the Forward Aisle Stand, what position is the NAV Controller switch in, on the Doppler Navigation Controller?
I'm not sure if this helps, but the G/S indicator was visible after I switched it to MAN or STBY.

Mark

---

Hi Mark,
Thanks for your reply. Yes, on the over head panel I did turn the DNS power switch to off, and once I had my ILS dialed into to Nav 1 I turned the auto pilot from Nav to heading. And still no luck in getting the glideslope indicator to move from the bottom of the scale. Did you have a similar problem when using doppler?
I always use to auto pilot controll from shift + 5. Maybe I should take a look on the forward isle panel to make sure it's coinciding correctly?

And still no luck in getting the glideslope indicator to move from the bottom of the scale.
I am able to see the Glide Slope indicator without a problem, I'm not absolutely sure that switching the NAV Controller to MAN or STBY was the key. It could have been a coincident. Switching the NAV Controller to OFF might be an even better idea.

Did you have a similar problem when using doppler?
No. It's work correctly for me.

I always use to auto pilot controll from shift + 5. Maybe I should take a look on the forward isle panel to make sure it's coinciding correctly?
Whether I use the A/P 2D panel (shift+5) or the A/P on the Aisle Stand in the VC, doesn't make any difference mine.

Mark

I did turn the nav controller to off and turned it off on the over head panel as well. Again the glideslope will come on but not move from the bottom of the scale.  I put in a fix ticket and the support team said they couldn't replicate the problem on their end. OH well
Maybe it has to do with the way I'm loading the 707 from the start? How do you load yours when you're starting out?

One of several ways.
1) Go to Documents\Flight Simulator X files and start FSx by double clicking on 707-300 Cold-n-Dark (KSEA) or 707-300 Cleared for takeoff (KSEA)
2) Start FSX and Load 707-300 Cold-n-Dark (KSEA) or 707-300 Cleared for takeoff (KSEA), then click Fly Now.
3) I start from the Free Flight with the 707-300 at whatever ever airport I choose and start a flight that way.
4) After flying with another aircraft, change over to the 707-300 and continue flying from there.

These are probably all the ways to start a flight. Sometimes things go wrong when I use method 4. Switching from one payware aircraft to another can cause a fatal error in FSX. Not often, but it does happen.

Mark

Hi Mark,
I finally figured this out. Maybe it's in the manual and I over looked it. When I have my ILS dialed in and I'm done with the doppler I simply switch the auto pilot from Nav to Navloc. Then I can turn it off or used to auto pilot for landing and the glideslope functions as it should. And that takes care of the glideslope issue. I'm not sure if the real 707 operated this way but it works for me. Nice to have that resolved.