Please only post bugs that are new in this build, and tag your post with #pc and/or #xbox.
Are you on Xbox, Steam or Microsoft Store version?
Store
Are you using Developer Mode or made changes in it?
No
Brief description of the issue:
When you pop out a touch screen GPS, some buttons are not clickable or have another action than the expected one.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Start a flight with the king air and pop out the MFD. Then try to play with the buttons. ex set a frequency. Some buttons are not working or do another action in the cockpit. This depends on the cockpit view and on the pop out window size (try to resize it and play again with buttons). If you switch to external view, none of the buttons is working. Seems like if the pop out window is transparent to events and some mouse events are sent to the cockpit instead of the window itself.
PC specs and/or peripheral set up if relevant:
I saw similar with the FBW A320 dev version last night - couldn’t click on some of the options on the EFB when this was popped out - spent ages trying to figure out why my throttle calibration wouldn’t work. Also I found that clicking on the EFB when popped out, but not taken external, enabled a sort of “click through” to the sim underneath - I kept clicking the coffee cup in the FBW when I was actually trying to click the popped out EFB.
Sorry to tell you but that’s not a new SU8 issue. It’s been around for ages. I actually think it may be 2 separate issues. The touch not working is one thing and the clicking on one monitor while something else in the main sim window changes is the other.
It should definitely be fixed. But Sling is right. It’s in no way related to SU8. Not even remotely. This bug has been a thing since launch (probably even since alpha) and was reported many times. Then the threads died a slow death and got locked because no one cared enough to push the issue.
Until your GTN was released and became popular, this was considered a “niche” issue that only affected a small subset of cockpit builders. It’s only really something that came to light in the last little while as people started realizing you can use tablets and touch screens with popouts, particularly with your GTN. And now it’s getting a little more widespread attention.
And not only does it not work right, but they added another bug in SU6 when they “fixed” mice not always working right in popouts. That’s the second issue you mentioned. Since SU6, touching a popout (like the GTN) moved to another monitor will register touches in the main sim window as well. So trying to work your GTN750 on Touch Monitor #2 will be registering touches in your virtual cockpit on Monitor #1. This can potentially flip switches, open the storm window, etc. So you’re correct the 2 issues are related, but they have nothing to do with SU8.
As I posted on your Discord last week, this bug in the sim is the only thing that has me using the TDS GTNXi over your GTN750 (despite owning a lifetime license for your GTN). I would really love to see this issue fixed. I’ve been bringing this up constantly since the first days after launch. But it would appear this issue isn’t on Asobo’s radar.
A few examples of reports of this issue since launch (first dating from Aug 20, 2020).
It’s a known issue by a small part of the community. I’d be amazed if this is even on Asobo’s radar at all.
EDIT:
Here’s a link to the barely alive wishlist thread that’s managed to somehow stay alive since Sept 2020. over a year, it’s only managed to garner 84 votes.
Thanks for these explanations.
Hope Asobo will take care of that soon.
I can add the touch screen events not sent to HTML gauges that prevents using a tablet.
Unfortunately, that won’t do anything. To use the GTN with a tablet, you need to use something like SpaceDesk or Duet. It then turns the tablet into a wireless monitor for the PC. And the touch issue is still affected just as if it was a hard-wired touch screen. Touch input still doesn’t work. Unless you can do something like the MCDU for the FBW A320 (browser-based client that displays the MCDU), that won’t make a different.
There’s another bug on top of that that’s also been around since launch. If your mouse hovers over a popped out window (either from a touch event or just moving your cursor), you lose all control of your hardware in your sim until you move the mouse out of that window. So even IF we could somehow touch the popped out GTN, we’d still have that other issue. Yet another bug that’s been reported repeatedly since launch and ignored.
BTW, in case you’re wondering about how Real Sim Gear GTN bezel manages to work with your GTN - their touch driver for their screen translates touch into mouse up events instead of registering them as touch. That gets around the touch limitation in the sim.
However, it doesn’t get rid of the other bug I mentioned in my last post. Once you use the GTN, you then have to reach for your mouse and move your cursor out of that window to regain control of your physical hardware.
There’s a workaround to that however. If you have SPAD.Next, you can use that (via SimConnect) to take over control of your hardware. In that case, you don’t lose control of your hardware when the mouse is hovering over a popped out window.