FSXA ETE Profile Display

[delivery guy]

I like really like that "R" button Tom...Is it possible to make a simple button or how can I get a copy of this amazing L Var directory optimizer do it all in 1 display program..

Update on the Profile ETE:

I found the second code was rubbish as it was inconsistent and put my thinking cap on. Took a look at some common formulas and finally hit me....

ALTITUDE / FPM = TIME...Used both VSR and the Profile setting on this formula.
Time - Time = ETE Profile Now the ETE is perfect....

The Altitude in my code is custom because it includes the above AGL and MSL and is
important for when adjusting the altitude. You can just use A:altitude.

<!-- ETE DISPLAY -->

<!-- ABOVE/BELOW WP -->
<!-- ALT / FPM = TIME -->
(L:WP ALT ERROR,Enum) 0 == (L:MSL ALT ERROR,Enum) 0 == or if{
    (L:ALTITUDE CALC1, feet) (L:VSR DISPLAY PLUS, Feet per minute) / (>L:TIME1, Minutes) }

(L:WP ALT ERROR,Enum) 1 == (L:MSL ALT ERROR,Enum) 1 == or if{
    (L:ALTITUDE CALC1, feet) (L:VSR DISPLAY MINUS, Feet per minute) / (>L:TIME1, Minutes) }

<!-- ALT / FPM = TIME -->
    (L:ALTITUDE CALC1, feet) (L:TARGET PRFL CALC, Feet per minute) / (>L:TIME2, Minutes)

<!-- TIME - TIME = ETE -->
    (L:TIME1, Minutes) (L:TIME2, Minutes) - (>L:RATE, Minutes)

<!-- ETE DISPLAY -->
    (L:RATE, Minutes) (>L:ETE PRFL TIME, Minutes)

<!-- FORCE ZERO -->
    (L:ETE PRFL TIME, Seconds) 0 &lt; if{ 000000 (>L:ETE PRFL TIME, Seconds) }

 

[rpmc]

I like really like that "R" button Tom...Is it possible to make a simple button

Make yourself a small pic icon or use the one attached

, then use this simple script - see #5 - same as the one below:

<Gauge Name="Panel Reload" Version="1.0" >
  <Image Name="Reload.bmp" Bright="Yes" ImageSizes="20,20,0,0"/>
  <Mouse>
    <Area Left="0" Top="0" Width="20" Height="20">
    <Cursor Type="Hand"/>
      <Click>
        (A:Fuel weight per gallon, pounds per gallon) 0 ==
          if{ (>K:RELOAD_USER_AIRCRAFT) }  <!-- FSX -->
          els{ (>K:RELOAD_PANELS) }        <!-- FS9 -->
      </Click>
    </Area>
  </Mouse>
</Gauge>

For additional ideas on how to set up a Panel Refresh 'gauge', see the Refreshing Panels in FS9 wiki in this website. The methods discussed can be adapted to FSX. Plus, the Panel Reload script, above, is already included in that wiki.

Bob

 

[rpmc]

I have had Black box and another recommended , but have avoided them because I assume
that there is a long learning curve associated with them .

Not surprisingly, I disagree. Blackbox is straightforward. It's also versatile, powerful and can output variables to HDD file in addition to display on the screen.

And, BB isn't the only option. Doug Dawson also provides a diagnostic gauge on his website, and as mentioned above, Tom Aguilo will soon release his module redesign with many new features, one of which is that diagnostic display.

What's surprising to me is that you have been able to get along without Blackbox so far. Your gauges are complex and you try a lot of new things. I would have thought a logic debugger would have been one of your staple tools. Anyway, it's what I use to check any A:Var, any L:Var, any time. And Tom's will have all those features too, of course.

Bob

 

[COBS]

As a general idea, in my company we develope a project by first identifying the general aspects that need to be covered, then we define the different sections to be included, then each section is programmed like a whole part, with "loose ends" that have to be tied upon the final stages.

While a part is being programmed new ideas might rise that belong to other part(s) of the project, in these cases they are sketched within the proper section(s) so we can resume working on them as we get full involved with that section's (part) code.

Tom , you put into words the process much better than I could ever have described it.
Regards ; " .. then each section is programmed like a whole part ... " , I had to smile as that was what I did
with my 'Mission Adaptive Flight Plan Editor' , I had three separate instruments , an MFD , an ICAO page ,
and a Lat/Long page , then when they were working correctly they were all merged into one MFD .
I just did it naturally that way to keep it all as simple as possible , then after the merge I refined it a little .

I found the second code was rubbish as it was inconsistent and put my thinking cap on. Took a look at some common formulas and finally hit me....

