nvoglv64.dll detection problem after nvidia driver update

[Anonymous]

Hello,

I have been implementing a plugin for Maya 2017 for a while. It is a physically based simulator and supporting CPU and GPU (cuda) simulation together. Before I updated the nvidia driver version, GPU side of the simulator had been working properly. Right now, even if I roll back the driver, it is not working. I am quite sure the source of the problem is nvoglv64.dll detection issue. I am using nvidia gt 755m (SLI) display card with the latest nvidia driver(378.78). By the way, the same plugin is still working properly in my other machine which has nvidia gtx 580 display card and the latest driver. The only the difference that I observe, that machine reads the nvoglv64.dll. I tried many things such as rolling back the driver to many other versions, rolliing back the cuda, playing with different configuration in nvidia control panel, and even formatting the system and installing a fresh windows 10 with all updates. So, please I really need help in this issue.

Thank you!

Initialized VP2.0 renderer {
Version : 2016.3.71.11. Feature Level 5.
Adapter : GeForce GT 755M/PCIe/SSE2
Vendor ID: 4318. Device ID : 4045
Driver : .
API : OpenGL V.4.5.
Max texture size : 16384 * 16384.
Max tex coords : 32
Shader versions supported (Vertex: 5, Geometry: 5, Pixel 5).
Shader compiler profile : (Best card profile)
Active stereo support available : 0
GPU Memory Limit : 2048 MB.
CPU Memory Limit: 7731.36 MB.
}
OpenCL evaluator is attempting to initialize OpenCL.
Detected 3 OpenCL Platforms:
0: Intel(R) Corporation. Intel(R) OpenCL. OpenCL 1.2 .
Supported extensions: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_dx9_media_sharing cl_intel_dx9_media_sharing cl_khr_d3d11_sharing cl_khr_fp64
1: Intel(R) Corporation. Experimental OpenCL 2.1 CPU Only Platform. OpenCL 2.1 .
Supported extensions: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_dx9_media_sharing cl_intel_dx9_media_sharing cl_khr_d3d11_sharing cl_khr_gl_sharing cl_khr_fp64 cl_khr_image2d_from_buffer
2: NVIDIA Corporation. NVIDIA CUDA. OpenCL 1.2 CUDA 8.0.0.
Supported extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts
OpenCL evaluator choosing OpenCL platform NVIDIA Corporation.
Choosing OpenCL Device GeForce GT 755M. Device Type: GPU Device is available.

[Anonymous]

Please, any ideas?

[Anonymous]

I too had same problem...I went back to Nvidia 372.90 and then in 3D settings I selected the troublesome programs..i.e. Maya and DaVinci Resolve 12.5

Whew! I started to panic for a wile!

Hope it Helps!

-Kel-

[Anonymous]

Ah....a while

[Anonymous]

Thanks for the reply. Well, I tried to turn back to 370.90 but win10 somehow does not allow me to go earlier than 376...

[Anonymous]

Argh! That is also why I left my less than a year old self built machine to have on it only Windows 7 ...ah.....I suggest if you talk to Nvidia, let them know You are not an isolated case, and in meantime I will search for workarounds for your instance of Win 10 installed problem to our similar display/crash error.

[Anonymous]

Simulating your problem...I had forgotten that the switch for GPU or CPU was set to GPU as opposed to default Auto....try setting 'Edit > Restore Default Settings' in Maya....then restart computer and hope you are back! But also have previous Nvidia installed driver..Ignore the latest one!~

[Anonymous]

Thanks for the reply. The only problem is that when I run the simulation plugin over the ".cu" file, the scene is not updated. On the other hand, same plugin is working perfectly over the "c++" file. My opinion, Maya can not read the driver info from the registry. That's the reason VP 2.0 shows Driver: . in the output window. BTW, I am sorry to hear that you are limited with win7 with your new machine. Unfortunately, these type of hardware issues confine our hands. Nothing to do but still working on it.

Tnx alot again.

[Anonymous]

Ah! That's why I chose win 7 over ok 8.1 and, to me, not fully working well 10...have found 7 to work fine with professional graphics and sound

[Anonymous]

totally agree...