Thanks so much! Yes, it does sound like a dual graphics issue. In some configurations, I think external displays always use the dedicated GPU, so that would track with what you're seeing.
We're still investigating the exact cause of these dual GPU issues, but we've added some experimental options to try and alleviate them in the meantime.
Could you please try going to Preferences > Compatibility & Troubleshooting > change Qt Rendering Hardware Interface to D3D11 from Automatic. You can try OpenGL too, just to see what happens.
In addition, within the same panel at the bottom is a checkbox for Override Chromium GPU Workarounds - try checking this separately, as well as in conjunction with the Qt RHI override above.
I really appreciate you taking the time to try different configurations to narrow down the issue. To give you some insight, Fusion has a few different graphics systems in use at once: the canvas (Dx11, Dx9, or OpenGL), the toolbar and command UI (D3D11, Metal, or OpenGL), and embedded Chromium browser frames (ANGLE to D3D, GL, etc). They all have their own methods for detecting GPUs and different workarounds and shims for working with a given GPU; it could be causing Chromium and the command UI to disagree on the correct configuration, or it could be entirely isolated to the browser frame. We are improving our logging in this area to have a better understanding of the root cause.
Lance Carocci
Fusion QA for UI Framework/Cloud Workflows, and fervent cat enthusiast