I like the way you think and operate .
I consider all my gauges as WIP , they can always be improved and have new capabilities added to them.
I did a simple Radar , then progressively over time added new features to it , and added connectivity to
other gauges to allow cross pollination .

Not surprisingly, I disagree. Blackbox is straightforward. It's also versatile, powerful and can output variables to HDD file in addition to display on the screen.

And, BB isn't the only alternative. Doug Dawson also provides a diagnostic gauge on his website, and as mentioned above, Tom Aguilo will soon release his module redesign with many new features, one of which is that diagnostic display.

Bob , I think that I'm converted , I had always been scared that they might be too complex to learn and operate ,
your reassurance is appreciated .

Cheers
Karol

 

[rpmc]

Take my word for it. When you make use of an XML tool like Blackbox, your work will become more efficient, faster paced, and you will be able to take on even more advanced projects.

 

[rpmc]

I like that...general question! Is there any way to reload aircraft without reloading the aircraft to update your work or is this a must?

In FS9, you can use (>K:RELOAD_PANELS) but in FSX you must use (>K:RELOAD_USER_AIRCRAFT). That simple gauge refresh script above will apply the right one.

 

[taguilo]

Not surprisingly, I disagree. Blackbox is straightforward. It's also versatile, powerful and can output variables to HDD file in addition to display on the screen.
And, BB isn't the only option. Doug Dawson also provides a diagnostic gauge on his website, and as mentioned above, Tom Aguilo will soon release his module redesign with many new features, one of which is that diagnostic display.

Indeed Blackbox and Doug's gauge are two excelent tools, and I've used both quite a lot while developing.

LVars Logger utility is a bit different than Blackbox as in this one the user needs to define the LVars he/she wants to inspect for each panel he/she might want to work with; LVars Logger (which is entirely written in XML) automatically loads all the LVars present in a flight session, and gives the option to interact with them while running. Also is a powerful tool for inspecting a third party aircraft while seeking for unknown LVars embedded in the .MDL file, or the names of LVars that are tied to certain dummy switches/buttons, etc.

In FS9, you can use (>K:RELOAD_PANELS) but in FSX you must use (>K:RELOAD_USER_AIRCRAFT). That simple gauge refresh script above will apply the right one.

Actually RELOAD_PANELS and RELOAD_USER_AIRCRAFT gives almost the same for practical purposes, however the latter won't retain current LVar values upon reload, something than can be dissapointing within a development scenario.
XMLTools module includes LOCALVARS class (the one used as an interface to LVars Logger utility) which in turn includes a flag that enables LVar values to maintain their values after RELOAD_USER_AIRCRAFT is triggered, just to mimic in some aspect what RELOAD_PANELS does in FS9.

Tom

 

[rpmc]

LVars Logger utility is a bit different than Blackbox as in this one the user needs to define the LVars he/she wants to inspect for each panel he/she might want to work with; LVars Logger (which is entirely written in XML) automatically loads all the LVars present in a flight session

Hmm? Tom, you make it sound as if Blackbox does not automatically parse the gauges in the panel set and list all the L:Vars and A:Vars used (or any A:Var one might want to see for that matter). But of course, it does that. The user can select all, none, or just some of the variables to watch - point and click, not too hard, which is necessary when there are hundreds or even thousands of variables. A lot of work went into display management in Blackbox. Because there can be so many variables, there must be a logical and easy way to manage the real time display, and also to mitigate the frame rate hit that can occur if copious amounts of variables are displayed.

Anyway, I don't see what you are getting at .. Bob

 

[rpmc]

Actually RELOAD_PANELS and RELOAD_USER_AIRCRAFT gives almost the same for practical purposes, however the latter won't retain current LVar values upon reload, something than can be dissapointing within a development scenario.
XMLTools module includes LOCALVARS class (the one used as an interface to LVars Logger utility) which in turn includes a flag that enables LVar values to maintain their values after RELOAD_USER_AIRCRAFT is triggered, just to mimic in some aspect what RELOAD_PANELS does in FS9.

Yeah, this is one of the features that will be useful in XMLTools. It's just that, for the time being, since RELOAD_PANELS won't work in FSX, we use RELOAD_USER_AIRCRAFT.

I'm also anxious to get logging capability of XMLVars. You know that one diagnostic gauge I constructed for the fs9gps:Map guidebook used well over 1000 XMLVars. I may have even exceeded the v1.0 limit. Anxious to see XMLTools.

Bob

 

[taguilo]

Hmm? Tom, you make it sound as if Blackbox does not automatically parse the gauges in the panel set and list all the L:Vars and A:Vars used (or any A:Var one might want to see for that matter). But of course, it does that. The user can select all, none, or just some of the variables to watch - point and click, not too hard, which is necessary when there are hundreds or even thousands of variables.

