Re: CL_DEVICE_NOT_AVAILABLE when creating CLContext with 64-bit Java on GTX 970
Posted by
SuspiciousDroid on
Apr 01, 2016; 7:05pm
URL: https://forum.jogamp.org/CL-DEVICE-NOT-AVAILABLE-when-creating-CLContext-with-64-bit-Java-on-GTX-970-tp4036560p4036580.html
Putting that call in a static block makes the init happen at class load time, instead of the first time you use the API.
I didn't even make it static, I just put it one line above CLContext.create ^^
I also checked with process explorer, but the location of the OpenCL DLL doesn't change between the two versions, both load it from system32.
The only real difference that the non-working version is missing some DLLs, all of which I think are related me including JOGL in the working one.
Here's the list of missing DLLs, just so I don't skip over any details:
- d3d9.dll
- dbghelp.dll
- dciman32.dll
- ddraw.dll
- dwmapi.dll
- glu32.dll
- jawt.dll
- jogl_desktop.dll
- jogl_mobile.dll
- msctf.dll
- nativewindow_awt.dll
- nativewindow_win32.dll
- ntmarta.dll
- nvcompiler.dll <-- maybe it's missing this one? nvidia compiler seems important
- nvd3dumx.dll
- nvoglv64.dll
- nvSCPAPI64.dll
- nvspcap64.dll
- opengl32.dll
- sspicli.dll
- winhttp.dll
- winsta.dll
- wtsapi32.dll
On a side note: Why does JOGL load DLLs used for HTTP and Windows Remote Desktop sessions?