Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

VR Mouse controls on stock A320 & 747 quirky?

Featured Replies

Hi

I'm hoping that someone has the 'gem of a solution' to my confusion on manipulating the controls of the Asobo 747 and A320neo

I am finding that for some, the left hand mouse button lights up the control, but no other buttons seem to be able to manipulate it; others work sometimes but not other times.  I've tried the default mouse settings, I've tried altering the 'secondary action' and 'tertiary action' designations of the middle push and right hand buttons but it remains a bit of a lottery whether the controls work or not.

An example:

The 747 auto-throttle switch.  Sometimes it lights up blue, but there seems to be no mouse action that will switch it off (which makes landing a challenge!), even though the mouse works perfectly well with the identical 'FD' toggle switch next to it

A320 - enabling the Autopilot controls (pressing in the twist knob for, eg, activating the heading control).  The mouse cursor lights up the control in blue, the left button gets its attention waiting for the enabling action but the expected right button press doesn't actually enable it

Both - the landing lights/etc/ toggles.  I can light up the switches in blue and even get them to turn orange, but NOTHING I do with the mouse will toggle the switches

Is just me? 

Edited by AJZip

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Author

OK - I've sat in a darkened room for a bit and tried to work through the issues separately and logically.

The A320 enabling of the autopilot controls.  Taking the Heading Mode for an example:

Using the VR mouse with 'Default' bindings, then there are three bindings set up for the Heading Mode

- one is for twisting the knob.  This works fine

- another is for 'Engage Selected Heading Mode'.  By default, this is the middle wheel button and, in the cockpit graphics, momentarily pulls the knob OUT

- a third is for 'Engage Managed Heading Mode'.  Here, the default mouse button is the right button and, in the cockpit graphics, momentarily pushes the knob IN

 

So this might be my understanding.  I thought on a 320, you pushed the heading button to activate the Heading Mode.  Apparently you pull it.  This, in the MSFS modelling does indeed engage the Heading Mode and pushing it doesn't.

I can live with that...but, then, what exactly does 'Engage Managed Mode' do?  Engaging this by pushing the button does nothing as far as I can see.  Anyone know? 

 

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Author

Just realised I've got this in the wrong section.  If a mod is passing can you pop it into the VR section?

Thanks

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.