Personal tools
You are here: Home Forum Install & build Problems with the OCC viewer

Problems with the OCC viewer

Up to Install & build

Problems with the OCC viewer

Posted by Holger Steffen at September 06. 2017

Hello and greetings to all here.

Hope, somebody knows a solution for the problem described below:

I have installed salome 8.2.0 (from this website) and salome-meca LGPL 2017. on my  CentOS 7.3 system.

Salome from this website runs fine.

At salome-meca, the occ-viewer is not working.

It keeps black, also if I select to show a gradient.

Geometry is not shown, only vertices can be seen.

I contacted the forum at salome-meca,

but I was recommended to put the question here, because it is a salome problem.

I think, they are right.

salome is started by:  /opt/SALOME-8.2.0-CO7.2/salome

salome-meca is started by:  /home/holger/salome_meca/appli_V2017/salome %f

 

I have some problems with the graphics driver (nvidia 384.59),

if I try to update kmod-nivdia via yum, I get an dependency resolution error.

But all other 3d (and of cause 2d) applications are running fine:  salome, ansys, varicad, bricscad, vmware (with creo), freecad, blender, meshlab, google earth, gmsh,...

only salome--meca makes trouble .....

 

When I start from shell, I get following messages: 

 

 /home/holger/salome_meca/appli_V2017/salome %f

runSalome running on localhost.localdomain

Searching for a free port for naming service: 2817 - OK

Searching Naming Service + found in 0.1 seconds 

Searching /Kernel/Session in Naming Service +++libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: swrast

Warning: this type (Study,objref) already exists, it will be ignored.

+****************************************************************

*    Warning: HYBRIDPLUGIN GUI resources are not found.

*    HYBRIDPLUGIN GUI will not be available.

****************************************************************

****************************************************************

*    Warning: BLSURFPLUGIN GUI resources are not found.

*    BLSURFPLUGIN GUI will not be available.

****************************************************************

****************************************************************

*    Warning: HexoticPLUGIN GUI resources are not found.

*    HexoticPLUGIN GUI will not be available.

****************************************************************

****************************************************************

*    Warning: NETGENPLUGIN GUI resources are not found.

*    NETGENPLUGIN GUI will not be available.

****************************************************************

****************************************************************

*    Warning: GHS3DPLUGIN GUI resources are not found.

*    GHS3DPLUGIN GUI will not be available.

****************************************************************

 found in 2.0 seconds 

Start SALOME, elapsed time :   2.2 seconds

 

 

 

 

 

 

 

 

Re: Problems with the OCC viewer

Posted by Christophe Bourcier at September 07. 2017

Hi,

Edit the file appli_V2017/env.d/envProducts.cfg, go to the last line and remove ":/lib64".

That worked for me.

Christophe

Re: Problems with the OCC viewer

Posted by Holger Steffen at September 07. 2017

OK, thank you for the hint!

I have three versions of salome: on my CerntOS 7.3 machine

salome_meca 2016, salome_meca_2017, and salome

and I had the failure of graphics at salome_meca2016 and salome_meca2017

Now I did the editing as you told for both versions salome_meca.

And now, the graphics is working fine for salome_meca2016

but salome_meca2017 still has no occ graphics ...

?????

Have you one hint more for me?

Greetings from Hollingstedt,

H.Steffen

 

Re: Problems with the OCC viewer

Posted by Christophe Bourcier at September 07. 2017

Can you copy/paste the log to see if there are other errors than previously?

Christophe

Re: Problems with the OCC viewer

Posted by Holger Steffen at September 08. 2017

OK,

here it is:

(it are the messages, which are output after starting from the shell. Is there another log file?)

 

 

/home/holger/salome_meca/appli_V2017/salome %f

runSalome running on localhost.localdomain

Searching for a free port for naming service: 2816 - OK

Searching Naming Service + found in 0.1 seconds 

Searching /Kernel/Session in Naming Service ++++++++++++++++++++libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: swrast

