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

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

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

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

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.

Mark

Quote:

I think I saw you on Vatsim with that one. 

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:

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

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


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!

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.

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?

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?

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.