manguras Posted January 25, 2022 Report Posted January 25, 2022 (edited) Hi guys Has anyone had a similar experience? I'm flying at FL360 but IVAO webeye shows 380? I'm using latest v1.2.3 Thanks Edited April 12, 2022 by Pils
Pils Posted January 26, 2022 Report Posted January 26, 2022 There is apparently no way to detect that the IVAO pilot client is online therefore the realistic altimetry, which is the cause of the altimeter under reading in your case, is always enabled. I believe there is a request with the Altitude developers to provide a mechanism. If you lend your voice to this request then it might help hasten its implementation. If/when this means exists then a feature request will be submitted to the CL-650 developer. Thanks.
Tanguy317 Posted February 7, 2022 Report Posted February 7, 2022 Hi, I had a similar experience and still experiencing this problem while flying on IVAO. Using last version of altitude, Active sky and CL60 v1.2.3
leha74ru Posted February 8, 2022 Report Posted February 8, 2022 there are many different clients. the idea of making a manual switch, online-not online looks the most sensible 2
danhenri Posted February 8, 2022 Report Posted February 8, 2022 (edited) I get better results on IVAO if I leave the barometric item checked in the user settings. Then, the difference is only about 200 ft. If unchecked, then the différence is near 2000 ft at high altitudes... Edited February 8, 2022 by danhenri 1
leha74ru Posted February 10, 2022 Report Posted February 10, 2022 (edited) in addition to IVAO, there are also clients in which I fly and these are not online flights, but there are penalties for lights on/off up to and above FL100. Therefore, we need a simple checkbox and not a definition of whether the client is running or not. Edited February 10, 2022 by leha74ru 1
airforce2 Posted April 3, 2022 Report Posted April 3, 2022 I'm somewhat dismayed that this was neglected in the 1.5.2 update. Bob 2
ois650 Posted April 4, 2022 Report Posted April 4, 2022 Folks, this is not a Hot Start issue. You need to push IVAO client teams to work on this. You will notice that X-Pilot works perfectly. Quote There is apparently no way to detect that the IVAO pilot client is online therefore the realistic altimetry, which is the cause of the altimeter under reading in your case, is always enabled. I believe there is a request with the Altitude developers to provide a mechanism. If you lend your voice to this request then it might help hasten its implementation. If/when this means exists then a feature request will be submitted to the CL-650 developer. Thanks. 1
airforce2 Posted April 4, 2022 Report Posted April 4, 2022 (edited) This isn't just about online ATC programs--the nonstandard altimetry breaks compatibility with other utilities that determine altitude using the provided X-Plane dataref. Why can't Hot Start just provide a user switch to turn the "realistic" altimetry off? It's got to be a whole lot simpler than auto-detecting online communications from specific ATC programs, and it would preserve the option to employ the standard interface to X-Plane. This *is* a Hot Start issue--this is the *only* add-on I am aware of that chooses to do its altimetry independently of the X-Plane platform dataref, which breaks compatibility with anything not specifically coded for that...in other words, lots of stuff. In my case it's Radar Contact v4, which is not being developed any longer but which works flawlessly with any aircraft that adheres to use of the standard platform dataref. It's also an issue with the Pilot2ATC and PF3 offline ATC add-ons as well. Why is it considered preferable to build complex auto-detection routines in for a select group of ATC clients, rather than just allowing the user to de-select the nonstandard HotStart altimetry with a tickbox? Edited April 4, 2022 by airforce2 1 1
Pils Posted April 4, 2022 Report Posted April 4, 2022 7 minutes ago, airforce2 said: Why is it considered preferable to build complex auto-detection routines in for a select group of ATC clients, rather than just allowing the user to de-select the nonstandard HotStart altimetry with a tickbox? To quote the developer: Well, adding an on/off switch isn't difficult. But it goes against the philosophy of the product, so I'm opposed to it from the point of view of the logical purpose of the product. People would just enable it and not give a single care to temperature compensation. I'd rather people learn the proper way, than try to simplify it and then acquire bad habits. There is also the fact X-Plane is going to have this simulation built in with V12, and many people are going to be using it with many addons, as presumably it’ll be default enabled.
Pils Posted April 4, 2022 Report Posted April 4, 2022 To elaborate a little: we, the volunteers who help with the forum, have passed on the numerous feedback on this topic, as have the members of the Discord. Requests have been heard, and are always under consideration. But I can’t say any more than that as I’m not the developer. 1
leha74ru Posted April 5, 2022 Report Posted April 5, 2022 On 4/4/2022 at 8:07 PM, oisin650 said: Folks, this is not a Hot Start issue. You need to push IVAO client teams to work on this. You will notice that X-Pilot works perfectly. there are not two or three such clients .. push each one? can do as requested? one checkbox to disable alternative height calculation
KPDover Posted April 6, 2022 Report Posted April 6, 2022 Another Pilot2ATC user here. I'm glad it seems like this will be a non-issue in X-Plane 12, but in the meantime, can we please have a temporary checkbox to fix the issue?
Pils Posted April 12, 2022 Report Posted April 12, 2022 https://virtualsky.ivao.aero/pilot-client-changelog/ Thanks for your patience and lobbying of IVAO developers. This will be implemented in the next update. 1
Recommended Posts