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

FS2004 Bell 407 V2.0

It's actually simple. You capture the current absolute time in a custom L: var when starting the timer. The difference between absolute time and your captured time is the elapsed time.

"Flight time" might be time between engine start and engine shutdown, so trigger the time capture when on the ground and engine combustion is 1 and reset the captured time when on ground, the engine is off and the captured time is not 0.
"Elapsed time" needs to be implemented into the mouse rectangle. I do not know how the Davtron works, but I assume it's controlled with a start-stop-reset button.
Start: Capture time.
In the background: If captured time is greater than 0 and the "stop" variable is 0, evaluate difference between current and captured time.
Stop: Set "stop variable" to anything but 0.
Reset: Set captured time to 0. Set stop variable to 0.
 
Heretic said:
It's actually simple. You capture the current absolute time in a custom L: var when starting the timer. The difference between absolute time and your captured time is the elapsed time.

"Flight time" might be time between engine start and engine shutdown, so trigger the time capture when on the ground and engine combustion is 1 and reset the captured time when on ground, the engine is off and the captured time is not 0.
"Elapsed time" needs to be implemented into the mouse rectangle. I do not know how the Davtron works, but I assume it's controlled with a start-stop-reset button.
Start: Capture time.
In the background: If captured time is greater than 0 and the "stop" variable is 0, evaluate difference between current and captured time.
Stop: Set "stop variable" to anything but 0.
Reset: Set captured time to 0. Set stop variable to 0.
Click to expand...

My friend, one more time I'd like to thank you. Since I've readed your first reply, I have been reading the M803's manual and experimenting as well. Also, I got nailed the "NVIS Green A Option" art work. My brain is slow but works at a steady pace and I won't stop until I fully understand what's going on (combining my current code with your tips and the information within the tutorial which you kindly provided earlier). :)

Davtron_M803_Clock_NVIS.jpg


Cheers,
Sergio.
 
Last edited:
Hi there, fine people!

I am still working on the Davtron M803. Nontheless, I've been receiving "friendly fire" from some subroutines which I still trying to understand... :duck:
So, I let it for a while and I came to this:
SK407_altimeter.jpg


Cheers!
Sergio.
;)
 
Last edited:
Good day friends

Now, the ADI. This is a reference image:
407_ADI_REF.jpg


As much as I like how reflections looks in Photoshop, within the simulator is a little bit...disappointing.
SK407_ADI.jpg


ADI_Action.jpg


Well, two more gauges to go...
Sergio.
:confused:
 
Those gauges are simply amazing. The rest of the bird is equally good.

Thanks very much for all the super good, hard work you're doing!

Looking forward eagerly to seeing this all together and released.
Pat☺
 
Hello Maryadi

I am still using the all mighty FS2004 and sticked to its old ways, altough I would eventually full embrace this design concept. The only thing stoping me, is my very basic programming knowledge to fully exploit this capabilities. I have good teachers who are always helping me with XML nuances and as last resource I ask for help. For example the Davtron M803, it was tricky for me and after a few weeks experimenting with ideas and hints given for one excellent XLM programmer, I finally got it working (Bjoern, do you agree? ;)).

At last but not least, this door is still open because the 407 is a work in progress.
Cheers,
Sergio.
:)
 
Hello Greg

Thank you kindly, today I was working on the Bendix King HSI. I am happy with it but some tweaks are needed.
Sergio.
:wave:
 
Hello lads!

I've finished to code the Bendix/King HSI and a bizarre ADF (you can call it "custom ADF" :rotfl:):
SK407_ADF.jpg


Now, both in "action" (enlarged to see more details ;)):
407_Gauges_in_action_01.jpg


Now in the VC:
407_Gauges_in_action_02.jpg


As you can see, I prefer not include screw heads in the gauge art; that's because -in my humble opinion- they can be drawn exactly where they need to be
(within textures and 2d panel bitmaps :scratchch:scratchch:scratchch).

Please, feel free to add any feedback regarding the gauge layout, graphics, etc. If you think something looks odd and even wrong, just let me know!

Just to clarify, the helicopter where I am performing all tests, is the former Bell 407 designed by Rory Kelly and Alan Devin. As soon as I am able, I will begin to test and export the updated Bell 407 (and variants) into the sim.

In the near future, perhaps the radios and some other gauges will be included. However, several changes in the entire code are expected, that's because some of them will be shared in the VC. In this regard, I will think how to get the best outcome...

That being said, I think I spend enough time with gauges and with a clear head, it is time to move on. Therefore...I should continue modeling the rest of the 407 itself!

I hope you like all the gauges made until now.
Sergio.
:cool:

P.S. Bjoern, thank you kindly for all help provided! Simply stated, I wouldn't get to this point without it. :wizard: :wizard::wizard:
 
Last edited:
You must log in or register to reply here.
Back
Top