Jump to content
The simFlight Network Forums

maskrider

Members
  • Posts

    62
  • Joined

  • Last visited

Posts posted by maskrider

  1. Thanks for the link.

    How many $ does EURO cost? :D And can you pay in dollars, I wonder?

    Guess those are questions best addressed over at the SimFliight FS Commander forum, eh?

    I must say that the FS Commander screen shots don't look very inviting. Doesn't seems as pleasing to the eye as FSNav. Guess it all depends what you're used to.

    Chris

  2. Hi Guys,

    I haven't been around this forum for a while. I've been doing a lot of flying in FSX and haven't really cracked open FSNav in a while- much as I love it.

    Except for the auto-altitude adjustments, auto-throttle adjustments and the ease of adding way points- several significant differences, I confess- I have become accustom to FSX and learning to fly making speed and altitude adjustments on my own. Flying IFR flight plans helps with the altitude part- most of the time- but you are right- it isn't as easy to just kick back and watch the scenery go by as it used to be.

    I am interested in this FS Commander I am hearing about. First question: what does a fully unlocked version of it go for?

    Thanks,

    Chris

  3. FYI Here is a link to a website called elbiah.de. Check out the link named Flight Simulator Tools . There is a neat pack there called MyFSTools which includes, among other neat little utilities, a utility name Tower.

    This may be old news to some, but it was welcome news to me. :D

    TOWER lets you establish and save tower viewpoints wherever you wish. So, you can slew your AC to the top of any tower at any airport and then name and save that view position!

    Tower then has an option called "Set to nearest [saved] positon automatocally". When started automatically as FS9 starts (a checkable option) Tower automatically updates the tower view to whatever your nearest saved viewpoint happens to be. Very neat.

    Here is the link:

    Elbiah.de

    Cheers,

    Chris

  4. Thanks for the info guys.

    Yeah, Avian, FSNav used with FS2K2 allows you to set the tower view to any-where/any-altitude by simply right clicking the location and choosing "set tower view to here" from the context menu- and filling in the desired altitude. Makes it great for instant replays.

    Simon, I am sorry to here that its a fact of life that this function doesn't function with FS9. Thats a drag. Oh, well. Gain a little, lose a little, I guess.

    Tx,

    Chris

    PS If I were to make a suggestion about what might be tweaked for FSNav5, I would say breath new life into the "set tower view to here" function in FS9 and beyond! :wink:

  5. Hi Dave,

    You are right- many performance profiles for add on aircraft are not included in FSNav's default listing. However, adding a new profile is no problem.

    The aircraft selection window allows you to save a perfromance profile. What I normally do when I want to add a new AC that isn't listed is to pick an aircraft from the list whose performance I expect to be similar to the add-on AC's performance.

    Then I enter the name of the add on AC in the name box of the aircraft selection window and save it. The new add on AC will then be available as a choice.

    After that a little tweaking is usually necessary to get the "borrowed" performance profile to mesh with that of the add-on's.

    Experience will show you what needs tweaking and the readme file for the add on AC will likely give most of the relavent performance parameters. Also, there is a lot of AC performance profile info available on the internet.

    Hope this helps,

    Chris

  6. Hiya everybody.

    I''ve been using FSNav and enjoying it for several years- with FS2K2. I recently built myself anew rig that will handle all of the newer sims and now have CFS2, FS2K2, FS9 and FSX loaded up. I have FSNav running successfully in both FS2k2 and FS9.

    I haven't tried loading it into FSX because I am under the impression that version 4.7 doesn't do FSX. Is that right?

    Anyway as far as I can tell FSNav is working fine with FS9 except for one small hitch. I can't use FSNav to reset the tower view in FS9 like I can in FS2K2. Is that a fact of life for everyone WRT FSNav v FS9 or is it a hitch with my particular set up?

    Thanks,

    Chris

  7. Hiya Harald

    Not a prob.

    Mind you now, I am no expert on such matters.

    I downloaded your ENZV-ENBO and loaded it up and observed the 4000 foot altitude. Then I created my own ENZV-ENBO and sure enough, for some reason- the altitude gets limited to 4000 feet even though I had set the initial flightplan altitude at 20000 feet. I guess that it is something to do with the SID/STAR but don't ask me what it could be.

    Anyway, I manually input 20000 feet at the first waypoint outside the SID green zone and this set the rest of the flight- to the desired 20000 feet.

    So, I suggest just going in and manually resetting the altitude. You might even try doing it for WPs inside the green zone and see what happens.

    Here is my "altered" ENZV-ENBO if you want to have a look see.

    Cheers,

    Chris

    ENZV-ENBO-Rev.zip

  8. Hiya Harald,

    SIDs and STARs are slippery little devils. The ones that one downloads for FSNav are mostly user designed and can vary all over the map as far as how "reasonable" they seem. Some are just flat out goofy and make "0" sense.

    Personally I have resigned myself to using other peoples SIDs and STARs as starting points for my own- if at all. If I like what I see- fine, I keep it. If I don't, I change it.

    WRT your specific question, the 4000 feet is likely just the altitude at which the SID/STAR has you joining or leaving an airway. You should be able to set the cruise altitude for anything you want it to be- but if a SID or STAR gets into the mix when calculating the final route you may find yourself limited to the altitudes specified therein until you are heading for waypoints outside the green zones of the SID or STAR.

    I guess that if you have assigned no cruise altitude for the flight you could very well find yourself limited to altitude specified in the SIDs/STARs.

    I can imagine this happening especially if the SID/STAR are either very long- covering the entire distance between departure and landing or if the distance between departure and landing is relatively short so that you are always in the green zone of the SID/STAR.

    Make choosing the aircraft and cruise altitude for the flight the first thing you do before you insert any waypoints into the flight plan.

    Cheers,

    Chris

  9. 29.92 is your basic "normal" sea leval, no weather, all things equal average air pressure. Air pressure is almost never normal.

    Try watching the SHIFT+Z altitude reading. The SHIFT+Z altitude is always the correct altitude. When you are on the ground and hit the B key the altimeter air pressure readout will immediately reset to the correct local pressure and the altimeter altitude reading will correct itself to the same altitude as your SHIFT+Z readout.

    When in the air and you hit the B key, the altimeter pressure reading will reset immediately to the local conditions but the altitude reading will take a bit longer as the autopilot- if engaged- corrects the planes' altitude.

    WRT this being something to do with FSNAV. I don't know. It seems to me it is more to do with how you are setting up your weather- manually or continuous real world online updating.

    Chris

  10. Yes, exactly. What Bob said. The control surfaces are key to getting things done. Pay attention to flaps. I think it is even permisso to touch the spoilers to a limited degree if necessary.

    One of the planes panels has a very nice flap/airspeed chart as part of the flap position indicator. It is a very nice starting point/rule of thumb for large jets.

    Chris

  11. Hehe, well all I can say is that it is really great to have so much real world piloting experience at hand in this forum. Very interesting and good advice. Expecially the part about "just fly the bird". Do whatever is necessary.

    However, let us put ourselves momentarily into the shoes of those who may sometimes find themselve, for whatever reason, "not reproducing flight as it is, but simply playing a game." :D

    I, too, suffer from this affliction from time to time.

    Ricardo49, my read on your post is that the 230knot landing spead that you see in the flight plan is the speed in the flight plan window of FSNAV and not the speed that is actually being called out in the IAS readout genrated by FSNAV in the autopilot speed window.

    The speed shown in the flight plan window for the final approach leg, as you rightly point out is higher than the landing speed called out in the aircraft specs. It is also higher than the correct landing speed being fed into autopilot/throttle by FSNAV and indicated in the IAS window. I believe that the reason for this slightly confusing situation is that the flight plan shows the speed of the aircraft at the beginning of that leg.

    Anyway, my point is that FSNAV actually does call out the correct speed in the autopilot IAS window but many times the plane is not capable of quickly moving to those indicated speed call outs when auto pilot is engaged.

    When you see that you are approaching above the indicated speed call out or just too fast, disengage FSNAV altogether or at least disengage the planes/FSNAV's auto-throttle functionality and put control of airspeed into your own hands.

    Cheers,

    Chris

  12. Thanks Ig for a heads up about "B" command! Wow! What a time saver that will be from now on.

    Just in case anyone wants to be resetting the altimeter by hand, it really helps to swap out many of the altimeters for one that is easier to read. The stock 737 has a great one. You want to be able to easily read your altitude and your dialed in barometric pressure.

    Chris

  13. Here is a simple rule that is key to successful landings using FSNav:

    Keep you altimeter adjusted!!

    :D

    Back when I was still an FSNav sprout, FSNav would either bring me in too hi or too low on strips where I could not afford to be neither- especially too hi or long on shorter runways.

    At first I figured it was just that some planes worked good and some didn't. Finally I realized that my only consistently good approaches and landings always happened when I had weather turned off. That was the only time that my on screen "SHIFT+Z" altitude and my altineter altitude reading matched up.

    I realized finally that they had too be the same. The on screen "shift+Z" altitude reading is always the "true" altitude. I finally realized that the "BAR" knob on the altimeter was actually supposed to be used for something!

    You can set it before take off- but it will usually always be different before arrival. Make sure you have it adjusted properly well before starting descent and approach if possible and keep checking it.

    The tower will give you this reading when you are asking for clearance. Many times this can be difficult to get in a timely fashion though if there are lots of airfields in the area. You can tune into the airports AIS freq well ahead of time and get the reading- as well as the open runway- info.

    If your destination airport has no AIS or Tower, get altemeter reading from the nearest available or just ayeball it by comparing your on screen to altimeter reading and making adjustments- harder to do while descending though.

    Rule of thumb:

    If the"SHIFT+Z" on screen altitude read out is higher than altimeter reading adust "BAR" knob upward- usually 1 click equals about 10 feet or 1 inch of mercury. Vice versa if the opposite is the case.

    This may be old basic beginniers news to many- but it was a real "discovery" for me.

    Of course if you are turning AP off well before landing and flying your finals by hand, your eyeball will tell you when something is out of whack. But I have found that no matter the aircraft, FSNav will give very nice finals as long as the altemeter stays properly adjusted- and the aircraft parameters are in the ball park.

    Cheers,

    Chris

  14. Hi Marcos,

    Thanks for clearing that up for me. Being strictly a simulator "flyer" I get a bit confused at times by the apparent discrepency between what some do and do not consider to be a SID or STAR. Especially trying to dope it out from some of the approach plates that I see.

    For a STAR I understand what you are saying that the procedure is for getting you from the airway to the IAF- whether the IAF is aligned with the runway or not.

    How about for a SID?

    If a STAR is for getting you from an airway to and IAF what does a SID do for you? Is it for getting from the runway to an airway? Or do you fly to some initial departure point from the runway before the SID actually begins? I guess what I am asking is what is the equivilent term for an IAF in a SID? An IDF?

    Cheers,

    Chris

  15. Hi Dennis,

    Yep, I understand what you are saying and I guess that I am not quite real world pilot enough to get a grip on the problem.

    If it were me, I would make my approach look something like this:

    fsnavexample2.jpg

    Flying in from the SW (ARNCO) thru RICCA and onto MIKEE where you then expect landing vectors to Fulton-Brown Runway 8.

    If I were making the STAR myself it would look pretty much like the screenie above with FT as a my final approach fix with a possible bearing radial coming off of ATL VOR.

    But like I said, that is how I might do it. I don't know how it would be done out in the real world.

    Cheers,

    Chris

  16. Hi Dennis,

    I will lend what assistance I can.

    You are correct of course, a SID needs a runway as a first point and a STAR needs a runway as the end point.

    Some of the navigational aids, such as VORs, DMEs and NDBs can be used as "bearing" points in your SID/STAR in stead of actual fly to waypoints.

    After you have dragged the nav aid into the FSNav plan window you can change it from a waypoint to a bearing point by right clicking on its line entry and choose "Bearing Point". You will note that the nav aid icon will change and now has a red negative sign added to it.

    You may have several waypoints that take their bearing from a particular nav aid. For each WP that uses a particular nav aid as a bearing point you will have to copy and paste that bearing point nav aid into the plan window and then drop and drag the WP into the line above that new bearing point navaid line entry.

    The pic below shows what this looks like in the FSNav screen.

    fsnavexample.jpg

    I won't go any further than this except to say that at the FSNavigator website one can download a series of excellent tutorials on how to build SIDs and STARS using FSNAV.

    As for downloading SIDs and STARS. There is a basic starter set fsnavss8.zip at the FSNav website that contains some 1500 or so SIDs and STARs. To refresh this set just click on the "options" button in the FSNav screen and shoose "download SID/STAR". Make sure before you do this that your FSX/FSNAV window is in "window" and not "full screen" mode- alt+enter.

    Thats about all I know- just learning myself- so I will leave the finer points to others more knowledgeable than I..

    Cheers,

    Chris

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.