Jump to content
The simFlight Network Forums

deetee

Members
  • Posts

    23
  • Joined

  • Last visited

Posts posted by deetee

  1. After some investigation I think I see what's going on.

     

    My copy of FSC is currently using FSX as the current nav database source.

    The VORs and NDBs quoted are also intersections but these do not appear in X-Plane, only as VOR and NDBs so XP does not recognise them as intersections.

    These 3-letter intersections (normally an intersection has 5-letters) do not appear either in the currently available 3rd party nav data (NavDataPro or Navigraph).

     

    There are 3 ways around this:

     

    1. Add X-Plane as a nav database option to FS Commander like one can do now for FS2004, FSX and P3D. (the ideal solution for XP users as FSX would not be required)

    2. Add an override option to FS Commander so that when it finds a waypoint in a flight plan such as TNT (which is both a VOR and an Intersection), that it will choose to add it as a VOR/NDB as a priority instead.

    3. Carry on as we are having to manually edit exported XP flight plans.

     

    Hope that is clear! :smile:

    Dave

  2. Hi Volker, that may be so but for an X-Plane flight plan to work they need to be set as a VOR and NDB respectively, otherwise the XP FMS will just not accept them. Please try for your self if you have XP10, otherwise please take my word for it as a user that every time I export a flight plan from FSC, I need to correct it manually before loading it into the FMS to avoid big holes in my route! :-) I would really appreciate you modifying this.

    I hope also that sometime in the future it will be possible for FSC to use X-Plane database (like Plan-G) so a copy of FSX is not required.

    Thanks again for your continued support of FS Commander, for me it's an indispensable utility!

    Dave

  3. Hi Volker,

     

    I regularly use FSC to create X-Plane flight plans and have noticed a slight problem which, when the flight plan is imported in the XP FMS, can lead to the FMS not recognising VORs and some NDBs.

    Here is an example output from FSC:

     

    I
    3 version
    0
    17
    1 EGLL 0 51.477500 -0.461389
    11 D4LON 0 51.485110 -0.573667
    11 D7LON 0 51.510150 -0.650417
    2 BUR 0 51.519010 -0.677469
    11 LON10 0 51.583750 -0.685203
    11 LON14 0 51.671620 -0.695306
    11 WOBUN 0 52.019440 -0.733333
    11 WELIN 0 52.247220 -0.852222
    11 AKUPA 0 52.486670 -1.091111
    11 TIMPO 0 52.558890 -1.163889
    11 ELVOS 0 52.700280 -1.306944
    11 TNT 0 53.053950 -1.669969
    11 RODOL 0 53.238060 -1.861944
    11 [LBA] 0 53.864990 -1.652889
    11 [iLBF7] 0 53.974590 -1.765306
    11 [LBF51] 0 53.933800 -1.766531
    1 EGNM 0 53.865830 -1.660556
     
    The 2 lines highlighted are incorrect.
    TNT is a VOR so should read:
    3 TNT
    LBA is an NDB and should read:
    2 LBA
     
    The BUR NDB near the beginning has been correctly listed so I'm not sure what's going on there.
     
     
    Anyway, these are the standard codes for X-Plane FMS files:

    1 - Airport

    2 - NDB

    3 - VOR

    11 - Fix

    28 - Lat/Lon

     
    Would it be possible to address this in an update?
     
    Many thanks
    Dave
  4. Just done a fresh install of FSX SP2.

    I mapped one of the axes of my CH yoke to the elevator trim, which works fine but messes up the AP ALT hold function.

    So I activated the "Elevator trim disconnect on AP" function in FSUIPC.

    However with the AP activated the trim axis still affects it, and wiggling the lever still moves the trim.

    I'm using FSUIPC 4.28.

    Thanks for your help.

    David.

    Edit: OK I just realised this only works if you assign the elevator trim in FSUIPC.

    Sorry about that. :oops:

    I wonder why FS does disconnect it?

  5. Hi Peter,

    When I woke up this morning I checked the log which was clean - no errors.

    I then realised that the only explanation must be a permissions issue.

    I checked "Run As Administrator" in the compatability tab for AISmooth and 737 Fuel Planner and Presto!, both worked fine.

    I should have thought of this before but hey I guess I was tired and the ole' brain was half asleep.

    Thanks for your trouble anyway, I hope at least this post serves to help others who will surely come across this issue at some point.

    Best regards and have a great Sunday.

    David

  6. Hi Peter,

    I'm having trouble running FSUIPC v4.20 on FSX with Vista x64.

    Although the program works okay within FSX, all the applications that I have tried that use FSUIPC do not connect (It's Your Plane, AI Smooth 1.20, B737 Fuel Planner). I am sure that Simconnect is okay as my TrackIR works fine.

    Have you had any trouble before running on V64?

    Your assistance would be most appreciated. :)

    Regards,

    David

  7. Hi Peter,

    I have recently been using an excellent and innovative new software called It's Your Plane by Robert Cezar.

    First of all I'm no expert but it seems to me that at launch it retrieves information from FSUIPC regarding amongst other things, the currently loaded flight plan.

    The problem is that I get an error message generated by IYP under certain conditions - seemingly when running a mission.

    Before I explain further it might save time if you read this thread (especially the 3rd post)...

    http://forums.fsaddon.eu/viewtopic.php?p=5676#5676

    I guess my question is - is it normal that when running a mission that FSUIPC uses a relative path to the PLN file rather than an absolute as it appears to do with a "regular" PLN?

    Your help would be most appreciated. :)

    Best regards,

    David

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