issues running imapviewer on linux

[mojofutbol]

We're having an issue getting the imapviewer to work correctly on linux running cent os 5.4.
The application doesn't seem to accept any flags from a shell (aside from the help -flag), and in addition when opened, none of the menu's seem to work.
The menu's quickly flash when you click on them, but are inaccessible.

We're running vray version 2.4501

Anybody have any ideas/suggestions?

[tashko.zashev]

Hi,

I see you are using a nightly build. Please specify the exact V-Ray (nightly) and Maya version.
Just checked the irradiance map viewer on Cent os 6.4 and everything works fine, so most probably the issue is related to version 5.4. I will try to run a test using the same os version here and inform you about the results.

[tashko.zashev]

We can't reproduce this even with Cent os 5.4.

Please send us the output from the following commands:
*) uname -a
and
*) lsb_release -a

and the exact V-Ray build you are using.

[mojofutbol]

Hi Tashko,
Thanks for the quick reply.
Here's the info
results of uname -a:
Linux ny-wsx8022.methodstudios.com 2.6.18-194.26.1.el5 #1 SMP Tue Nov 9 12:54:20 EST 2010 x86_64 x86_64 x86_64 GNU/Linux


results of lsb_release -a:
LSB Version: :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: CentOS
Description: CentOS release 5.4 (Final)
Release: 5.4
Codename: Final

We have a few different builds of vray depending on which job.
This is we are currently using on our show:
vray2.45.01

Cheers,
Ivan

[tashko.zashev]

Thank you very much for your info.

We have on more request.
Please open a shell and navigate to imapviewer folder, then execute the following:

ldd imapviewer

Also try to download and install the latest V-Ray 2 nightly build and see if this helps. Actually I can't run a accurate test without knowing the exact nightly build release date.

[mojofutbol]

Downloaded january 6th, 2014
results of ldd imapviewer:
libpthread.so.0 => /lib64/libpthread.so.0 (0x000000352a200000)
librt.so.1 => /lib64/librt.so.1 (0x000000352c600000)
libz.so.1 => /usr/lib64/libz.so.1 (0x000000352a600000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003529e00000)
libGL.so.1 => /usr/lib64/libGL.so.1 (0x0000003537000000)
libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x0000003534800000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x000000352ae00000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x000000352b600000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x000000352e200000)
libm.so.6 => /lib64/libm.so.6 (0x0000003529a00000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x000000352d600000)
libc.so.6 => /lib64/libc.so.6 (0x0000003529600000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x000000352d200000)
/lib64/ld-linux-x86-64.so.2 (0x0000003529200000)
libnvidia-tls.so.331.49 => /usr/lib64/tls/libnvidia-tls.so.331.49 (0x0000003537c00000)
libnvidia-glcore.so.331.49 => /usr/lib64/libnvidia-glcore.so.331.49 (0x000000353e000000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x000000352aa00000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x000000352b200000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x000000352de00000)

We have this build as well -- 3.05.01 (installed on the 6th of January also) -- which has the same issue.
Here's the result of ldd imapviewer for this version(3.05.01):
libpthread.so.0 => /lib64/libpthread.so.0 (0x000000352a200000)
librt.so.1 => /lib64/librt.so.1 (0x000000352c600000)
libz.so.1 => /usr/lib64/libz.so.1 (0x000000352a600000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003529e00000)
libGL.so.1 => /usr/lib64/libGL.so.1 (0x0000003537000000)
libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x0000003534800000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x000000352ae00000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x000000352b600000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x000000352e200000)
libm.so.6 => /lib64/libm.so.6 (0x0000003529a00000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x000000352d600000)
libc.so.6 => /lib64/libc.so.6 (0x0000003529600000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x000000352d200000)
/lib64/ld-linux-x86-64.so.2 (0x0000003529200000)
libnvidia-tls.so.331.49 => /usr/lib64/tls/libnvidia-tls.so.331.49 (0x0000003537c00000)
libnvidia-glcore.so.331.49 => /usr/lib64/libnvidia-glcore.so.331.49 (0x000000353e000000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x000000352aa00000)

cheers,
Ivan
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x000000352b200000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x000000352de00000)

[Svetlozar Draganov]

We suspect that the issue is related to the Nvidia driver libraries.
Would you please send us the output from the following command:

ldd glxgears

... then please execute:

glxgears

This is a tool that will test your gpu-device/drivers. Let us know if it works or if any errors/warnings appears.

[mojofutbol]

hello Svetlozar,
here's the output of ldd glxgears:

libGL.so.1 => /usr/lib64/libGL.so.1 (0x0000003537000000)
libc.so.6 => /lib64/libc.so.6 (0x0000003529600000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x000000352ae00000)
libm.so.6 => /lib64/libm.so.6 (0x0000003529a00000)
libnvidia-tls.so.331.49 => /usr/lib64/tls/libnvidia-tls.so.331.49 (0x0000003537c00000)
libnvidia-glcore.so.331.49 => /usr/lib64/libnvidia-glcore.so.331.49 (0x000000353e000000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x000000352b600000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003529e00000)
/lib64/ld-linux-x86-64.so.2 (0x0000003529200000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x000000352aa00000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x000000352b200000)

glxgears seems to run fine.
Here's the output:
262 frames in 5.0 seconds = 52.334 FPS
256 frames in 5.0 seconds = 51.109 FPS


cheers

[Svetlozar Draganov]

Thank you very much for the feedback.

Did you download and install the Nvidia-driver from nvidia-website or did you install the RPM package through yum?
Let's try to remove the nvidia-driver and check if the same issue appears with the default driver(nouveau).

If the issue still persist please run the following command again and send us the output:

ldd glxgears