November 2016 - Wine-Bugs - list.winehq.org

[Bug 32752] Xanadu NEXT 3D does not show properly

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=32752 --- Comment #10 from ~J~ <funtimeschaos(a)rocketmail.com> --- Tested with 1.9.22-staging. It seems that the 3D models do render now (although with rainbow-like textures instead), so I guess this bug should be closed and a new one opened for the texture bug. -- 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.

Nov. 3, 2016

[Bug 23676] Arcanum essentially unusable due to graphics errors

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=23676 --- Comment #19 from Tim Savannah <kata198(a)gmail.com> --- So I gathered trace of wined3d. Here's what I do 1. start wine 2. a 2d menu pops up, I click "single player" then "load game", then push a button to load the game 3. Game loads, I walk around and scroll the camera. Scrolling the camera is the issue. On mesa, the textures don't seem to scroll with the camera sometimes, they just repeat. This causes a "blurring" effect. It's less obvious in grasslands but in cities with buildings it's easy to see the texture repeat instead of scroll. Almost like it's moving the texture, but not clearing the old position. On nvidia, everything works dandy. -- 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.

Nov. 3, 2016

[Bug 23676] Arcanum essentially unusable due to graphics errors

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=23676 --- Comment #18 from Tim Savannah <kata198(a)gmail.com> --- Created attachment 56023 --> https://bugs.winehq.org/attachment.cgi?id=56023 wine d3d trace using nvidia This is the wine d3d trace using nvidia -- 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.

Nov. 3, 2016

[Bug 23676] Arcanum essentially unusable due to graphics errors

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=23676 --- Comment #17 from Tim Savannah <kata198(a)gmail.com> --- Created attachment 56022 --> https://bugs.winehq.org/attachment.cgi?id=56022 wine d3d trace using mesa This is wine d3d trace using 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.

Nov. 3, 2016

[Bug 23676] Arcanum essentially unusable due to graphics errors

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=23676 --- Comment #16 from Tim Savannah <kata198(a)gmail.com> --- Given that I can both reproduce it working and not working... if you guys think there's some way that we can handle it within wine. It COULD BE that maybe we're doing something invalid in the wined3d layer, that nvidia's libGL handles one way and mesa's handles another. Or maybe the difference could be a feature support, i.e. maybe the nvidia card supports some extension that is being used, let's just say "GL_NV_path_rendering" (I'm picking one out of thin air that nvidia supports but mesa does not. Not saying that function is in any way related). If we have a conditional like: if supports(GL_NV_SOMETHING) { .. do it this way .. } else { ..emulate that function ... } our "emulate that function" code could be broken. I can provide a trace of wined3d, would that be the most useful thing? -- 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.

Nov. 3, 2016

[Bug 23676] Arcanum essentially unusable due to graphics errors

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=23676 Tim Savannah <kata198(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kata198(a)gmail.com --- Comment #15 from Tim Savannah <kata198(a)gmail.com> --- Hey guys, I can confirm that this is still happening, HOWEVER, there is a way around it for some people. I have one of them laptops with an intel for standard graphics and an nvidia card which can be enabled for 3D (nvidia optimus). What I find is that this happens when I just run wine directly, but NOT when I use "optirun wine Arcanum.exe" (this will launch arcanum using the geforce card for display, not the intel card). When I run it through the nvidia card (and thus nvidia's libGL), I do NOT get the issue. But when I run it through the intel card and mesa's libGL, I DO get the issue. This leads me to believe that the issue is likely with mesa's libGL, and not wine. I get the same results using BOTH wine's implementation of dx9, and microsoft's (using the dx9 dll's as "native"), which again suggests that the issue is not within wine but mesa. Prior to 1.9.22 I was getting a rolling warning on the console, something about "stub! texture blit not supported in software mode" I'd look up the exact message but it's gone now ( I guess was implemented between 1.9.21 -> 1.9.22 ? ) So... anyone else got the nvidia driver and can confirm it works? Anyone on just plain mesa can confirm it doesn't work? That would then support my theory. Now as to what to do about it.... ya got me! -- 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.

Nov. 3, 2016

[Bug 23154] APB: All Points Bulletin crashes on startup with Wine-Mono

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=23154 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio(a)earthlink.net, | |winetest(a)luukku.com --- Comment #8 from winetest(a)luukku.com --- (In reply to Olivier F. R. Dierick from comment #7) > I think the bug is for the original 2010 version of All Point Bulletin, not > APB: Reloaded. > > The former was discontinued in 2010 after the company went bankrupt. The > later is a reboot from another company. > > I see no point to use the 2010 version anymore. > > The bug should be closed wontfix in my opinion. -- 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.

Nov. 3, 2016

[Bug 41647] TFM Music Maker controls are not usable

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=41647 Grazvydas Ignotas <notasas(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download -- 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.

Nov. 3, 2016

[Bug 41647] New: TFM Music Maker controls are not usable

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=41647 Bug ID: 41647 Summary: TFM Music Maker controls are not usable Product: Wine Version: 1.9.22 Hardware: x86 URL: http://sega4ever.power-heberg.com/Download/tfmmaker152 .rar OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: notasas(a)gmail.com Distribution: --- After starting the program, click "Instruments" tab and try to adjust any of the knobs. Nothing useful noticed in the terminal output. Just a guess it's an issue message handling, so selected user32 component. Tested to be broken on vanilla wine-1.9.22, wine-1.9.22 (Staging) and wine-1.6.2. Works correctly on real Windows 7 and 8.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.

Nov. 3, 2016

[Bug 41646] crash when I Start the software MTAE

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=41646 --- Comment #4 from Erich E. Hoover <erich.e.hoover(a)wine-staging.com> --- (In reply to winetest from comment #1) > Component seems to be oleaut32 and the location is quite clear. Where it breaks is clear but it's passing in a pointer at address 0x7, which is clearly wrong. The root cause is most likely that the application got back something wrong from somewhere else. -- 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.

Nov. 3, 2016