VP2 Error : Failed to initialize graphics device.

[hulud]

Hi,

I'm trying to use Maya 2018 on Linux with an NVidia GTX 1050 card.

When Maya starts it logs a message saying "VP2 Error : Failed to initialize graphics device.". Then Maya opens, I try to subdivide using opensubd a simple Sphere in the viewport and Maya crashs (Maya 2018) or the viewport breaks (Maya 2018.5).

I tried on Ubuntu 18.04 and Centos 7.6. Both act the same.

I tried the NVidia drivers 410 and 390. Both act the same.

I doubled checked glxinfo to be sure I'm using the NVidia drivers.

Any though ?

Best,

Cyril

[sean.heasley]

Hi @hulud 

For the 1050 we recommend driver version 398.82. You can find an install for version 398.82 here!

If that doesn't help, a customer with a Linux distro had the same issue in this thread.

The solution from that thread was:

I got Maya running again by running this line:

john@colfax-ESC1000-G2:/usr/autodesk/maya2016/lib$ sudo ln -s libssl.so.6 libssl.so.10

which I found in this script:

If one or more of these posts helped answer your question, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

Kudos are greatly appreciated. Everyone likes a thumbs up!

https://gist.github.com/heiths/3250500

which I got to from this thread:

http://www.arch-pub.com/Installing-Maya-on-Ubuntu_10726634-3.html

Please let me know if anything changes!

[sean.heasley]

Hi @hulud 

I'm just checking in again to see if you need more help with this. Did the suggestion I provided yesterday work for you?

If so, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

[hulud]

Hi Sean,

The driver you pointed me is a Windows driver.

I have added the ssl symbolic link, but nothing new.

Cyril

[sean.heasley]

Hi @hulud 

Ah my bad I forgot you were on Linux distros.

It doesn't look like Nvidia has our supported driver available for Linux distros but this does indeed seem to be a GPU error.

for now you can try adding these lines to your Maya.env file:

MAYA_OPENCL_IGNORE_DRIVER_VERSION=1

MAYA_DISABLE_OPENCL=1

[sean.heasley]

Hi @hulud 

I'm just checking in again to see if you need more help with this. Did the suggestion I provided on Friday work for you?

If so, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

[nuno.pereira2VX6D]

Hi Sean,

This is not resolved. On CENTOS7 both Maya2018 and 2019 produce this. We have NVIDIA's RTX5000's with the latest available drivers for Linux.

Using the env vars to disable openCL does not work either neither symlinking libssl.

Is this a specific graphics card/drivers issue or are there any other libraries we may be missing?

Have you had any other reports on this?

Many thanks

Nuno

[warnold2]

on Linux one needs to ensure there isn't any conflicting GPU drivers.  depending on the system  CentOS/RHEL/Ubuntu each have their own system "default" 

running glxinfo  should provide the high level info to know which driver is being used
can you post the output. 
as well was there any output from Maya on what it believed the GPU initialization found. 

if running from the terminal should be something like:

maya
Initialized VP2.0 renderer {
Version : 2016.11.44.12. Feature Level 5.
Adapter : Quadro P2000/PCIe/SSE2
Vendor ID: 4318. Device ID :
Driver : 4.6.0 NVIDIA 415.18.
API : OpenGL V.4.6.
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 : 5120 MB.
CPU Memory Limit: 60634.7 MB.
MultiDraw consolidation: enabled
}
OpenCL evaluator is attempting to initialize OpenCL.
Detected 1 OpenCL Platforms:
0: NVIDIA Corporation. NVIDIA CUDA. OpenCL 1.2 CUDA 10.0.132.
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_copy_opts cl_khr_gl_event cl_nv_create_buffer
OpenCL evaluator choosing OpenCL platform NVIDIA Corporation.
Synchronizing between Graphics and OpenCL using sync mode 1
Synchronizing between OpenCL and Graphics using sync mode 1

for Ubuntu in many cases the system symlink for  /usr/lib/libGL.so.1 may not be setup to point to Nvidia driver 
in some cases the installation on CentOS/RHEL can also get mixed results with nouveau 

Nvidia has their bug reporting tool which can list most of the info defining the installation/running of the driver
/usr/bin/nvidia-bug-report.sh
the output could be helpful

 

[nuno.pereira2VX6D · Accepted solution]

Hi all,

Our tech team solved this.
Needed to repoint the tiff library in the right direction. I know this
description is not exactly helpful to anyone at this point but I'm not
aware of all the deatils.

I will ask our team the exact solution and post it here for future
reference.

[Anonymous]

Hi,

It seems like we are experiencing the same issue over here. Did your tech team ever get back to you with more details regarding repointing the tiff library in the right direction?

[nuno.pereira2VX6D · Accepted solution]

He guys so there's another thread with the same issue
https://forums.autodesk.com/t5/installation-licensing/vp2-error-failed-to-initialize-graphics-device...

which had a pointer to a gituhb install script that was linked here:
https://gist.github.com/heiths/3250500

We have our own custom deployment procedures so we nicked the bits that
seem to affect system libraries.


- sudo ln -s /usr/lib/x86_64-linux-gnu/libtiff.so.5.1.0
/usr/lib/libtiff.so.3
- sudo ln -s /usr/autodesk/maya2014-x64/support/openssl/libssl.so.6
/usr/autodesk/maya2014-x64/lib/libssl.so.10
- delete the lib.so.3 and ln -s from lib.so.5


That did it for us. Symlinking libssl by itself didn't work but then we did
the other 2 and it evertyhing worked. It may no be neeedd or may be a
combination of the 3.

MAYA_OPENCL_IGNORE_DRIVER_VERSION=1 and MAYA_DISABLE_OPENCL=1 had no effect
on the problem.

This seems to be very much a recurring issue on CENTOS7 so maybe autodesk
should have a closer look on shipped libraries and install symlinks.

Thanks