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

Getting TOT Gauge to spike at higher temp on start up when drop back to normal

Messages
123
Country
newzealand
Hi all

I have been working on a Helicopter TOT gauge that reflects the real gauge in a MD500E.
What I would like to do is on engine start have the TOT gauge spike to a higher number as per the real gauge then drop back to its normal reading which is about 450 (simulated).
what do I need to add to the xml file to simulate what I am trying to achieve

Best regards

Rhys
 
I will start trying something in this spirit to fake the spike:
pseudo code of mine :)
if (engine is starting) \\I believe you can do this checking engine combustion A:var
while delta time -> { blit TOT slider or needle to higher fake value(s) }
check if delta time if reached-> {blit TOT slider or needle to real TOT simulated values} \\ here you should use the proper A:Var for TOT

However if you want to do it like the pros you will need to tweak the heli values I believe in the air file.
I believe there are tools that can do these tweaks , search the forum or check in the wiki.

Worse case scenario ask Chat-GP 😄
 
Holy crap!😄 I put this question in chat-gp to put it on test and I got this as answer (I m still in denial this is some serious stuff, Lol)

"What I would like to do is on engine start have the gauge spike to a higher number as per the real gauge then drop back to its normal reading which is about 450 (simulated). what do I need to add to the xml code for fs9 to simulate what I am trying to achieve"

To simulate the behavior you described, you can use XML code in FS9 gauge programming. You'll need to modify the XML code for the gauge you want to change.
Here's an example of what you can add to your gauge XML code to make the needle spike on engine start and then drop back down to a normal reading:
Code:
<Element>
  <Select>
    <Value>
      (A:ENG1 MASTER, bool)
    </Value>
    <Case Value="0">
      <Value>
        450
      </Value>
    </Case>
    <Default>
      <L:SpikedValue>
        0
      </L:SpikedValue>
      <L:TimeStart>
        0
      </L:TimeStart>
      <GaugeStart>
        <Value>
          450
        </Value>
      </GaugeStart>
      <Value>
        (L:SpikedValue)
      </Value>
    </Default>
  </Select>
  <Nonlinearity>
    <Item>
      <Value>0</Value>
      <Mapping>0</Mapping>
    </Item>
    <Item>
      <Value>1</Value>
      <Mapping>300</Mapping>
    </Item>
    <Item>
      <Value>2</Value>
      <Mapping>800</Mapping>
    </Item>
  </Nonlinearity>
</Element>

This code assumes that the gauge you want to modify is already set up to display a value of 450 normally.
The code uses the "Select" element to check if the engine is running. If the engine is not running, the code sets the value to 450. If the engine is running, the code sets the value to a "spiked" value that starts at 800 and gradually drops down to 450 over a few seconds.
The "Nonlinearity" element is used to create a curve that maps the spiked value to the needle position on the gauge. In this example, a value of 0 corresponds to a needle position of 0, a value of 1 corresponds to a needle position of 300, and a value of 2 corresponds to a needle position of 800.
Note that this is just an example, and you may need to modify the code to fit your specific gauge and engine startup behavior. Also, keep in mind that modifying XML code can be tricky, so make sure to test your gauge thoroughly before using it in a flight simulation.


Regenerate response
 
Hi Adino

Thanks heaps for that. I entered the command line but the gauge didn't show up so I must have put the code in the wrong place
I have attached the TTI file. Are you able to add the new code to the current xml file. Im not sure where it goes

Cheers

Rhys
 

Attachments

Note that this is just an example, and you may need to modify the code to fit your specific gauge and engine startup behavior. Also, keep in mind that modifying XML code can be tricky, so make sure to test your gauge thoroughly before using it in a flight simulation.
These were not my words actually it was AI telling you that the code is just an example and that he not even sure it will do what you want.
Use the example as an idea on the type of logic you can use to code your gauges if you are experience with coding. I'm sorry If I created too much expectations with the replies...
 
Back
Top