Created attachment 129255 [details] The background texture for the Nav Map spreads the entire screen, which is actually supposed to have your current 3D environment visible outside it. I will reproduce here the important details of this bug, which I have already posted at https://bugs.wine-staging.com/show_bug.cgi?id=494 and at https://bugs.winehq.org/show_bug.cgi?id=40336 . I have been recommended to open a mesa bug by several members of the wine community. --- A feature of the HUD in this game is the "NavMap", a navigation map which overlays onto the current gameplay and displays a map either of the current star-system, or of the whole galactic sector, and with some additional relevant information. This HUD, like the other gameplay menu-elements, is supposed to simply overlay onto the screen, being transparent/translucent on the outside. Indeed, one can also interact with some game/menu elements outside said window even if it is currently displayed. However, the observed behaviour (attached) for the "NavMap" is that the background texture for the "map" portion, a texture of a star-scape, is instead displayed across the entire screen. The user can still interact with the (now invisible!) objects behind the texture. Some text in the NavMap window is also obscured. This behaviour occurs on a clean install of the game, with the official 1.1 patch, and with Jason's Extended Patch 1.20; also on just the Demo version of the game. http://dl.4players.de/f1/freelancer/freelancer_demo.exe --- 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 --- 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. Apologies in advance if I have erroneously categorised this report.
(In reply to Adam Hirst from comment #0) > https://dl.dropboxusercontent.com/u/3219541/logs/wine-preloader.trace The trace file doesn't seem to exist anymore
(In reply to Matt Turner from comment #1) > (In reply to Adam Hirst from comment #0) > The trace file doesn't seem to exist anymore Ah, sorry about that. I had forgotten about the recent Dropbox changes. Here's a fresh public link to that same file: https://www.dropbox.com/s/zbnlcnuq1rypsy9/wine-preloader.trace?dl=0
Might there be any update on this issue?
It seems that in the interim, this bug has been fixed. I'm testing using 2 very similar machines, a T430 and an X230 both with Intel 4000 graphics chips. Both using the .trace and when installing the game from scratch, the issue no longer appears. I also reported this fact to WineHQ. It would, however, be useful/interesting to know exactly when this got fixed. Current software versions: linux 4.16.5-1 (also linux-ck-ivybridge 4.15.18-1) xorg-server 1.19.6+13+gd0d1a694f-2 mesa 18.0.1-1 xf86-video-intel 1:2.99.917+829+gd7dfab62-1 wine 3.7-1 (also wine-staging 3.7-1)
I've had to move the .trace again. It's now compressed, too. Sorry for the noise. https://www.dropbox.com/s/0i9rce5zunbc431/freelancer.trace.7z?dl=0
Resolving as fixed as per comment #4
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.