• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX Radar Stand Off/ Panning display aspects .

Messages
542
Country
australia
I have a Radar display that can be selected to provide different views ,

1. "Normal view" , based on aircraft's present position ,
(A:pLANE LATITUDE,degrees)/(A:pLANE LONGITUDE,degrees)

or,

2. "Stand Off view" , based on any Flight Plan Waypoint position ,
this is a position that is generally geographically distant from my aircraft ,
(A:GPS WP NEXT LAT,degrees)/(A:GPS WP NEXT LON,degrees)

This selectable view arrangement was discussed at the following link ,
http://www.fsdeveloper.com/forum/showthread.php?t=427000

As can be seen the " Stand Off " view has the following limitations ,
- Must have a Flight Plan loaded .
- If no Flight Plan exists then the Radar Stand Off display is blank and shows
' No Flight Plan Loaded ' text .
- Worst of all , the Stand Off display was totally limited to showing terrain etc
imagery of 'Waypoints' that were contained in a Flight Plan.

While the Stand Off application provided powerful uses for both information and Flight Planning purposes , it's limitations were a source of annoyance.

I wanted a setup that removed all limitations , and that could provide complete global Radar display views of any place on earth , and could do so even if no flight plan existed .

I have achieved the above by replacing the Stand Off basis ,
From
(A:GPS WP NEXT LAT,degrees)/(A:GPS WP NEXT LON,degrees)
To
(L:RequiredWaypointLatitude, degrees)/(L:RequiredWaypointLongitude, degrees)

I now have 4 conditions ( or pages ) that provide this Lat/Long to the Radar Stand Off display view , as follows .

B.1 - 'SELECT FLT PLN SEQ' - any flight plan Index/SEQ number is set at thumbwheel , then SET , it will display at appropriate waypoint location , this function can be used when flying the plan on autopilot without resetting the Active Leg .

B.2 - 'ENTER POSITION' - any location on earth can be entered with the keyboard as a Lat/Long or Airport ICAO , then set , it will display on the Radar , these locations are totally independant of flight plan and can be made even when no Flt Pln exists.

B.3 - 'ACTIVE WPT' - this is the old system ,
(1) normally it will progress or step through the flight plan SEQ/Index numbers displaying the next waypoint as the flight progresses.
(2) by setting any other SEQ number WILL make that the "Active Leg" , and the autopilot will turn to honor that Active Leg .
however the applicable waypoint will show on the Radar in either instance.

B.4 - PAN VIEW POSITION - by setting 'DIST' (distance) and 'BRG' (bearing) the Radar view will be displaced accordingly from the user aircraft ,
Example : set a distance of 60 nm , the view moves forward to that distance , then 'INC' (increase) bearing and the view will go around in a circle at a constant 60 nm from the aircraft , I currently have the distance rang set at
0-300 nm.

It now provides a greater degree of flexability .
The following shot shows the 4 control functions ,

cb7zR.jpg
Stand Off.jpg


My problem now is ,
the Radar text when no flight plan exists , the previous code was ,

HTML:
    <!--III  No flight plan exists : blank page--> 
            <Element id="Advisory_Data">
              <FloatPosition>0.000,0.000</FloatPosition>
                <Visibility>(@c:FlightPlanIsActiveFlightPlan)  0 ==</Visibility>
                <Element id="LEG_Data">
                    <FloatPosition>0.000,42.000</FloatPosition>
                    <GaugeText id="Fltpln_NIL">
                        <BackgroundColorScript>0x000000</BackgroundColorScript>
                        <FontColorScript>0x349F34</FontColorScript>
                        <FontFace>Tahoma</FontFace>
                        <FontHeight>16</FontHeight>
                        <Tabs>0L,40L</Tabs>
                        <GaugeString>\n\n\n\t%NO%
                                \n\n\n\t%FLIGHT  PLAN%
                                \n\n\n\t%LOADED                         
                        %</GaugeString>     
                        <Length>350</Length>
                        <Size>350,270</Size>
                        <Bright>True</Bright>
                    </GaugeText>
                </Element>
            </Element>

