Jump to content
The simFlight Network Forums

V. Heine

Members
 View Profile  See their activity

  • Posts

    4,066

  • Joined

  • Last visited

  • Days Won

    31

 Content Type 

Posts posted by V. Heine

    Problem with non-unique navaid codes

    in (Former) FS Commander Support Forum

    Posted

    Hi Phil,

    we have tried to somehow verify the problem you described, but unfortunately we could find any abnormal behavior of the flight planner. Of course, when flight plans are loaded, we not only check the ICAO code, but also the corresponding lat/lon values, since navaid names can be geographically ambiguous.

    In order to help you, I suggest the following. Please create the original plan again and save it. Then reload the plan and save it again under a different name. Send the two plans to Volker (his email address is on our homepage). We will check what is happening.

    Regards

    Sascha & Volker

    User Objects

    in (Former) FS Commander Support Forum

    Posted

    Hi Geoff,

    and below are the format description for the userobj.txt, found also inside the file userobj.txt.

    Regards,

    Volker

    # This file contains user-defined map objects to be shown in

    # FlightSim Commander. To define objects in these file, the

    # following rules apply

    #

    # The symbol '#'at the beginning of a line identifies a comment.

    # The line will be ignored when FS Commander reads the file.

    #

    # There are three types of objects you can define: lines, filled

    # polygons, and unfilled polygons.

    #

    # A line is a sequence of points where the first and last points

    # are different. Lines would typically be used for Rivers, roads,

    # etc.

    #

    # A polygon is a sequence of points where the first and last

    # points are identical. A polygons thus shows a closed surface.

    # Polygons would typically be used for Lakes islands, and the like.

    #

    # In a filled polygon the enclosed surface has the same color as

    # the border. In an unfilled polygon the enclosed surface is

    # transparent.

    #

    # For both lines and polygons you can choose a color. The color

    # must be specified in the RGB format; i.e. by three consecutive

    # numbers ranging from 0 to 255 specifying the colors red, green,

    # and blue part. E.g. 0,0,0 is black; 255,255,255 is white,

    # 0,255,0 is green, etc

    #

    # Each object has in its first line a header which specifies the

    # type of object. 'l' stands for line, 'fp' for filled polygon,

    # 'up' for unfilled polygon. The comma is used as a delimiter.

    # The first number is the line width which can be 1 (thin),2 (medium),

    # or 3 (thick). The following three numbers specify the color.

    # Thus

    # l,3,0,0,0 would be a thick black line

    # up,1,0,0,255 would be a blue unfilled polygon with a thin line

    # fp,1,255,255,255 would be a white filled polygon with a thin line.

    # (actually line width in a filled polygon is irrelevant because

    # you don't see it.)

    #

    # If you like, you can use capital letters; so L,0,0,0 would also

    # be fine.

    #

    # Each header is followed by a variable number of points. Each point

    # is defined by its latitude and longitude in that order. CRUCIAL:

    # latitude and longitude must be given in decimal notation where

    # north and east are positive and south and west are negative.

    # E.g. 50.5,-123 would be N50°30' W123°.

    #

    #

    # The following two examples illustrate the basic mechanism. Delete

    # these examples, if you do not need them.

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