February 2018 - Wine-Bugs - list.winehq.org

[Bug 38436] New: Grand Theft Auto V failed to launch
by wine-bugs＠winehq.org Feb. 2, 2018

Feb. 2, 2018

https://bugs.winehq.org/show_bug.cgi?id=38436 Bug ID: 38436 Summary: Grand Theft Auto V failed to launch Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: franklin(a)goodhorse.idv.tw Distribution: --- Created attachment 51297 --> https://bugs.winehq.org/attachment.cgi?id=51297 Backtraces of page fault when launching GTA5 on Linux. When launching GTA5, it crashed with page fault. My GTA5 was installed via steam running on Linux. My steam was installed with winetricks. However, I found that when installing steam with winetricks, it installed 32-bit(x86) version instead of 64-bit version. I wonder if this is why it failed to launch. -- 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.

1 52

[Bug 42330] New: Grand Theft Auto V (Steam): black screen, only audio
by wine-bugs＠winehq.org Feb. 2, 2018

Feb. 2, 2018

https://bugs.winehq.org/show_bug.cgi?id=42330 Bug ID: 42330 Summary: Grand Theft Auto V (Steam): black screen, only audio Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jamesheald(a)linux.com Distribution: --- Created attachment 57087 --> https://bugs.winehq.org/attachment.cgi?id=57087 Console logs Grand Theft Auto V is now able to launch from the launcher but you only have audio and a blank screen. The game also crashes if you get it as far as pressing the play button (Which is difficult as there appears to be an input delay, also you cant see anything with the screen being black). Have tried in windowed mode, enabled virtual desktop, enabled/disabled CMST along with letting the launcher launch GTA V in safe mode. Heres a video of a previous attempt: https://vid.me/KMp4 -- 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.

1 69

[Bug 13332] New: widl fails with unknown embedded type for somedata (0x0)
by wine-bugs＠winehq.org Feb. 2, 2018

Feb. 2, 2018

http://bugs.winehq.org/show_bug.cgi?id=13332 Summary: widl fails with unknown embedded type for somedata (0x0) Product: Wine Version: 1.0-rc1 Platform: Macintosh OS/Version: Mac OS X 10.5 Status: UNCONFIRMED Severity: critical Priority: P2 Component: tools AssignedTo: wine-bugs(a)winehq.org ReportedBy: sachin_bhandare(a)persistent.co.in Created an attachment (id=13211) --> (http://bugs.winehq.org/attachment.cgi?id=13211) Sample IDL file Attached sample IDL file fails with following error. $>widl -I $WINE_HOME/include/wine/windows -I. -s -u -p -h test.idl error: write_embedded_types: unknown embedded type for somedata (0x0) I am using following WIDL version $>widl -V Wine IDL Compiler version 1.0-rc1 Copyright 2002 Ove Kaaven -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

1 18

[Bug 42505] New: Physx 3.4 new GRB feature (Gpu rigid bodies) doesn' t work on GPU on WineStaging 2.2
by wine-bugs＠winehq.org Feb. 1, 2018

Feb. 1, 2018

https://bugs.winehq.org/show_bug.cgi?id=42505 Bug ID: 42505 Summary: Physx 3.4 new GRB feature (Gpu rigid bodies) doesn't work on GPU on WineStaging 2.2 Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rtfss1(a)gmail.com Distribution: --- Hi, Physx 3.4 features a new GRB pipeline running almost all Physx engine features on GPU with great speedup.. Currently it's in late beta: https://github.com/NVIDIAGameWorks/PhysX-3.4 you have to register to obtain but seems final public version will be coming next week GDC.. anyway I compiled this SDK and run a GRB sample.. in Windows runs with great speedup on a GTX970.. Running Wine-Staging 2.2 which supports Physx get: fixme:nvapi:unimplemented_stub function 0x36e39e6b is unimplemented! No PhysX capable GPU suggested. If you have a PhysX capable GPU, verify that PhysX is not set to CPU in the NVIDIA Control Panel. ..\..\SimulationController\src\ScScene.cpp (665) : warning : GPU solver pipeline failed, switching to software ..\..\SimulationController\src\ScScene.cpp (679) : warning : GPU Bp pipeline failed, switching to software so seems nvapi function 0x36e39e6b returns exactly the toogle in Nvidia Control Panel on Windows of running Physx on CPU/GPU as if I change on Windows that toggle to force running Physx on CPU i get exactly same output: No PhysX capable GPU suggested. If you have a PhysX capable GPU, verify that PhysX is not set to CPU in the NVIDIA Control Panel. ..\..\SimulationController\src\ScScene.cpp (665) : warning : GPU solver pipeline failed, switching to software ..\..\SimulationController\src\ScScene.cpp (679) : warning : GPU Bp pipeline failed, switching to software can nvapi function 0x36e39e6b be implemented so GRB works? -- 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.

1 4