I now need a visability statement for the 2 control funtions that are flight plan reliant to show the text when no flight plan exists , the other 2 control functions are independant of flight plans therefore do not need the text.
The following is what I am after ,

HTML:
<Visibility>
(@c:FlightPlanIsActiveFlightPlan)  0 == (L:StandOff mode,enum) 1  ==  and
OR
(@c:FlightPlanIsActiveFlightPlan)  0 == (L:StandOff mode,enum) 3  ==  and
</Visibility>

How do I write that visability statement ?

Cheers
Karol
 
Last edited:
Messages
542
Country
australia
Finally got it working ,

HTML:
<Visibility>
(@c:FlightPlanIsActiveFlightPlan)  0 == (L:StandOff mode,enum) 1  ==  and
				
(@c:FlightPlanIsActiveFlightPlan)  0 == (L:StandOff mode,enum) 3  ==  and 
  or
 </Visibility

The ' No Flight Plan Loaded ' text now shows on the Radar in Stand Off if
no Flt Plan exists and only displays when control pages B.1 and B.3 are selected , thats as was required .

Cheers
Karol
 
Messages
542
Country
australia
For information purposes.

The following is the functional code for the Radar display PAN FUNCTION as is used in the above shot.
It may be of interest to anyone wanting to add a simple PAN capability to a Radar.

*****
CUSTOM DRAW

OPTION ONE

HTML:
<CustomDrawParam id="Latitude" Name="Latitude">
                            <Value>(L:RequiredWaypointLatitude, Radians)</Value>
                        </CustomDrawParam>

                      
<CustomDrawParam id="Longitude" Name="Longitude">
                            <Value>(L:RequiredWaypointLongitude, Radians)</Value>
                        </CustomDrawParam>

OPTION TWO
Based on post #12 by Tom at above link

HTML:
<CustomDrawParam id="Latitude" Name="Latitude">
                            <Value>(A:PLANE LATITUDE,Radians) (L:RequiredWaypointLatitude, Radians) (L:Toggle_ViewSW,enum) 1 != ?</Value>                      
</CustomDrawParam>
                      

<CustomDrawParam id="Longitude" Name="Longitude">
                            <Value>(A:PLANE LONGITUDE,Radians) (L:RequiredWaypointLongitude, Radians) (L:Toggle_ViewSW,enum) 1 != ?</Value>
                      
</CustomDrawParam>

with Switch
(L:Toggle_ViewSW,enum)  !   (&gt;L:Toggle_ViewSW,enum)

OPTION THREE
Two Custom draw sections with a switch that toggles between
the two sections.

