Trying to simulate instrument errors in a VSI

[JackZ]

Good proof of concept, but I am afraid that’s a bit of a hair pull.
Most if not all of the modern aircrafts are equipped with IVSI (instantaneous vertical speed indicator), built to counteract the effect you’re trying to implement by using counterweights and small pistons.
https://www.mcico.com/resource-center/a ... t-lag-time

The reaction time lag of a standard VSI is for vintage aircrafts with old VSIs. It can be up to 6-9 seconds

[SimPassion]

Good point Jacques , exactly what I need :

[JackZ]

Yeah. IVSI Have INSTANTANEOUS written on the face of the Gauge somewhere

[SimPassion]

Yeah. IVSI Have INSTANTANEOUS written on the face of the Gauge somewhere

Yes, as in the picture shown above

[frumpy]

I have only flown standard VSIs, but it was 20 years ago, is that vintage? I assume that in most steamgauge 172s and modern ULs you can find at the airfields have non-IVSIs. I used to work at an airfield and looked at the gauges, afaik IVSIs are more for IFR equipped aircraft.

I am easily bothered by all too perfect displays of aircraft systems in a flightsim. Like engine 1 values are identical with engine 2 values and they change exactly at the same instant moment and of course always have perfect sensors with a 1°C resolution and so on, you name it. Elite flightsim did better 25 years ago (btw. you can setup each plane having a standard or IVSI). I feel with AM and it's posibilities to alter values a bit we can greatly increase immersion, like Jacques did with the vibration needle effects.

For IVSIs, this can be a swinging movement of the needle when flying through rough air since the counterweight starts moving. But I don't think this is easily feasible in X-Plane, yet it does not make too much sense without a motion platform.

[JackZ]

I think even 20 years ago most of the VSI were already in fact IVSI. I have not flown any GA aircraft for a while, but I don’t recall having encountered VS lag delays such as 6 to 9 seconds which seems A LOT.
In my Airbus we don’t have this problem anyways as data comes from the Air data reference computers (ADR) and is therefore compensated.

As per to “to clean to be true” I do agree with you, as once again even in the Airbus it is common to see differences on altitude displays between captain’s and F/O PFD’s of like 10 to 20 feet.

[jph]

Interesting project and great work and input.
Nice.
Joe

[frumpy]

I think even 20 years ago most of the VSI were already in fact IVSI. I have not flown any GA aircraft for a while, but I don’t recall having encountered VS lag delays such as 6 to 9 seconds which seems A LOT.

Here its quite a few seconds:
https://youtu.be/YIOGik5klB4?feature=shared&t=115

Here is also a very slow VSI, left of the standby horizon:
https://youtu.be/nHaQ-8ta9EY?feature=shared&t=306

[frumpy]

Next version is up.

Changes:
- speed limitation of the pointer is removed for now, as it did not feel right and the code looked nasty
- random offset of +-50 ft/min added; afaik this is the normal range for instrument error
- ground effect added; while the plane is in ground effect, the static pressure rises. This causes a negative reading on takeoff and landing; for real life check this: https://youtu.be/RQCBihrk0EY?feature=shared&t=660
- some random changes due to turbulence; I did not find any dataref for up/downdrafts, so I used fluctuations of the wind and brought the mean to 0; check this: https://youtu.be/r83l8sU12Ak
- strength of ground effect and turbulence can be tweaked to your liking with the initial variable definitions

Thats a demo of the offset and ground effect:
https://youtu.be/3cz57kwi4dI

AAA VSI with delay offset groundeffect turbulence.siff

(160.92 KiB) Downloaded 119 times