I guess I've failed on exposing the problem clearly.
the issue is: under the same conditions, with the mission QNH adjust, my hornet displays baro alt different from other modules. (and from what is displayed at the F2 or F10 view)
Thanks Hulkbust. yes 1in is equal to 1000ft, but don't focus too much attention to it - I inserted that info to illustrate the gradual offset of the altimeter | the gist is: same atmospheric conditions, same QNH setting -> the Hornet is displaying different altitude than other modules flying under the same conditions.
Thanks for the reply, Fresh. DCS trying to simulate the real "conditions" is one of the things that we like so much. I know that, same as the real world counterparts, the altimeters in DCS can be adjusted for pressure, but not for temperature variation and this is a risk factor. Up north, you will find approach plates indicating the need to "Apply altitude corrections for cold temperatures." However, the issue I`m pointing is, regardless of the mathematical model used to simulate atmospheric effects, every plane altimeter, at the same conditions, using the same altimeter setting, should indicate the same altitude. (unless altimeter error is modeled differently from aircraft to aircraft)
It could be intentional or not, but IMO, this bug* could cause vertical separation issues between packages containing different type of planes.
*or not
Anyways, let's see if there are other points.
-------
I tested flying with a friend and the conclusion is that the issue is not the hornet - it`s the MudHen
F16, F14 and FA18C are all showing acceptable altitude under the conditions above. The F15E is not - since it is a relative new module they will probably fix that in a future patch.
Thanks for the input Hulkbust and Fresh.