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

FSXA Second altimeter

Vitus

Vitus

Resource contributor
Messages
1,480
Country
newzealand
I can "declare" a second altimeter in the aircraft.cfg file. I was wondering if there is a hidden set of token variables available to get a second, different reading.

Regards
Vitus
 
No. Create your own custom variable. You can of course also include code to "synch" the kohlsman value should the user press the B key for standard pressure.
 
Hi Bill,

thanks for the answer. I already thought so. The density-altitude function is not linear, therefore not easy to implement :(
I will figure out something, sometime....

Vitus
 
I've worked on a second, independent altimeter some time ago (with some "extras" like pre-programming QFE/QNH for different modes with values in mbar/inHg/mmHg each not influencing the "main" altimeter ;)). I had researched a lot back then and was quite happy with the results, although not 100% perfect - especially as I wanted to include some "altimeter" errors simulated, like the temperature dependent altimetry error which doesn't work right in my gauge...

I have all my research (DA formulas, Temperature Error models, QFE conversion and so on...) and the final (xml) gauge on my second computer, I'll search them and can provide you with them if you like.

Jakob
 
Ok, found the files. Here is the gauge I made, but it isn't final yet (although paused). MultiAltimeter.zip, and I only found part of my resources, here Formulae.zip. The rest of the info I gathered from the internet (see Link list below), as the ICAO-Standard Atmosphere Document which had loved to get hold of, is very expensive (which is a shame in my opinion, international standards/documents should be free of charge for non commercial use).

I hope I could give you some useful information,
Jakob

Link List

There are more but my bookmarks are not that well organized ;)

p.s. I found I hadn't even started integrating the Temp Error yet... :(
 
Gruess Gott Jakob,

wow! Thanks for your effort, it is much appreciated! However I am currently spending my time on a different system, it might take some days but I will get back to you!

Besten Gruss
Vitus
 
You're welcome. Please let me know if there is something missing or unclear, I can try to figure it out but I must admit the last time I worked on this was over a year ago... :)

Jakob
 
Simply declare second altimeter in Aircraft.cfg:

Code: 
[altimeters]
altimeter.0 = 1
altimeter.1 = 1

And use indexes for second altimeter:

Code: 
(A:INDICATED ALTITUDE:2, feet)
(A:KOHLSMAN SETTING HG:2, inHg)
2 (>K:KOHLSMAN_INC)
2 (>K:KOHLSMAN_DEC)
 
That works for FSX, but if one is modeling for both sims... :ziplip:
 
Hey some1,

awesome! This would be a simple way indeed. And as I am just developing for FSX, I don't care about old technology :D

But there is a problem: I can't use the (>K:KOHLSMAN_INC) code because I use a drag-script and the (>K:KOHLSMAN_SET) to modify the QNH.
Is there a second set-event for the second altimeter?

Regards
Vitus
 
You must log in or register to reply here.
Back
Top