Jump to content
The simFlight Network Forums

V. Heine

Members
  • Posts

    4,066
  • Joined

  • Last visited

  • Days Won

    31

Posts posted by V. Heine


  1. This version can only be used for the Microsoft FS2004 or FSX.
    This version is not compatible with Prepar3D.

    This version is neither an update nor an upgrade of the current FlightSim Commander versions 9.x.

    As before, sales are made through the companies Aerosoft (www.aerosoft.com) and SimMarket (www.simmarket.com).

    Aerosoft users who own a FlightSim Commander 9.x and use the Microsoft FS2004 or FSX can contact Aerosoft via this link
    http://support.aerosoft.com/index.php a free full version Download the FlightSim Commander 10
    and install it with your valid Aerosoft license key.

    SimMarket users who own a FlightSim Commander 9.x and use the Microsoft FS2004 or FSX
    can download a full version of the FlightSim Commander here.

    Filename: fsc10.zip

    The installation can only be done with your valid SimMarket license key.

    See also attachment at the bottom of the page
    ==================================================================================================

    Cette version ne peut être utilisée que pour Microsoft FS2004 ou FSX.
    Cette version n'est pas compatible avec Prepar3D.

    Cette version n'est ni une mise à jour ni une mise à niveau des versions actuelles de FlightSim Commander 9.x.

    Comme précédemment, les ventes se font via les entreprises Aerosoft (www.aerosoft.com) et SimMarket (www.simmarket.com).

    Les utilisateurs d'Aerosoft qui possèdent un FlightSim Commander 9.x et utilisent 
    Microsoft FS2004 ou FSX peuvent contacter Aerosoft via ce lien
    http://support.aerosoft.com/index.php une version complète gratuite
    Téléchargez FlightSim Commander 10 et installez-le avec votre clé de licence Aerosoft valide.

    Les utilisateurs de SimMarket qui possèdent un FlightSim Commander 9.x et 
    utilisent Microsoft FS2004 ou FSX peuvent télécharger une version complète 
    de FlightSim Commander ici.

    Nom de fichier: fsc10.zip

    L'installation ne peut être effectuée qu'avec votre clé de licence SimMarket valide.

    voir aussi pièce jointe au bas de la page


    ==================================================================================================

    Diese Version kann nur für den Microsoft FS2004 oder FSX verwendet werden.
    Diese Version ist nicht mit Prepar3D kompatibel.

    Diese Version ist weder ein Update noch ist es ein Upgrade der aktuellen FlightSim Commander Versionen 9.x.

    Der Verkauf erfolgt wie bisher über die Firmen Aerosoft ( www.aerosoft.com ) und SimMarket ( www.simmarket.com ).

    Aerosoft User, die einen FlightSim Commander 9.x besitzen und den Microsoft FS2004 oder FSX verwenden,
    können bei Aerosoft über diesen Link http://support.aerosoft.com/index.php eine kostenlose Vollversion 
    des FlightSim Commander 10  herunterladen und mit Ihrem gültigen Aerosoft Lizenzschlüssel installieren.

    SimMarket User, die einen FlightSim Commander 9.x besitzen und den Microsoft FS2004 oder FSX verwenden,
    können hier eine Vollversion des FlightSim Commander herunterladen.

    Dateiname: fsc10.zip

    Die Installation kann nur mit Ihrem gültigen SimMarket Lizenzschlüssel erfolgen. 

    Siehe auch Anhang hier am Seitenende

    Volker Heine
    Important notes uninstall an existing FSC eng fra ger.pdf

  2. Hello Geoff,

    I wish you a happy new year too and all the best for 2018.

    Quote

    BUT   What happens if I bring in another airway>waypoint cycle eg: Departure>waypoint airway>waypoint>dct waypoint> dct waypoint> dct waypoint>waypoint airway>waypoint>airway>dct waypoint> dct waypoint>Destination. If I use the OK button, it kills the manual fixes.

    I'll try to explain it by example
    First Route String YPPH PH H18 BURGU Y53 WENDY V279 ML
    Second Route String GEMAC N759 PEBLU Q619 LEKUS Q537 HN H328 CREEK NZGS
    Manual Waypoints BADGR FARRA

    Copy the first and the second route string together
    Result: YPPH PH H18 BURGU Y53 WENDY V279 ML GEMAC N759 PEBLU Q619 LEKUS Q537 HN H328 CREEK NZGS
    Insert a DCT between ML and GEMAC
    Now press the O.K. button
    Result: YPPH PH H18 BURGU Y53 WENDY V279 ML GEMAC N759 PEBLU Q619 LEKUS Q537 HN H328 CREEK NZGS

    Insert the manual waypoints BADGR FARRA between ML and GEMAC

    Don't use the O.K. Button. Just save the flight plan

    This plan based on Cycle 1713
    It may not work with an old cycle

    Quote

    A friend flies an A380, and said he mostly starts with a SID, then airway waypoint airway etc, then several non airway fixes while transfering to another airway,
    but not at an intersection. He (more likely his company) would have entered a series of direct to fixes and eventually, at some intersection,
    be back on an airway again then a STAR>Destination..He would do this several times on a trip. I wondered if that was a case for a route segment, not that I have ever used one

    Also this type of flight plans is possible
    I always create flight plans first with a SID and STAR and / or Transition
    Only then I insert automatic or manual waypoints

    Regards,

    Volker

     

     

     

     

  3. Hello Geoff,

    Happy New Year.

    The philosophy behind the O.K. Button has the great advantage that a route string with few intersection and Airways
    a complete route with all waypoints can be created.
    However, the route string must based from the same Airac cycle.

    The disadvantage you have shown in your post.
    For example, I use a different way.
    This shows above all the double waypoints but also has the advantage that one recognizes the lat/lon values at which waypoints can only be the right one.

    If a waypoint is recommended, but I do not see it in the variety on the map, then I use the waypoint window.
    To use your example with GOSPA. In the Waypoint window I enter GOSPA and then compare the coordinates in the Waypoint window,
    in the Flight Plan Panel and in the status bar. I realize that it can only be the FIX GOSPA.

    I hope that I could explain it understandably.

    Best regards,

    Volker

     

    FSC_9.x_2.jpg

  4. Hello Geoff,

    The O.K. Button can only be used with a route string.
    Example: Departure Intersection Airway Intersection Airway Intersection Airway etc. etc. Destination.
    YMML ML Y260 CORRS Y21 LOLLY P753 NZQN
    The O.K. Button can't be used when waypoints are entered manually.
    Example:
    YMML ML Y260 CORRS Y21 LOLLY P753 ADKOS ENRAT IPNOR AVGER GOSPA MABGA UGPED UKLAK ATVUP AGTAM LARAV NZQN
                               |------------------- O.K. Button using -------------|---------------------------- Dont't use the O.K. Button----------------------------------------------------|
    The buttons High Alt and Low Alt only activate together
    if the route string also consists of a High Alt and a Low Alt route string.


    Regards,
    Volker

    By the way. Your cycle is outdated.

    FSC_9.x_1.jpg

  5. Hello Peter,

    The use of the O.K. Button is only permitted if the flight plan complies with the following convention:
    Departure - SID - Airway - Intersection - Airway - Intersection - Airway - etc - etc - STAR - Transition - Destination.
    (see also English manual chapter 5.2.2 Airway routes).

    For flight plan that do not comply with this convention, the  O.K. Button can not be used.
    Will the the O.K. Button used anyway leads to the error described.
    A saved flight plan must correspond to the same Airac Cycle when re-loaded under which this plan was created.

    Best regards,

    Volker

     

×
×
  • 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.