Thanks very much !
1 Like
Thatâs what I meant when using VR. VR users need to supersample in order to achieve good visuals with much lower resolution than a 4k monitor. Every part of the panel that has textures with worn out effects or lower resolution shows much more unsharpness and contrast then on a monitor.
So for instance, when I look at this cockpit in VR I can read the faceplates of the instruments sharp and clean and also the display of the Garmin. But the rest is unreadable and looks not sharp. Plackards are unreadable and the tekst above switches too. This happens in all planes however the panels with clean surfaces do look better. Especially the default Asobo planes.
Thanks - copied and pasted to a handy text document for quick reference.
1 Like
nice shots
I know we arenât supposed to request official support on these forums, so what is the best way to log a support ticket with some of the issues we have observed so far?
Unless it is serious or causing CTD then I think everything is covered already ?
You have something new to add ?
you could try PM
Hobbs meter doesnât work, although the state.cfg does record the engine time. It reports 0.
No icing on windscreen or fuselage. Coupled with no current draw from the anti-ice systems. Pitot heater does show current draw though.
Iâm not at my machine to check others but these are what I found last. You hadnât commented on these so assumed you may have missed them.
maybe not commented on all. But all Noted
3 Likes
Thanks. I think this is going to be my plane of choice for the next few weeks at least. 
Just remembered another.
The backup altimeter knob doesnât work. 
Oh, and you were right about the fuel selectors. On my next flight, the engine started without me having to touch those that time, with them pointing straight down, but before it definitely didnât work until I swapped the feeds. If I can replicate I will.
1 Like
Night you arenât easy to PM.
I have an installation issue. âSerial Number is Not Validâ - I have emailed.
My sense of aesthetics says: ânoooooooo âŠ!!!â 
4 Likes
I had a really nice flight in this last night.
Awful weather so used some GPS NAV, some VOR NAV, and a ILS approach all the way down to DA. Everything worked pretty well, Autopilot did its job when engaged.
I noted most of the things mentioned above, just wanted to add a couple of other things I noted, sorry if they have been noted before, but I donât recall seeing them.
I donât seem to be able to enter a Freq in to the KN62A and the format does not look correct for the entry of a frequency.
For me the OAT gauge is reporting 10 degrees higher than the actual out side air temp. Below it is at approx 19 where the actual for where this was taken is currently 9.
Yes, this is working. But I think what was meant are the camera positions that you can normally change through by tipping the hat switch of the joystick up and down (at least that is the default functionality for my Thrustmaster TCA). This is actually quite handy, in order to get to the landing view and the instrument views. So I guess it should be an easy fix to create/assign the views to this functionality.
That looks like it is stuck in a test mode, except not all of the elements are actually lit.
The DME should have two modes, if the Arrow implementation is to go by. It can either be driven by NAV1/NAV2, controlled by a flip switch in the Arrow, or by a third frequency on the DME itself. Which it keys on is controlled by a little slide switch. Iâve not looked at the DME yet so perhaps that is INOP?
So the slide switches work. I can turn the unit ON/OFF for example.
And it does seem slaved to NAV1, rather than NAV2. And if I change frequencies on the 530, that works also.
Biggin Hill VOR 115.10
Brookmans Park 117.50
When you then move the slider from RMT to FREQ, you see the frequency set on the DME itself.
However this cannot be adjusted with the rotaries to the right. Both rotaries turn, but they do not change the frequency on the DME. Compare this to other DME fitted aircraft like the Arrow.
ETE also doesnât appear to work:
I have only used the DME in Nav1 and it worked fine.
Yes I am aware of that thank you, but that is the frequency for NAV 1 only.
As @hobanagerik points out below normally you could enter a frequency in to KN62A and track another VOR and I do that a lot in the Arrow. Comes in handy at times for certain procedures.
2 Likes
It doesnât show you how long it will take to get to that NAV aid. This instrument definitely needs some work. FREQ, and GS/T are effectively useless at this time, and RMT half works.
1 Like
I dont own the plane but thatâs exactly what i was seeing from the first screenshots. Lots of vertices, doesnt look like its up to the modeling standards and thats why i was never interested in this plane.
1 Like