[Bug 42505] New: Physx 3.4 new GRB feature (Gpu rigid bodies) doesn' t work on GPU on WineStaging 2.2
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@winehq.org Reporter: rtfss1@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?
https://bugs.winehq.org/show_bug.cgi?id=42505
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
https://bugs.winehq.org/show_bug.cgi?id=42505
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Product|Wine |Wine-staging CC| |erich.e.hoover@wine-staging | |.com, michael@fds-team.de, | |sebastian@fds-team.de
--- Comment #1 from Sebastian Lackner sebastian@fds-team.de --- The NVAPI implementation is currently only included in Wine Staging, so moving to the Staging product.
https://bugs.winehq.org/show_bug.cgi?id=42505
--- Comment #2 from oscarbg rtfss1@gmail.com --- Posting simple exectuable program: https://www.dropbox.com/s/r3q9kj8q2sb51q6/physxgrbtest.tar.gz?dl=0
run: wine SnippetHelloGRB.exe
Shows: fixme:nvapi:unimplemented_stub function 0x36e39e6b is unimplemented! ....\cudamanager\src\CudaContextManager.cpp (404) : info : No PhysX capable GPU suggested.
....\cudamanager\src\CudaContextManager.cpp (405) : info : 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
https://bugs.winehq.org/show_bug.cgi?id=42505
ChinaphoneOne chinaphone.185+winehq@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chinaphone.185+winehq@gmail | |.com
--- Comment #3 from ChinaphoneOne chinaphone.185+winehq@gmail.com --- You can try to install older PhysX version e.g. 9.14.0702 which don't use 0x36e39e6b function to init. Then remove PhysXDevice64.dll (and PhysXLoader64.dll (?)) from application root directory.
With this I have more GPU load (15%-20% vs 3%-6%) and no PhysX warnings in SnippetHelloGRB.exe.
-
wine-bugs＠winehq.org