Improper Baro Setting: The ESI-500 and G1000 require “independent” setting of the barometric pressure (Altimeter setting). If one is not updated, altitude changes will be calculated differently, creating a VSI mismatch.
If the ESI has the same barometric reading as the G 1000 because it was set by the G 1000, then the ESI would need to be barametricaly set from the ESI and not the G 1000. This is only just one of the ways to deal with a discrepancy between the two. So back to my first statement to verify they are the same, this was leading into the process to troubleshoot the difference. The two could read the same, yet be really far off, so they need to be set separately. To be fair and not knowing, it may be that they were individually established and my comment was needing refinement. My apologies.
Where are you getting this from? Because that is not at all how the real things work. I’ll repeat the baro setting has nothing to do with VSI. VSI is a rate of change function not a fixed value like altitude. Only the altitude value is affected by the baro correction.
Right- But if I’m understanding them correctly, they’re saying that the ESI altimeter doesn’t respond to the ESI Baro knob but the ESI altimeter DOES respond to the PFD Baro setting:
But yeah, either way none of that has anything to do with a faulty VSI indication.
Honestly, if all that stuff is legitimately malfunctioning that badly, it might just need a reinstall.
Yes it is. As already mentioned in this thread a static port issue such as a blockage could cause such issues if modelled but baro correction is local to the altimeter. You’ll notice in a steam gauge aircraft only the altimeter has baro correction. The VSi does not. It works on the rate of change of the static port pressure. It’s a bit much for this thread for me to explain the inner workings but I’m sure google has many examples of that if you are interested in the detail.
With SU5 released, I tried a few employee career skydive missions that featured the Kodiak… Unfortunately, the skydivers still don’t register as jumping so it seems to be an issue with the Kodiak itself.
I tried both the default Porter (which is similar to the Kodiak in that it just prompts to press enter to jump) and the Caravan (which uses the keybinds for red light/green light to initiate the jump) and both worked fine. Below is a screenshot of the end of the jump sequence where the jumpers haven’t registered as jumping in the Kodiak, as well as proof that I can complete these missions in the Caravan. Hopefully this can get fixed!
Just an update. If the G1000 vertical speed is indicating 1000fpm or greater then the ESI500 will match, if <1000fpm its usually half value vs the G1000. Sorry don’t have screenshots as was busy descending
It’s been a busy week on the Kodiak side, especially with the recent simulator updates.
On the MSFS 2024 version, we’ve been working on improving engine behaviour and overall handling. Changes to the sim have allowed us to refine things like beta range control and engine response, which now feel much more natural during taxi and landing. We’ve also expanded the engine temperature simulation, particularly in reverse thrust conditions.
The aircraft is now fully running on the new FS2024 flight model, and we’re currently fine-tuning it, especially near ground effect.
Systems-wise, we’ve wrapped up a full round of updates, including avionics fixes and a rework of switches and circuit breakers to a more consistent standard. Career Mode also received fixes, including improvements to skydiving behaviour.
On top of that, we’ve started working on a Medevac expansion for the Kodiak 100, which we’ll be sharing more about soon.
For the MSFS 2020 version, some improvements from 2024 are being brought over, including updates to the yaw damper, trimming behaviour and other fixes. Work there will pick up once the 2024 version is finalized.
For the full update details and discussion, join us on Discord:
I remember how, as a kid, I got into my share of discussions over whether one person or thing (sports team, artist, etc) was better than another. Maybe it’s something similar
Sorry to hear. No I was able to start the Kodiak manually without issue.
Are you sure you did not skip on or two steps?
Recommend just follow the Checklist.
I’ve got this setup in Spad with both 3 and 1 on a button but it only interrupts the warning, not silence it as if button on dash is pushed. Wondering if I missed something? Thanks for this post!