***************
UPDATE SECTION
( Edit; update code corrected as mentioned at post #6 below )
HTML:
<!-- GEOCALC with the DIST and BRG that are set it calculates the PAN position Lat/Long that is used in the CUSTOM DRAW -->
(L:StandOff mode,enum) 4 ==
         if{
           (A:PLANE LATITUDE, degrees) (>C:fs9gps:GeoCalcLatitude1, degrees)
                        (A:PLANE LONGITUDE, degrees) (>C:fs9gps:GeoCalcLongitude1, degrees)                          
                        (L:DistMove,nmiles) (>C:fs9gps:GeoCalcLength, nmiles)                      
                        (L:ViewBrgAngle,degrees) (A:GPS GROUND TRUE TRACK, degrees) + dnor (>C:fs9gps:GeoCalcAzimuth1, degrees)
                        (C:fs9gps:GeoCalcExtrapolationLatitude, degrees) (>L:RequiredWaypointLatitude,degrees)
                        (C:fs9gps:GeoCalcExtrapolationLongitude, degrees) (>L:RequiredWaypointLongitude,degrees)
            }  

<!-- Initialises the startup default Bearing -->
    (L:StandOff mode,enum) 4 == (L:ViewBrgAngle,degrees) 0 == and
         if{
            360 (&gt;L:ViewBrgAngle,degrees)
            }


***************
DISPLAY DATA SCREEN
(could be incorporated into a Radar)
The background Bitmap of the MFD in above shot is size 228 x 205 .

HTML:
<!-- OOO START  PAN POSITION OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO -->  
<Element>
      <Visible>(L:StandOff mode,enum) 4 ==</Visible>
      <Element>
        <Position X="0" Y="105"/>
        <FormattedText X="20" Y="70" Font="Gloucester MT Extra Condensed" FontSize="9" LineSpacing="10" Adjust="Left" Color="#93FF72" Bright="Yes" Tabs="0,14C">
          <String>\tRET\n\n\n\n\n\n\tMNU\n</String>
        </FormattedText>
      </Element>    
      <Element>
        <Position X="0" Y="16"/>
        <FormattedText X="228" Y="162" Font="Gloucester MT Extra Condensed" FontSize="9" LineSpacing="10" Adjust="Left" Color="#93FF72" Bright="Yes" Tabs="0,207">
          <String>\n\n\n\n\n\n\tINC\n\n\n\tDEC\n\n\n\tINC\n\n\n\tDEC\n</String>
        </FormattedText>
      </Element>    
        <Element>
          <Position X="52" Y="6"/>
          <FormattedText X="127" Y="9" Font="Tahoma" FontSize="8" LineSpacing="9" Adjust="LEFT" Color="#349F34" Bright="Yes">
            <String>%B.4 : PAN  VIEW  POSITION >>%</String>
          </FormattedText>
        </Element>
<!-- User aircraft current Lat/Long -->
        <Element>
          <Position X="32" Y="26"/>
          <FormattedText X="130" Y="35" Font="Tahoma" FontSize="10" LineSpacing="15" Adjust="Left" Color="#206220" Bright="Yes">
            <String>%A/C LAT  :  %((L:ACPOS, number))%{case}%{:0}%((A:PLANE LATITUDE, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % flr r flr 'N' 'S' l0 ? )%!s!%!02.0f!%\{dplo= } %!02.0f!%' %!02.0f!%"%{:1}%((A:PLANE LATITUDE, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % r flr 'N' 'S' l0 ? )%!s!%!02.0f!%\{dplo= } %!07.4f!%' %{:2}%((A:PLANE LATITUDE, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % r flr 'N' 'S' l0 ? )%!s!%((A:PLANE LATITUDE, degrees) abs )%!09.6f!%\{dplo= }%{end}\n
                    %A/C LONG  :  %((L:ACPOS, number))%{case}%{:0}%((A:PLANE LONGITUDE, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % flr r flr 'E' 'W' l0 ? )%!s!%!03.0f!%\{dplo= } %!02.0f!%' %!02.0f!%"%{:1}%((A:PLANE LONGITUDE, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % r flr 'E' 'W' l0 ? )%!s!%!03.0f!%\{dplo= } %!07.4f!%' %{:2}%((A:PLANE LONGITUDE, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % r flr 'E' 'W' l0 ? )%!s!%((A:PLANE LONGITUDE, degrees) abs )%!010.6f!%\{dplo= }%{end}
            </String>
          </FormattedText>
        </Element>
      
      <Element>
         <Position X="32" Y="63"/>
         <Polygon Color="#1D581D" LineWidth="0.1" Bright="Yes">
           <Point X="0" Y="0"/>
           <Point X="120" Y="0"/>
         </Polygon>
      </Element>      

<!-- Current PAN  Lat/Long  position-->    
        <Element>
          <Position X="32" Y="66"/>
          <FormattedText X="130" Y="35" Font="Tahoma" FontSize="10" LineSpacing="15" Adjust="Left" Color="#349F34" Bright="Yes">
            <String>%PAN LAT  :  %((L:ACPOS, number))%{case}%{:0}%((L:RequiredWaypointLatitude, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % flr r flr 'N' 'S' l0 ? )%!s!%!02.0f!%\{dplo= } %!02.0f!%' %!02.0f!%"%{:1}%((L:RequiredWaypointLatitude, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % r flr 'N' 'S' l0 ? )%!s!%!02.0f!%\{dplo= } %!07.4f!%' %{:2}%((L:RequiredWaypointLatitude, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % r flr 'N' 'S' l0 ? )%!s!%((L:RequiredWaypointLatitude, degrees) abs )%!09.6f!%\{dplo= }%{end}\n
                    %PAN LONG :  %((L:ACPOS, number))%{case}%{:0}%((L:RequiredWaypointLongitude, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % flr r flr 'E' 'W' l0 ? )%!s!%!03.0f!%\{dplo= } %!02.0f!%' %!02.0f!%"%{:1}%((L:RequiredWaypointLongitude, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % r flr 'E' 'W' l0 ? )%!s!%!03.0f!%\{dplo= } %!07.4f!%' %{:2}%((L:RequiredWaypointLongitude, degrees) d 0 &gt;= s0 r abs d 3600 * 60 % r d 60 * 60 % r flr 'E' 'W' l0 ? )%!s!%((L:RequiredWaypointLongitude, degrees) abs )%!010.6f!%\{dplo= }%{end}%
            </String>
          </FormattedText>
        </Element>

            <Element>
              <Position X="26" Y="103"/>
              <FormattedText X="50" Y="12" Font="Tahoma" FontSize="10" LineSpacing="12" Adjust="LEFT" Color="#349F34" Bright="Yes">
                <String>-%RESET%</String>
              </FormattedText>
            </Element>      
<!-- Readout of current  PAN Distance and Bearing -->
        <Element>
          <Position X="36" Y="124"/>
          <FormattedText X="75" Y="30" Font="Tahoma" FontSize="10" LineSpacing="15" Adjust="LEFT" Color="#349F34" Bright="Yes">
            <String>%DIST  :  %((L:DistMove,nmiles))%!03d!% nm%\n
                    %BRG  :  %((L:ViewBrgAngle,degrees))%!03d!\{dplo= }%</String>  
          </FormattedText>
        </Element>          
<!-- Arrow points from aircraft to Pan position -->      
   <Element>
          <Position X="135" Y="140"/>
            <Polygon Color="#206220" FillColor="#206220" LineWidth="1.5" Bright="Yes">
               <Point X="0" Y="12"/>
               <Point X="0" Y="0"/>
               <Point X="3" Y="0"/>
               <Point X="0" Y="-10"/>
               <Point X="-3" Y="0"/>
               <Point X="0" Y="0"/>
            </Polygon>
           <Rotate>
             <Value>(L:ViewBrgAngle,radians)</Value>
           </Rotate>
      </Element>      
            <Element>
                <Position X="175" Y="56"/>
              <FormattedText X="86" Y="125" Font="Tahoma" FontSize="8" LineSpacing="29" Adjust="LEFT" Color="#349F34" Bright="Yes" Tabs="0,1L">
            <String>%DIST -\n
                     DIST -\n
                     BRG  -\n
                     BRG  -\n%</String>
          </FormattedText>
            </Element>      
        <Element>
          <Position X="26" Y="164"/>
          <FormattedText X="65" Y="12" Font="Tahoma" FontSize="8" LineSpacing="10" Adjust="LEFT" Color="#CC9900" Bright="Yes">
            <String>%- BACK TO MENU%</String>
          </FormattedText>
        </Element>          

</Element>  
<!-- OOO END  PAN POSITION OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO -->


***************
SWITCHES

HTML:
<!-- DISTANCE increase and decrease -->  
<!-- the 301 and 300 set max range at 300nm  ,  if max range of 60 nm requires the values would be  61 and 60 -->  
(L:StandOff mode,enum) 4 ==
                if{
                (L:DistMove,nmiles) 1 + (>L:DistMove,nmiles) (L:DistMove,nmiles) 301 == if{ 300 (>L:DistMove,nmiles) }
                }       
      
(L:StandOff mode,enum) 4 ==
                if{
                (L:DistMove,nmiles) 1 - (>L:DistMove,nmiles) (L:DistMove,nmiles) -1 == if{ 0 (>L:DistMove,nmiles) }
                }       
<!-- BEARING  increase and decrease -->          
(L:StandOff mode,enum) 4 ==
                if{
                (L:ViewBrgAngle,degrees) 1 + (>L:ViewBrgAngle,degrees) (L:ViewBrgAngle,degrees) 361 == if{ 1 (>L:ViewBrgAngle,degrees) }
                }       
      
(L:StandOff mode,enum) 4 ==
                if{
                (L:ViewBrgAngle,degrees) 1 - (>L:ViewBrgAngle,degrees) (L:ViewBrgAngle,degrees) 0 == if{ 360 (>L:ViewBrgAngle,degrees) }
                }      
<!-- RESET , this resets both PAN Distance and bearing values back to zero -->      
(L:StandOff mode,enum) 4 ==
                 if{
                 0 (>L:DistMove,nmiles)
                 0 (>L:ViewBrgAngle,degrees) }

<!-- Cycles through the 3 Lat/Long readout formats of both Aircraft and PAN position -->
(L:ACPOS, number) ++ 3 % (&gt;L:ACPOS, number)

Cheers
Karol

ADDED NOTES :
1. It is recommended that PAN distances Max values be set at multiples of 60 nm to take advantage of the 1 in 60 Rule of Thumb .
ie;
- at 60 nm - a 1 degree change in either Heading or Bearing results in a 1nm lateral translation of Pan position view.
- at 300 nm - a 1 degree change in either Heading or Bearing results in a 5 nm lateral translation of Pan position view.
If the flight is Paused it provides two distance measures : * Aircraft to Pan distance , and
* the 1 in 60 Rule arc distance of the circle prescribed by changes in the Bearing value.
At times that can be a useful distance measure .
2. In straight line flight the Pan position translates over the Radar terrain at the Aircraft's Ground Speed .
3. The Bearing readout value and arrow indicator are relative to the aircraft nose , it is not a heading .
ie; if DIST = 100 nm and BRG = 090 the PAN view will be 100 nm to your right side , and the Pan view will change with turns .
 
Last edited:
Messages
1,564
Country
thailand
Karol,

It's always nice to see your innovative gps and map work. Keep it coming.

Bob
 
Messages
542
Country
australia
Hi Bob

Thank you for your comments , they are very much appreciated .

It is an interesting setup , fortunately I retained both ,
- the " On Keys " structure , and
- the " keyboard register " structure .
as I had used in 'ICAO' and 'LAT/LONG' view pages of the 'Flight Plan Editor' .

That resulted in some rather neat advantages ,

(1) With the " B.2 - 'ENTER POSITION' " Stand Off controller page , I can make any of the 5 entries possible , then set one of those entries and it's location will appear on the Radar screen when mode 6 is selected , that function is independant of any flight plan that may or may not exist .
Having made and set a position in the B.2 page , I can then navigate back to the LAT/LONG page of the 'Flight Plan Editor' and the previously made position entry is still present , therefore it can be entered into a Flight Plan as
either of ADD - DTO - REP depending on 'Entry Mode' selected .

(2) With all " B.1 , B.2 , B.3 , B.4 " Stand Off controller pages , I can use the
Radar touchscreen facility and click anywhere on the Radar screen to nominate a position location , then likewise navigate back to the LAT/LONG page and enter that position into a Flight Plan as ADD -DTO -REP .

Those capabilities are handy if you wish to create diversions or modifications or DTO at a distance from your aircraft , and generally that would be where you would be doing that sort of activity .

I enjoy the Touchscreen nomination facility , especially when using it repeatedly to leapfrog across the countryside in Stand Off mode , then clicking on a Airport icon and then being able to zoom in and see the runway layout detail.

I just now had a thought about a improvement to all controller pages ,
each should have a button that instantly snaps back directly to the LAT/LONG page to facilitate a Flight Plan entry .
It's just to make it more user friendly .

One other thought that I have been having lately is about the Touchscreen position nomination , not sure if it's possible , but ,
It would be neat to have a selectable mode function as follows ;
1. Lat/Long
2. Airport
3. VOR
4. NDB
5. Intersections .

Select your " Click mode " .
For 2 -5 it would Pick up both 'Location and Identifier' , which would then be available for entry in that format into a Flight Plan .

I do have a tendancy to get carried away with ideas .
Perhaps I should stop thinking !

Cheers
Karol
 
Messages
542
Country
australia
CORRECTION

I made a double error that negated itself !
The error is in the above "GEOCALC Update section.
Below , please find the 'correct' update section .

This is the line that was incorrect ,

HTML:
(L:ViewBrgAngle,degrees) (A:GPS GROUND TRUE TRACK, degrees) + (A:GPS MAGVAR, radians) + dnor (>C:fs9gps:GeoCalcAzimuth1, degrees)

Error 1 : The " MAGVAR " should not have been included , it's superflous as it is already taken into account in "A:GPS GROUND TRUE TRACK' .

Error 2 : Thoughtlessly I mixed a "radians" in a GEOCALC that was being conducted with " degrees " ( that's what negated it's effect , and thus hid the error , it's just plain wrong )

My apologies for any inconvenience .

The following is correct .


HTML:
[HTML]		   
(L:StandOff mode,enum) 4 ==  
         if{
(A:PLANE LATITUDE, degrees) (>C:fs9gps:GeoCalcLatitude1, degrees)
(A:PLANE LONGITUDE, degrees) (>C:fs9gps:GeoCalcLongitude1, degrees)							
(L:DistMove,nmiles) (>C:fs9gps:GeoCalcLength, nmiles) 
						(L:ViewBrgAngle,degrees) (A:GPS GROUND TRUE TRACK, degrees) + dnor (>C:fs9gps:GeoCalcAzimuth1, degrees)
						(C:fs9gps:GeoCalcExtrapolationLatitude, degrees) (>L:RequiredWaypointLatitude,degrees)
						(C:fs9gps:GeoCalcExtrapolationLongitude, degrees) (>L:RequiredWaypointLongitude,degrees) 
			}
[/HTML]

Cheers
Karol
 
Messages
1,564
Country
thailand
One other thought that I have been having lately is about the Touchscreen position nomination , not sure if it's possible , but ,
It would be neat to have a selectable mode function as follows ;
1. Lat/Long
2. Airport
3. VOR
4. NDB
5. Intersections .

Select your " Click mode " .
For 2 -5 it would Pick up both 'Location and Identifier' , which would then be available for entry in that format into a Flight Plan .

Certainly, and that can all be done with "Touchscreen"-like mouse clicks - that is, to the extent that the mouse is an acceptable enough proxy for one's finger. I certainly think it is.

Click anywhere on the map and a 5 item list appears. Line #1 is the lat/lon of the click point. Lines 2 through 5 are the nearest Airport, VOR, NDB, Intersection to the click point -- perhaps the facility Ident and distance from the click point is displayed for those lines. Furthermore, each of the 5 lines of the list can be "clickable". Click Line #1 and a Type 5 User Waypoint is added to the Flight Plan. Click any of the other lines and the ICAO of that facility is used to create a new waypoint. No knobs need to be turned and no keyboard entry is require; it's all "touchscreen".

You still need to enter the new waypoint number or program suitable geometry so that the most logical new waypoint number is derived by code.

Being able to return an accurate latitude and longitude from a mouse click anywhere on the map, at any zoom and with TrackUp equal zero or one, does indeed open up a lot of new possibilities to those of us using XML as you also have discovered. For one thing, it enables us to sorta keep up with new real world MFD's that have gone "touchscreen".

Maybe I'll polish up the gps-MFD gauge I wrote while finishing the CustomDraw Guidebook and post it on the website. The gps and approach navigation, flight control, audio panel, nav/com/xponder, TAWS, TCAS, MFD is done but I never decided what aircraft to use for engine instrumentation nor did I finish the primary flight display yet because I am still playing around with the ehsi trying to get it to be aesthetically pleasing with the map function. This is when I wish I knew C++ because I can't do enough with the graphics in XML to satisfy me. Of course, no weather capability. It's all very fun.

Keep your stuff coming. I really enjoy seeing others get into the map and gps and design new products!!

Bob
 
Messages
495
Country
austria
Good job!! Good stuff!!
It's really interesting what there can be done with GPS!!!
And what other person do!!

I hope you don't mind but i looked into the avsim library and yes it's already 7 years ago,
that i did a similar gauge.

http://library.avsim.net/search.php?SearchTerm=nav-info.zip&CatID=root&Go=Search

It gives you a seletable list of nearby airports, NDB,s VOR's and intersection.
And there is also the possibility to get into details. Frequencies, Bearing , distances and so one..
It's on very old gauge! A little bit updated.

So it's very interesting for me to see the different approaches to make such a gauge.
Rob, especially your bitmap, posted in another thread was very interesting.
Much more readable then my 6 pages of airportinformation.

Keep on playing with GPS

Edi
 
Messages
1,564
Country
thailand
Thanks Edi. I will take a look at your work :)

Karol's gauges are really interesting too and he is certainly expanding the capabilities of "panning". Brought that to a whole new meaning.

There's still a small group of us that keep the gps and map alive!

Bob
 
Messages
495
Country
austria
Bob,
as said it's a little bit old.
I did some small update.
I added also some kind of runwayadvisory using Doug's sound gauge!!
I would like to improve it but at the moment i've not the time.
If you are interest, i could post it here!

Sorry Karol, i'm little of topic.

Edi
 
Messages
1,564
Country
thailand
Hi Edi,

I have not loaded your gauge and run it in FS yet, but I looked through NAV_Info_Main and NAV_Info_Map and I'm impressed. I can imagine that very few people truly understood gps and moving map variables in 2007, but you certainly did. And of course, I like your ability to tune frequencies through the gauge. You're the man!

I believe an advantage I have over you is that I went for a big screen display of information with "touchscreen-ish" interface from the beginning so I didn't have to figure out how to make things fit in a smaller, early vintage gps display. Today's MFD displays are much bigger and that helps - I think it makes it easier for the hobby gauge designers to be creative. Another advantage is that my map work is done with FSX in mind rather than FS9. There is a lot more that can be done in FSX using XML such as TCAS and TAWS-lite, et. al.

You were ahead of your time. Well done!

Bob
 
Messages
542
Country
australia
Hi Edi

In my opinion your NAV_Info_Main instrument is absolutely stunning .
It was a truely monumental achievement .
Personally , I think that your instrument and the recent one that Bob created are valuable beyond measure .
Their functions and capabilities ensure that they will never become dated .

I know that there are a lot of Eye Candy rivet counters about , but there will always be a core group of Flight sim flyers who need the extra capabilities provided by these unique instruments .
To those of us , they are timeless treasures .

Cheers
Karol
 
Messages
542
Country
australia
Just a little rambling on my part .

One of the many things that I liked in the NAV_Info_Main instrument was the
character counting in the Search ICAO .
Then you typed in the forth ICAO character it would automatically switch off the keyboard .
I hope to implement the character counting in the Mission Adaptive Flight Plan Editor instrument .

Having the Keyboard open to type in either a ICAO or Lat/Long means that the normal aircraft keyboard control functions are not available .
Therefore in my opinion the briefest possible time period of hijacking the keyboard for character entry is highly desireable .
Character counting with auto keyboard disconnect is the very best option .

It was my concern about the open keyboard that made me place a flashing warning light on the MFD bezel that prompts the user that the keyboard is still open .

Cheers
Karol
 
Top