https://bugs.winehq.org/show_bug.cgi?id=40336
Adam Hirst adam@aphirst.karoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
--- Comment #2 from Adam Hirst adam@aphirst.karoo.co.uk --- OK so I decided to run apitrace trace wine /path/to/Freelancer.exe and do as little as possible to reproduce the error:
* click through a "GPU not recognised" dialog * Load Game from main menu * (saved game was on a planet), watch the Planet "scenescape" animation * Click "NavMap" icon * see NavMap with 'excess' border * Exit game by Alt+F4
The resulting file was rather large (I think about 170MB), but I uploaded it to Dropbox. I hope it's useful.
https://dl.dropboxusercontent.com/u/3219541/logs/wine-preloader.trace
I've already cross-posted this at my wine-staging bug report ( https://bugs.wine-staging.com/show_bug.cgi?id=494 ), where I noted that the issue is still present with the following set-up:
mesa 13.0.3-1 wine-staging 2.0-1 linux-ck-ivybridge 4.9.6-1 xf86-video-intel 1:2.99.917+747+g028c946d-1
Hardware is here an i7-3520M with just the Intel (4000?) graphics.