Bob Fiedler
-
Posts
337 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Bob Fiedler
-
-
I think your original method was correct. When you load the plan in FS9 The origin will show as the runway you have selected. When you activate the plan, you have the option of either moving to the runway or, as I do it, staying where my airplane is parked and taxiing to the runway. There is no guarentee that your selected runway is going to be the active though! Actually, I often have the parking spot as my origin. The edit-map window will always just show the middle of the airport as the origin. I never activate the plan (GPS switch and NAV1 on A/P) until I'm in the air anyway.
I also use the "previous flight" as my default flight so I'm usually already located at a parking spot when the program starts off.
Bob F.
-
I've never had any sound on changing windows. I don't think there is supposed to be any. Seems to be sort of useless unless you are visually impaired, in which case we will have to pull your license!
Bob F.
-
When you click the little airplane icon in the top menu line, a window opens with the present selection shown. There is a pull-down selection list for all the other aircraft that are loaded in the file. This file is user-updated only. New aircraft have to be entered manually in this window or by editing the file outside of FS9. Most people look for a similar aircraft and then make minor changes to suit.
If you had specified the aircraft, its likely that someone already has the data you need.
Bob F.
-
I looked through all of mine and I don't have any called "new aircraft", so I can't help you. Sorry.
Bob F.
-
On the right hand side there are menu options that light up explanations of their functions when you position your cursor over them. At least in the "docked" state. The second from the bottom is a small square and its function is "Map follows aircraft".
Bob F.
-
Would you like to know the combination to your local bank too! Are you a thief in any other part of your life?
Bob F.
-
Many of us have successful database files compiled. I've never had a problem. I attribute it to my using mostly stock scenery files. Some of the more complex files may be causing the problem. If you have some of them try disabling them one by one to see if it solves the problem. Its not a problem with the FSNavigator program!
Bob F.
-
O.K. The file you have is a .zip file. Do you have your system set to display the file extensions?
You should just be able to click on the file to expand it as seperate files.
Click on the "readme" file and read it. It describes why you have the file and how to install it.
Bob F.
-
My sids and stars are in a folder as follows:
Flight Simulator 9/modules/fsnavigator/sidstar
They are all single line file names with the extension of ".ss".
I don't recognize the file you mentioned. I got mine by activating the program module in FS9 and selecting the "download sids/stars/" from the "options menu.
Bob F.
-
WHEW!
Bob F.
-
In spite of my protestations about not wanting to retrace my steps, I did so.
I have FSNAV installed in FS9 and I extracted the elements of the program as downloaded into a new folder. I then run the setup program and the third "window" asked to click on the simulator program(s) that I wanted to install it in. Just be sure to check both or all of the programs you want to install it in.
I cancelled out of the setup at that point, but I don't see why it wouldn't work for you.
Bob F.
-
Its been a while since I, and most others here, have installed the program and I'm not going to go back and do it over just to test this answer.
The tutorial that I have says;
"The instructions are very clearly written and the program
loads beautifully, I've never had a problem. You just have to
tell it where your Flightsim is stored and which Sim you're
running - FS98 - 2000 - 2002. I'm going to be using FS2002,
but you'll be able to follow through for the other versions I'm
sure."
This indicates that there is a part of the "setup" program that allows you to designate the program that you wish to install it for. It may have a default entry which you would have to change, but I'm sure that it is possible. Many of us have it installed in both FS2002 and FS9.
Let us know how it works out.
Bob F.
-
SORRY! WRONG FORUM!
Its been a while since I, and most others here, have installed the program and I'm not going to go back and do it over just to test this answer.
The tutorial that I have says;
"The instructions are very clearly written and the program
loads beautifully, I've never had a problem. You just have to
tell it where your Flightsim is stored and which Sim you're
running - FS98 - 2000 - 2002. I'm going to be using FS2002,
but you'll be able to follow through for the other versions I'm
sure."
This indicates that there is a part of the "setup" program that allows you to designate the program that you wish to install it for. It may have a default entry which you would have to change, but I'm sure that it is possible. Many of us have it installed in both FS2002 and FS9.
Let us know how it works out.
Bob F.
-
FSNav gets its airport information from the FS9 scenery data. The FS9 data doesn't agree with the real world where 9L is now 8R, 27R is now 26L, 9R is 9 and 27L is now 27.
My question would be, where did your ATC get the real world info from?
There may be an add-on scenery for Miami that corrects the runway designations, in which case all you have to do is install that over the default and rerun the FSNAVDB program.
Bob F.
-
This is the route I get from EGLL to KJFK. Everything from Kennybunkport in is star generated.
Type: Name: Frequency: Course: Dist.: Time:
============================================================================================
Depart: Heathrow [EGLL] ATC: 123.90 0 nm 00:00
Arrive: Kennedy Intl [KJFK] ATC: 128.73 3102 nm 06:38
============================================================================================
Aircraft: Boeing 747
Cruise: 293 kts
============================================================================================
1 Depart: Heathrow [EGLL] ATC : 123.90 0 nm 00:00
--> Climb to 35000 feet.
2 Waypoint: Intersection [bUZAD] 358° 28 nm 00:05
3 Waypoint: Intersection [OLNEY] 334° 13 nm 00:02
4 Waypoint: Intersection [WELIN] 334° 8 nm 00:01
5 Waypoint: TRENT [TNT] VOR : 115.70 335° 57 nm 00:08
6 Waypoint: Intersection [RODOL] 334° 13 nm 00:01
8 Waypoint: Intersection [KOLID] 309° 38 nm 00:04
9 Waypoint: Intersection [bILVO] 309° 18 nm 00:02
10 Waypoint: Intersection [TUPEM] 308° 12 nm 00:01
11 Waypoint: Intersection [REMSI] 308° 14 nm 00:01
12 Waypoint: Intersection [MASOP] 310° 22 nm 00:02
13 Waypoint: Intersection [bESOP] 310° 45 nm 00:05
14 Waypoint: Intersection [DIMLI] 310° 47 nm 00:05
15 Waypoint: Intersection [03MCT] 309° 23 nm 00:02
16 Waypoint: Intersection [31MCT] 309° 28 nm 00:03
17 Waypoint: Intersection [MORAG] 309° 61 nm 00:07
18 Waypoint: Intersection [MIMKU] 309° 19 nm 00:02
19 Waypoint: Intersection [DOTTY] 304° 1634 nm 03:21
20 Waypoint: Intersection [TOPPS] 261° 581 nm 01:11
21 Waypoint: BANGOR [bGR] VOR : 114.80 257° 57 nm 00:06
22 Waypoint: Intersection [RAZZR] 237° 48 nm 00:05
23 Waypoint: Intersection [bRNNS] 236° 25 nm 00:03
24 Waypoint: Intersection [bOOTS] 243° 15 nm 00:01
25 Waypoint: KENNEBUNK [ENE] VOR : 117.10 241° 26 nm 00:03
26 Waypoint: Intersection [ASPEN] 216° 39 nm 00:04
28 Waypoint: PROVIDENCE [PVD] VOR : 115.60 215° 69 nm 00:08
29 Waypoint: Intersection [TRAIT] 234° 34 nm 00:04
30 Waypoint: Intersection [PARCH] 234° 14 nm 00:02
31 Waypoint: CALVERTON [CCC] VOR : 117.20 265° 32 nm 00:05
33 Waypoint: Intersection [ROBER] 230° 18 nm 00:03
35 Waypoint: Intersection [NARRO] 262° 44 nm 00:09
36 Waypoint: Intersection [ASALT] 357° 6 nm 00:01
38 Waypoint: CANARSIE [CRI] VOR : 112.30 45° 6 nm 00:01
40 Waypoint: Intersection [DMYHL] 43° 3 nm 00:00
42 Waypoint: FIX [N40 39.59', W73 47.71'] 92° 3 nm 00:01
--------------------------------------------------------------------------------------------
43 Arrive: Kennedy Intl - Rwy 13L ATC : 128.73 132° 0 nm 00:00
Runway heading 132°, altitude 13 ft ILS : 111.50
============================================================================================
Total: (10549 Lbs fuel required) 3102 nm 06:38
The speed is reduced to 204 kph just before Carnasie. Then to 180 at DMYHL and 169 on landing.
This seems doable to me.
Bob F.
-
Good news! The server is back up! I just downloaded two new ones this evening (11/22/2005). One is LFPG dated 11/03/2005 and the other is LFRH dated 10/28/2005.
Someone is doing something somewhere!
Bob F.
-
See page 12 of the users manual for the use and setting of the FMS.
It's all optional and will work with "Fly Flightplan".
Bob F.
-
On the right side of the screen there are menu icons. Its a good idea to, at least, pass your cursor over these to light up their meaning.
The one you are looking for is sixth up from the bottom and it toggles the map from flat to round,
Bob F.
-
When you return to FS, you must load the flightplan either as IFR or VFR using the "Flight Planning" menu option. Then it will appear in the GPS window and ATC will give instructions relative to it. The GPS/NAV switch must be set to GPS and the AP set to NAV for the autopilot to follow the plan. I suggest waiting until you are airborne to connect it though.
Bob F.
-
I haven't had much success with the SID/STAR download process either.
I decided to try it again just to see. VIOLA! I got three new entries listed.
They were EGNX which was created on 10/23/2005 and LHBP which was created on 9/1/2005 and LSZH which was created on 10/8/2005.
So, it looks like a little movement is being made along those lines.
All good things come to those who wait!
Bob F.
-
It is normal for the map to center on your airplane. If you move it further south the map will move north.
Bob F.
-
No! Just the NAV1 radio. The second VOR frequency would be used for manual navigation where a bearing would be significant. You can create waypoints in your flightplan by just clicking and dragging the point to the flightplan window or you can create bearing oints in the flight plan to use for new waypoint construction. But the NAV2 radio wouldn't be used.
Then again, I may be wrong as hell!
Bob F.
-
What do you mean "connect"? FSNavigator is a module that once installed requires FS2004 or FS2002, whichever it is installed in, to be active before it can be called up by the F9 key. It is impossible to run FSNavigator without the Flight Simulator program being active!
Maybe I'm misunderstanding the problem?
Bob F.
-
There are two boxes above the autopilot commands in FSNAV. One is a toggle for the autopilot and the other is "Fly Flight Plan". If you just want to let the autopilot control the airplane then the best you can do is use the NAV1 command and the autopilot will direct the aircraft to the Navaid that has its frequency in the NAV1 radio box. This will update as you fly from the frequencies in the flightplan. The waypoints without frequencies will be ignored.
The Fly Flightplan command will do lateral navigation to each waypoint in the plan. If the proper mode is selected it will also control the altitude and even the speed settings.
If you have the GPS/NAV switch in the a/p panel set to GPS then the autopilot won't work for lateral navigation either. The GPS is in control and it will follow the flightplan loaded in FS2004.
Puff! Puff!
Bob F.
Can't get a successful database creation for 4.7??
in FSNavigator Support Forum
Posted
The new version adds a couple of new items to the database that the old version didn't have. The existance and location of fueling stations and the marker beacon locations are the ones that come to mind. My version builds the database just fine and includes these items. I'm saying that there must be some incompatability with some of your add-on scenery in reguards to these items that is causing the "choke".
Or you could just ignore sensible advice and continue to bitch.
Bob F.