July 7, 20205 yr Latest v3.0.0.0 installed. Currently flying the FSLabs A320x. Altimeter setting was for 6000 ft. Warning started at 2000 ft. Disabled both altimeter settings to stop the warnings. Not the first time this has happened in taking off or in landing and this is not the only a/c it happens in. Anyone else experiencing this issue? PatB Intel i7-9900k | Asus ROG Maximus XI Extreme | 64GB RAM DDR4 | EVGA GeForce GTX 1080ti | WIN10 Pro x64 | P3D v5 HF2 |
July 8, 20205 yr Commercial Member The trigger is if your altimeter setting does not match the altimeter setting detected by RAAS at your current aircraft's location. If you're manually setting your altimeter based on a METAR, you could run into this issue since the alt setting's may differ. The FSLabs uses an altimeter setting system that's completely non standard. We can't read it well. That's why in RAAS we add options to disable callouts like this in case you ever run into problems such as this. However, we have a new RAAS version in beta testing that gives user more power over the trigger. You can now set tolerances. If you want to try it, send me a message with your Order # and email. Best, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
Archived
This topic is now archived and is closed to further replies.