[Bug 40336] New: Freelancer: Background Texture for in-game "NavMap" spreads across entire screen (Intel only)
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(a)winehq.org Reporter: adam(a)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. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40336 --- Comment #1 from Matteo Bruni <matteo.mystral(a)gmail.com> --- If this only happens on Intel, updating the Mesa package might be worth a shot. If that doesn't help, you should probably open a Mesa bug. You might also try to take a trace of the game with apitrace and upload it somewhere (it's going to be too big for attaching here). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40336 Adam Hirst <adam(a)aphirst.karoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux --- Comment #2 from Adam Hirst <adam(a)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. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40336 --- Comment #3 from Adam Hirst <adam(a)aphirst.karoo.co.uk> --- I have opened a Mesa bug report. https://bugs.freedesktop.org/show_bug.cgi?id=99617 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40336 --- Comment #4 from Adam Hirst <adam(a)aphirst.karoo.co.uk> --- 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. Regarding the trace: as I mentioned upstream, the URL has moved, this link *should* work: https://www.dropbox.com/s/zbnlcnuq1rypsy9/wine-preloader.trace?dl=0 I will also report this fact to Mesa. 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) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40336 --- Comment #5 from Adam Hirst <adam(a)aphirst.karoo.co.uk> --- 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 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40336 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40336 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #6 from Matteo Bruni <matteo.mystral(a)gmail.com> --- (In reply to Adam Hirst from comment #4)
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.
Thank you for the update, it was probably fixed in Mesa. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40336 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Matteo Bruni <matteo.mystral(a)gmail.com> --- Fixed elsewhere, closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org