Hi, i have the same issue and i’ve notice it happen when i use my controller to change the view (with Hat and button for instrument views.)
It look like every interactions with the camera (if the mouse is not used) is considered as a controller interaction (logic) but it keep the mouse cursor position as reference point for interaction.
In addition it considers using a flight controller (in exemple, the hat on a flight joystick) as the same than the right joystick interaction of a Xbox controller.
Below, a video of the issue (notice where the mouse cursor is placed):
For this video, i used a Thrustmaster T16000 joystick. No gamepad/Xbox controller plugged.
When the camera move from a position to another, i use buttons of the joystick (associated with the instrument views feature).
As this involves the Fenix A320 and PMDG 737, I am moving this to Aviate, Navigate, Communicate. Bug Reporting Hub is for first-party bugs on the base sim with aircraft made by or contracted by Microsoft or Asobo only.
You could try contacting Fenix and PMDG and they could work to resolve the issue.
Can you show the bug in effect on first party planes?
I’ve only ever seen that white dot a single time, when switching to an external view, and I could jot replicate. I think I was in the Cirrus Vision at the time.
I also see the white boxes around some instruments, but only after I have used the hat switch to adjust my view, even the reset view button on it.
Hi, below you can find the non-exhaustive list of default aircraft (non third-party).
The procedure used to reproduce and detect if the issue occurs is described below:
Center view (If default view is offset to screens, tilt-down camera to have a visual with them.)
Place the mouse cursor on a screen
Pan the view with the controller to hover screens with the last position of the mouse cursor (relative to your computer screen)
Use an instrument view button and place the mouse cursor on the screen
Center view or exit instrument view then, return to it.
No gamepad/Xbox controller used. Thrustmaster T16000 used. Camera control set on joystick hat and instrument view set on joystick buttons (legacy settings, no third-party software).
Airbus A320neo 🟢 Not impacted
Bell 407 (Garmin) 🟢 Not impacted
Boeing 747-800 🟢 Not impacted
Boeing 787-10 🟢 Not impacted
Boeing F/A-18E/F 🟢 Not impacted
Cirrus SR22 🟢 Not impacted
CubCrafters NXCub 🔴 Impacted (https://i.imgur.com/D2E1V4f.mp4)
CubCrafters XCub 🔴 Impacted (https://i.imgur.com/LCIUKkn.mp4)
DG Aviation DG-1001E 🟢 Not impacted
Daher TBM 930 🟢 Not impacted
Diamond DA40NG 🟢 Not impacted
Diamond DA62 🟢 Not impacted
Diamond DV20 (Garmin) 🟢 Not impacted
Darkstar 🔴 Impacted (https://i.imgur.com/VZxuThu.mp4)
Extra 330LT 🟢 Not impacted
Flight Design CTSL 🔴 Impacted (https://i.imgur.com/0IyPhs5.mp4)
Guimbal Cabri G2 (Garmin) 🔴 Impacted (https://i.imgur.com/aPhq5PD.mp4)
ICON A5 🔴 Impacted (https://i.imgur.com/N05CIng.mp4)
JMB Aircraft VL-3 🔴 Impacted (https://i.imgur.com/bC7cFhN.mp4)
Pilatus PC-6 (G950) 🟢 Not impacted
Pipistrel Virus SW121 🟢 Not impacted
Robin Cap10 (Garmin) 🟢 Not impacted
Beechcraft Baron G58 🟢 Not impacted
Beechcraft Bonanza G36 🟢 Not impacted
Beechcraft King Air 350i 🔴 Impacted (https://i.imgur.com/WJQBnt9.mp4)
Cessna 208B Grand Caravan EX 🟢 Not impacted
Cessna Citation Longitude 🟢 Not impacted
Cessna Citation CJ4 🟢 Not impacted
Cessna 172 Skyhawk (G1000) 🟢 Not impacted
Volocopter VoloCity 🔴 Impacted (https://i.imgur.com/BCsi8xu.mp4)
Pretty sure on my side, though can’t confirm 100%.
Both appeared at the same time
Both are related to pointer position
Both are related to interaction with cockpit buttons and knobs
Both are happening on pretty much any airplane (can’t think of any that isn’t affected except the ones that don’t have a glass cockpit, nevertheless the bug is probably the same, it’s just not affecting what isn’t there)
This type of testing and documentation (including reproduction steps) is extremely useful to the development team as they work to resolve this issue. I want you to know we referred the devs to your post here directly, and they found it very valuable.
For me its not related to cockpit interactions at all. I don’t need to click the mouse, just move it before or after using my quick view hat switch on my yoke.
If I move the mouse point to a known location, in reference to a glass instrument, then move my head tracker so that the pointer would be over that display, I don’t get the white border.
If I repeat the above, but before I move my head I press any input on my hat switch, for quick views, including pushing its centre button, then move my head I will get the white line.
The hat switch views puts it into a state where the white lines appear. If I move the mouse at all after pressing a hat switch button, then I won’t see it.
This is why I thought I never had this issue as I hardly ever use these hat switch views since getting a head tracker, and usually fly stream gauge planes.
It wasn’t until I got the Cirrus Vision jet that I noticed this.
Happens in the CRJ as well. I first saw it about 2-3 weeks ago and now it’s reproducible 100% of the time. I didn’t change anything in settings or controllers and I had been flying the CRJ for months before the issue began. It just started happening out of the blue, possibly after an MSFS update.
I have the same issue
No matter inside cockpit or outside.
Any aircraft
Also, it is accompanied by the mouse flickering and Im unable to controll my Airbus anymore
No push or pull for altitude or heading/NAV
New Beta-Update released. The release notes prove that the problem is probably solved and 2 options have been added to the menu to turn the behavior on and off.
Has anyone been able to test this?
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
