https://bugs.winehq.org/show_bug.cgi?id=40336
Bug ID: 40336 Summary: Freelancer: Background Texture for in-game "NavMap" spreads across entire screen (Intel only) Product: Wine Version: 1.9.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: adam@aphirst.karoo.co.uk Distribution: ---
Created attachment 54005 --> https://bugs.winehq.org/attachment.cgi?id=54005 Example of erroneous behaviour
This is essentially a repost of Bug #494 on the Wine-Staging tracker, as it turns out that it is not unique to the -staging builds. https://bugs.wine-staging.com/show_bug.cgi?id=494
-----
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 am currently running Wine-Staging 1.9.5 but the bug has been present since at least as early as 1.7.48.
Intel i5-3540M with HD4000 graphics, 16GB RAM. Arch Linux x86_64, Linux 4.3.6 (but at least as far back as 4.1.4). Intel driver 2.99.917+579+g74cd4d0 (but at least as far back as 2.99.917+381+g5772556)
---
Michael Müller from the Wine-Staging tracker tested this on other graphics hardware/stacks and came to the conclusion that the issue is only present on Intel+Mesa.