Bob, for each panel in where you want to use Blackbox, first you need to add the gauges to be inspected into a Blackbox project and finally generate a Blackbox xml gauge that will be specific for that panel.
LVars Logger works much like Doug's gauge, you don't need to configure anything different from adding the gauge to a panel.cfg of your choice. Then you start a flight, open LVars Logger subpanel and all the Local vars that are active will show in the display window, including those that might be coming from inside the .MDL only.

Anyway, I don't see what you are getting at .. Bob

I am not getting at anything...just describing some differences between both utilities. I am not saying that LVars Logger is better than Blackbox or Doug's gauge; it's just different, probably a combination of the best of both

I'm also anxious to get logging capability of XMLVars. You know that one diagnostic gauge I constructed for the fs9gps:Map guidebook used well over 1000 XMLVars. I may have even exceeded the v1.0 limit. Anxious to see XMLTools.

Actually LVars Logger uses another XMLTools class, LOCALVARS, for internal processing. XMLVARS class is included in the module as well, and now supports memory-limited number of custom variables (instead of the previous 2048).

Tom

 

[delivery guy]

Thanks for all the tips on tools to help programming. I never made many "Large coding" 2D gauges until now so this is helpful. Most of my gauges are all
3D and designed or small 2D gauges.

Where do i get Blackbox. I think i will start there....

 

[delivery guy]

i am trying to convert xml to spb and keep getting

error 83600FB7: AceXML Parser Error : 'guage' -
error 83600fb7: Read failed.

Maybe you can't covert gauges to spb? I use to do this for missions and the SDK says xml gauges. So this could be a good clue!

Any help would be great....

 

[WarpD]

Perhaps gauge instead of guage??

As for the conversion, sure... though it offers zero protection and otherwise doesn't do a thing for you... LOL

 

[delivery guy]

Gauge is just spelled wrong on my part. And I am not converting a file called gauge anyways. Gauge must be coming from the propdefs folder.

What i want to know is how to protect your important gauges? This would be helpful for some gauges. I will continue to use cab file for others.
I once noticed a cab file that could not be opened. Maybe there is a way to lock the cab file?

 

[WarpD]

The largest failure of the XML gauge concept is protection. It's a text file, open to the world.... even if you convert it to a .spb format... that can be converted back. So if you don't want to go 'open source'... you picked the wrong way to make gauges.

 

[taguilo]

What schema are you using for your XML gauges? I understand the SPB converter accepts FSX schema only.

Tom

EDIT: Ed is right, you can't protect XML files, converted or not, from unwanted watchers; SPB files can be reversed back using a buch of tools available everywhere.

 

[delivery guy]

That makes sense and I am ok with that. The only people going to steal your coding already are good enough to write their own!


Tom...Version 1.0 is what i am using and want to protect. I have written a G1000 in the same schema as the default G1000. It was about the same but different in coding style. i forgot the name of the schema it was.


I added the "R" reload script and added a cool feature. I made it so the window auto opens after reload. No point on opening the window each time. And you can include the ones that your working on. Thanks for the script Bob.

(>K:PANEL_4)

 

[tgibson]

Edited: Please note that I made an error in my original post (in a different thread) and said that
(A:Fuel weight per gallon, pounds per gallon) in FS9 returns 0, which is incorrect. For piston aircraft (avgas) it returns a number like 1583. So testing for 0 will not detect FSX vs FS9 in the previous code, This code should work.

<Click>
        (A:Fuel weight per gallon, pounds per gallon) 0 ==
          if{ (>K:RELOAD_USER_AIRCRAFT) }  <!-- FSX -->
          els{ (>K:RELOAD_PANELS) }        <!-- FS9 -->
      </Click>

Sorry for the error,

 

[delivery guy]

Roger that. Maybe just use battery on?

 

[rpmc]

Please note that I made an error in my original post (in a different thread) ...

Roger that. Maybe just use batter on?

I believe Tom's original post was indeed correct and furthermore, it was a pretty sharp eye to observe that FS9 screws up the units conversion for simulation variable (A:FUEL WEIGHT PER GALLON) and that it is fixed in FSX. The variable returns this:

so, it can be used to tell whether the sim is FS9 or FSX. If (A:FUEL WEIGHT PER GALLON, pounds per gallon) returns 0, then you're running FSX. If it doesn't, you're running FS9. Thanks again, Tom. It helped me make my Reload gauge compatible with either sim.

Where do i get Blackbox. I think i will start there....

BlackBox can be freely downloaded here.

Additionally, Doug Dawson provides a diagnostic module on his website.

And when Tom Aguilo releases XMLTools, I believe you certainly will want to try that.

If I am missing any, please let me know. Thanks.

Bob