January 26, 20224 yr Hi, I was hoping you might tell me which datarefs P2ATC is looking at to read indicated altitude? It appears that due to the custom nature of the hotstart CL650, the altimeter reading that P2ATC reads, is not what is shown in the cockpit. If I know which ref you are looking at, I can hopefully knock together a script to make it all play ball... Thanks, James James W
January 27, 20224 yr Commercial Member FSUIPC/XPUIPC offset 0x3324. Seems like HotStart would want to fix their aircraft. Dave
February 2, 20224 yr On 1/27/2022 at 7:04 AM, Dave-Pilot2ATC said: FSUIPC/XPUIPC offset 0x3324. Seems like HotStart would want to fix their aircraft. Dave Technically, its not broken. They're just simulating a level of realism with altitude/temperature drift that no other add on including the online ATC platforms (Vatsim, Pilotedge, etc) account for. Currently the CL650 does allow it to be disabled for the online ATC platforms but not when using P2ATC (their issue, not yours). Multiple people are trying to convince them to make it a global toggle, but they appear to be somewhat opposed because it breaks some of their immersion magic. I understand Hot Start's position, but they don't live in a vacuum and refusing to take into account the current real world around them add-on wise for the sake of their ideals of realism is a bit.... annoying. Supposedly XP12 is adding some additional datarefs that will allow better interoperability in situations like this. We shall see.
Archived
This topic is now archived and is closed to further replies.