+Warning: this type (Study,objref) already exists, it will be ignored.

 found in 10.5 seconds 

Start SALOME, elapsed time :  12.2 seconds

****************************************************************

*    Warning: HYBRIDPLUGIN GUI resources are not found.

*    HYBRIDPLUGIN GUI will not be available.

****************************************************************

****************************************************************

*    Warning: BLSURFPLUGIN GUI resources are not found.

*    BLSURFPLUGIN GUI will not be available.

****************************************************************

****************************************************************

*    Warning: HexoticPLUGIN GUI resources are not found.

*    HexoticPLUGIN GUI will not be available.

****************************************************************

****************************************************************

*    Warning: NETGENPLUGIN GUI resources are not found.

*    NETGENPLUGIN GUI will not be available.

****************************************************************

****************************************************************

*    Warning: GHS3DPLUGIN GUI resources are not found.

*    GHS3DPLUGIN GUI will not be available.

****************************************************************

libGL error: No matching fbConfigs or visuals found

libGL error: failed to load driver: swrast

TKOpenGl | Type: Portability | ID: 0 | Severity: High | Message:

  OpenGL driver is too old! Context info:

    Vendor:   NVIDIA Corporation

    Renderer: GeForce GTX 750 Ti/PCIe/SSE2

    Version:  1.4 (2.1.2 NVIDIA 384.59)

  Fallback using deprecated fixed-function pipeline.

  Visualization might work incorrectly.

  Consider upgrading the graphics driver.

 
Thank you for the effort!
 
Greetings,
Holger

Re: Problems with the OCC viewer

Posted by Christophe Bourcier at September 08. 2017

Strange, now you have an explicit error on the version of your NVIDIA driver. Can you check that it is correctly installed with:

glxinfo |grep version

 

There is also a reference to /lib64 in env.d/envProducts.sh, line 37. You can try to remove ":/lib64" on this line and launch salome again.

Christophe

Re: Problems with the OCC viewer

Posted by Holger Steffen at September 08. 2017

OK.

$ glxinfo |grep version

server glx version string: 1.4

client glx version string: 1.4

GLX version: 1.4

OpenGL core profile version string: 4.4.0 NVIDIA 384.59

OpenGL core profile shading language version string: 4.40 NVIDIA via Cg compiler

OpenGL version string: 4.5.0 NVIDIA 384.59

OpenGL shading language version string: 4.50 NVIDIA

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 384.59

OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

    GL_EXT_shader_group_vote, GL_EXT_shader_implicit_conversions,

 

 

Other suggestion:

I removed /lib64 from envProducts.sh,

but no success...

 

Greetings,

Holger

 

Re: Problems with the OCC viewer

Posted by Christophe Bourcier at September 08. 2017

Can you copy/paste the output of the following lines in the same terminal:

./salome context

glxinfo

echo $LD_LIBRARY_PATH

 

Christophe

Re: Problems with the OCC viewer

Posted by Holger Steffen at September 08. 2017

Hope, I have done all right,

Find file attached

Attachments

Re: Problems with the OCC viewer

Posted by Christophe Bourcier at September 08. 2017

There is still :/lib64 at the end of LD_LIBRARY_PATH. It must not be there.

Please check if it remains in some files of env.d:

cd appli_V2017/env.d

grep lib64

And check if you don't have lib64 in a new terminal: echo $LD_LIBRARY_PATH |grep lib64

Re: Problems with the OCC viewer

Posted by Holger Steffen at September 08. 2017
I have it!
Thank you very much!
It was my fault..
I copied the old version of  envProducts.cfg to envProducts_alt.cfg .....
Now, all is running fine.
Let's go on learning..
Greetings from Germany.
 
 
 

Re: Problems with the OCC viewer

Posted by Christophe Bourcier at September 11. 2017

Glad to hear it!

Greetings from Paris-Saclay.

Christophe

Powered by Ploneboard
Document Actions