Thanks for the confirmation! Then it seems like this is unfortunately too low-level for us to be able to debug the issue. Perhaps Asobo could help, but I am not sure they want to put resources into debugging issues that do not occur without a panel like ours triggering them…
At the same time, we are at a loss - they have the source code for the simulator and are the only ones who can meaningfully debug this. We could go on a chase and try removing/changing things piece by piece until the issue stops, but it is not a priority for us seeing as even the MSFS developers consider the DX12 option unstable, as far as I know.
I will write this down and add it to our backlog for investigation, but as mentioned it will likely have low priority unless this starts occurring for DX11 too. Sorry for the inconvenience!
Kind Regards,
Malte