<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[VATSIM traffic is shown off their actual FL on the ND. ALTM STD not recognised?]]></title><description><![CDATA[<p dir="auto">I've noticed on cruise that VATSIM traffic is shown not on the level they're cruising in their sim.<br />
In both screenshots, you can see the ND showing traffic +5400ft above and +3400ft above, while they should have read +50 and +30 exactly as they were exactly cruising on their filed flightlevels. Vatsim-radar showed them right on their FL and the VATSIM ATC client showed them on the right FL too (asked the controllers in both cases to confirm my observation).<br />
I've been on STD altimeter on both flights.<br />
Changing the altimeter setting (while still having STD active) doesn't change anything in the shown deviation.<br />
At the time of writing, a WZZ A320 crossed 5000ft above while the ND shows +52.<br />
In this case, I changed from STD to 1015 (which was the QNH on an airport right below) and icon showed +51 or +50.</p>
<p dir="auto">Any chance the TCAS (icons) don't take the switch from local QNH to STD into account?</p>
<p dir="auto"><img src="https://communityuploads.justflight.com/files/12737/49df68f8-77d8-44fe-b062-51a245c6cdff.png" alt="01_ALT_320vs370+54.png" class=" img-fluid img-markdown" /> <img src="https://communityuploads.justflight.com/files/12737/85953981-9f24-43ef-ae65-418aea7d94b2.png" alt="02_ALT_330vs360+34.png" class=" img-fluid img-markdown" /></p>
]]></description><link>https://community.justflight.com/topic/10884/vatsim-traffic-is-shown-off-their-actual-fl-on-the-nd.-altm-std-not-recognised</link><generator>RSS for Node</generator><lastBuildDate>Mon, 06 Jul 2026 11:28:49 GMT</lastBuildDate><atom:link href="https://community.justflight.com/topic/10884.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 05 Jul 2026 18:48:56 GMT</pubDate><ttl>60</ttl></channel></rss>