FSX XML: Glass gauges fading in

[taguilo]

Is it possible to include a <Update> in modeldef.xml file? If so, at what point exactly?

No, it is not.

Or if not, can we include a "loop using a Goto" in modeldef.xml file? If so, where and how?

Yes, a loop can be included in any XML script, regardless of the parent key. However, it should be used with care, because all the content within a loop is executed on every frame. Going to the essential from both of your questions, you can't replace an <Update> with a loop, what you can do is put the same code you would put in <Update> inside a valid modeldef key, for example <Code>, <Visibility>,etc. But if you don't really need to hide XML scripts from user inspection, the best option would be to use an invisible gauge in VC, as suggested by Roman.

Tom

 

[n4gix]

No, it is not.

How odd... I've been doing "sort of that" for several years now...

...and it seems to work quite well, thank you! Okay, it's not really an <Update> section, but it does serve the same purpose...

1. Create a tiny polygon in Max, GMax, whatever modeling program
2. Attach a <Visibility> script to the polygon.
3. In your modeldef.xml file, have a <Visibility> <PartInfo> section set up:

  <PartInfo>
    <Name>Update_Routine</Name>
    <Visibility>
      <Parameter>
        <Code>
          <!-- INITIALIZATION ROUTINE(S) -->
             (L:Init,bool) 0 ==
             if{
                 (* PLACE ANY ONCE ONLY SCRIPTS HERE *)
             1 (>L:Init,bool)
             }
          <!-- END INITIALIZATION ROUTINE(S) -->
       
          (* PLACE ANY "<Update>" SCRIPTS HERE *)
 
        </Code>
      </Parameter>
    </Visibility>
  </PartInfo>

Because any object with a <Visibility> tag will always be evaluated every cycle, stuff you put here will act just like a gauge's <Update> section.

 

[taguilo]

I've been doing "sort of that" for several years now...

I know Bill, I know...that's the reason I posted this:

"what you can do is put the same code you would put in <Update> inside a valid modeldef key, for example <Code>, <Visibility>, etc."

in my previous message, and left the details to you

Tom

 

[Chrismot]

Your answers will fill me with joy ...! I'm having a lot of fun to test all this ...

A huge thank you to XML Gurus!

 

[tonaz]

Sorry for reopening this old thread, but i would be very grateful if someone can help me.
From what i see, in my project, a gauge can contain only bitmaps with ONE alpha channel. On or off.
How it works the "layer system" you are talking about, if there is only one alpha bit?

wait maybe i got it, it involves 3d planes in the 3d model right?

 

[tgibson]

Hi,

DXT1 images only contain one alpha channel bit. DXT3, DXT5, and 888 32 bit images can have a grayscale alpha channel (I think that's 256 shades of gray?).

 

[tonaz]

true. but in designing gauges this don't count.
can you confirm? the gauges do not read dxt3/5.
actually they dont read not even dxt1.
just bmp with 1 alpha.
am i correct?

 

[tgibson]

Yes, unfortunately those formats do not work in gauges.

 

[tonaz]

Thanks for confirmation.
Wich is nonsense, couse outside gauges actually there is transparency, well, kind of. See effects textures (additive greyscale transparency).
Misteries of ESP1.0