Everyday I fly this beauty, I stumble on minor difficulties: as the screenshot below shows the altimeter doesn't allow me to dial 10.500 ft and by turning the altimeter knob, which only can be set for hundreds or thousands, I'm not able to get nice round numbers. Unless I missed something?
Puk
Alitude setting
-
- Senior Master Sergeant
- Posts: 2438
- Joined: 15 Mar 2016, 08:23
Re: Alitude setting
Hi.
I can dail in anything right up to 50000ft on the gauge the large knob for thousands , small knob for hundreds and units of 1 or more.
regards alan.
I can dail in anything right up to 50000ft on the gauge the large knob for thousands , small knob for hundreds and units of 1 or more.
regards alan.
- Nick - A2A
- A2A Captain
- Posts: 13734
- Joined: 06 Jun 2014, 13:06
- Location: UK
Re: Alitude setting
Puk,
This issue hasn't cropped up before, including in beta testing. Does the selected altitude ending in "99" persist between simulator sessions, or if not, is it something you've been able to reproduce?
For troubleshooting, some info on host sim type and any other add-ons active is always helpful.
Thanks,
Nick
This issue hasn't cropped up before, including in beta testing. Does the selected altitude ending in "99" persist between simulator sessions, or if not, is it something you've been able to reproduce?
For troubleshooting, some info on host sim type and any other add-ons active is always helpful.
Thanks,
Nick
Re: Alitude setting
Hi Nick,
At least it occured during the sessions of yesterday and today, so It certainly seems to be a persisting issue.
Info:
Windows10
FSX SE
MCP COMBO
TPM
Multi Panel
Cessna Yoke + 2 quadrants
BIP
FIPS
Rudder Pedals
Chaseplane
Spad.Next (i.c.w. vfips)
AS2016
I'll do some more testing tomorrow; it might have something to do with the use of the MCP combo box which does show rounded numbers btw.
I'll let you know,
Puk
At least it occured during the sessions of yesterday and today, so It certainly seems to be a persisting issue.
Info:
Windows10
FSX SE
MCP COMBO
TPM
Multi Panel
Cessna Yoke + 2 quadrants
BIP
FIPS
Rudder Pedals
Chaseplane
Spad.Next (i.c.w. vfips)
AS2016
I'll do some more testing tomorrow; it might have something to do with the use of the MCP combo box which does show rounded numbers btw.
I'll let you know,
Puk
Re: Alitude setting
I'm getting this as well, but only when adjusting the altitude via the VR Insight MPanel (which I usually don't do..).
You can get rid of that using the mouse.. Dial all the way to 0 and then back where you want it.
Gesendet von meinem F8331 mit Tapatalk
You can get rid of that using the mouse.. Dial all the way to 0 and then back where you want it.
Gesendet von meinem F8331 mit Tapatalk
Kind regards, Matthias
Re: Alitude setting
Thanks guys for your responses, but as I suspected it's the MCP combo that's causing the wrong altitude selecting numbers. Didn't had this issue before with all the other A2A planes.
Puk
Strangely enough the same issue appeared after I had assigned some buttons (There're no dial knobs on my other hardware) to "AP Altitude Value (FSUIPC:0000:07D4)". So, if I raise or lower the altitude etting through FSUIPC by 1000, 100, 10 the display still gives me f.i. 2.999.
Must be a bug I think?
Puk
Strangely enough the same issue appeared after I had assigned some buttons (There're no dial knobs on my other hardware) to "AP Altitude Value (FSUIPC:0000:07D4)". So, if I raise or lower the altitude etting through FSUIPC by 1000, 100, 10 the display still gives me f.i. 2.999.
Must be a bug I think?
Last edited by Puk on 24 Sep 2018, 03:51, edited 1 time in total.
- some1 - A2A
- A2A Lieutenant Colonel
- Posts: 1828
- Joined: 03 Aug 2008, 11:56
Re: Alitude setting
Yes, it looks like the hardware introduces some sort of rounding errors to altitude selector value. I adjusted the code to handle that, so it will be better in the next update
Michael Krawczyk
Re: Alitude setting
Even after the latest update the issue still persists, unfortunately. No big deal, but as I'm using the MCP combo a lot (makes life easier that way) it would be nice to have this fixed.Yes, it looks like the hardware introduces some sort of rounding errors to altitude selector value. I adjusted the code to handle that, so it will be better in the next update
_________________
Michael Krawczyk
Puk
- some1 - A2A
- A2A Lieutenant Colonel
- Posts: 1828
- Joined: 03 Aug 2008, 11:56
- some1 - A2A
- A2A Lieutenant Colonel
- Posts: 1828
- Joined: 03 Aug 2008, 11:56
Who is online
Users browsing this forum: No registered users and 4 guests