Hi

In general terms, I'm pleased with the long-awaited update.  I pretty much only fly in VR and:

- it loaded OK (it's still a quirky process but, in relative terms, it went OK)

- the Task Bar works!!!!   While the previous Cntrl-0 workaround at least meant VR users could run the sim at all over the past 2 months, it would randomly** repeat the problem during a flight - and lifting the headset when you need two hands to press the Cntrl and 0 while being 500' from the tarmac was 'a bit of an immersion killer' 😉 .   So it is a great, great improvement that it is, at last, fixed

- most of the rest also still works

 

**it might not be random and, instead, be linked with the issue below

 

But I have an oddity and, before I log it, wonder if anyone else has noticed the same.

- I have done a few test flights on a flight plan I am familiar with and using a variety of aircraft, both generic and 3rd party.  The flight is Sywell EGBK to Birmingham EGBB Runway 33.  I am using VOR and ILS navigation/autopilot.  I use mouse for manipulating the Task Bar and some of the controls, with hotas for pitch/yaw/roll/throttle/flaps/brakes/mixture

- take off is normal, as is cruise, as is the beginning of descent

- however, sometimes during the descent, but sometimes on the runway or taxiway off, the hotas freezes.  No buttons or axes work - even the VR/2D button I have assigned

- the controls can still be manipulated using the mouse.  And using them seems to re-engage the hotas

 

At first, I thought it was either the hotas or the 3rd party aircraft (JF Warrior and JF Arrow) but exactly the same thing happened at exactly the same stage of the flight with the stock Cessna 172 G1000

 

And, back to the ** observation...remember that I said that the need to hit Cntrl-0 to use the task bar or task bar drop downs would 'randomly repeat' before the update?  Well, come to think of it, once Cntrl-0 had been hit at the beginning of the flight, all was good with the Task Bar...until the approach.  It was always here that the Task Bar would often stop working again.  Might be linked, might be a coincidence, might be just my system.

 

Anyone else lost their hotas mid flight or, particularly, on approach or landing since the update? 

Edited January 9, 20224 yr by AJZip

It's a new bug for VR found in beta but won't be fixed until SU8 - When your mouse pointer is over a Toolbar window it renders the controller input null & void. Simply move the mouse, Voila!

 

 

3 hours ago, MarcG said:

It's a new bug for VR found in beta but won't be fixed until SU8 - When your mouse pointer is over a Toolbar window it renders the controller input null & void. Simply move the mouse, Voila!

 

 

Ah!

Great info, @MarcG   - thanks 🙂

I'll try it out and add a 'resolved' to the thread title if it does the trick  

4 hours ago, MarcG said:

It's a new bug for VR found in beta but won't be fixed until SU8 - When your mouse pointer is over a Toolbar window it renders the controller input null & void. Simply move the mouse, Voila!

Good to know, thanks! I thought something was wrong with my peripherasls. 

On 1/9/2022 at 4:01 PM, MarcG said:

It's a new bug for VR found in beta but won't be fixed until SU8 - When your mouse pointer is over a Toolbar window it renders the controller input null & void. Simply move the mouse, Voila!

 

 

Yup - confirmed.  When the mouse cursor  is on either the Task Bar or any of the pop up panels (ATC/Checklist/etc) nothing on the HOTAS works.  When you move the cursor anywhere else, the HOTAS works normally.  Thanks again, @MarkG.  I'll add a 'resolved' to the thread title.

3 minutes ago, AJZip said:

I'll add a 'resolved' to the thread title

Or not - not sure how to change the title.  This forum works a bit differently to others I use.  If I find out how, I'll amend it.  If not, it won't take readers long to see the solution 😉

4 minutes ago, AJZip said:

Or not - not sure how to change the title.  This forum works a bit differently to others I use.  If I find out how, I'll amend it.  If not, it won't take readers long to see the solution 😉

There is a time limit for editing a post (24 hours, I think). You could report your post (upper right of your post) and ask a moderator to change the title for you.

...jim

 

34 minutes ago, JimBrown said:

There is a time limit for editing a post (24 hours, I think). You could report your post (upper right of your post) and ask a moderator to change the title for you.

...jim

 

Thanks, Jim