Created attachment 143629 [details] apitrace and video It was observed some graphical bugs on Microsoft Flight Simulator X: Steam Edition when playing it on Steam using Steam Play. Steam Play version used was 3.16-8 Beta. One of the graphical bugs happen on the menu, where flight settings can be chosen. The bug starts when visualizing the chosen aircraft. Nearly the entire interface becomes black, with only the aircraft preview visible. The other graphical bugs happens on the simulation: there are many graphical errors happening, with the sky blinking very fast, polygons appearing randomly and menus not loading text. SEIZURE WARNING: the attached file has an apitrace and a video showing the issue. The apitrace open multiple windows, one of them shows the menu while other shows the simulation, and it replays considerably better (but not bug free) when using i965 instead of iris. SEIZURE WARNING: significant portions of the screen blink very fast. System specifications: Processor: Intel Core i3-6100U; Video: Intel HD Graphics 520; Architecture: amd64; RAM memory: 8 GB; Mesa: 19.1.0-devel (git-d086d16b81); Kernel version: 5.0.0-7-generic; Distribution: Xubuntu 18.04.2 amd64.
Still some blinking but this is dramatically better now.
With Mesa git-09e4771af9, I'm no longer observing the graphical bugs on the simulation part of this game. Other games with similar issues, as The Ruins of the Lost Kingdom CHRONICLE, Recettear: An Item Shop's Tale and Tachyon: The Fringe no longer have graphical bugs too. One thing I don't understand is why, even when in game there are no longer graphical bugs, the apitrace still shows some bugs. This was observed before with Euro Truck Simulator 2, where the game was fixed but the apitrace was still showing bugs. The menu problems seem to be unrelated to Mesa and seems to be a Wine bug.
It sounds like it's working better these days, so I'm going to close this for now. If there's still something to fix here, feel free to reopen!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.