Problems with VirtualGL and StarCCM+

[Jason Edgecombe]

Hi,

I'm having trouble with Seimens (formerly CD-ADAPCO) StarCCM+ working with VirtualGL.

When running "vglrun +tr Starccmplus13-nomesa" I get the following:

[VGL 0x25c0c780] XOpenDisplay (name=NULL dpy=0x015aaa10(:101) ) 1.359940 ms

... 

Warning: glxinfo unable to obtain openGL support.  Rendering with mesa.

There is only one VGL diagnostic message that is displayed.

Setting VGL_LOGO=1 does not show the VGL logo.

I've tried setting the following over different runs with no luck:

• export VGL_DEFAULTFBCONFIG=GLX_STENCIL_SIZE,8
  
• export VGL_DEFAULTFBCONFIG=GLX_ALPHA_SIZE,8
  
• export VGL_DEFAULTFBCONFIG=GLX_ALPHA_SIZE,8,GLX_STENCIL_SIZE,8
  

I've tried with two different VirtualGL versions:

• VirtualGL-2.6.1-20190101
  
• VirtualGL-2.6.2-20190321
  

I'm running on RHEL 7.6 x86_64.

Does anyone have any suggestions for making StarCCM+ work with VirtualGL?

Thanks,

Jason

---------------------------------------------------------------------------
Jason Edgecombe | Linux Administrator
UNC Charlotte | The William States Lee College of Engineering
9201 University City Blvd. | Charlotte, NC 28223-0001
Phone: 704-687-1943
jwed...@uncc.edu | http://engr.uncc.edu |  Facebook
---------------------------------------------------------------------------
If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply e-mail or by telephone at
704-687-1943.  Thank you.

[DRC]

Please send the trace log.

On 3/21/19 3:07 PM, Jason Edgecombe wrote:
> Hi,
>
> I'm having trouble with Seimens (formerly CD-ADAPCO) StarCCM+ working
> with VirtualGL.
> When running "vglrun +tr Starccmplus13-nomesa" I get the following:
>
> [VGL 0x25c0c780] XOpenDisplay (name=NULL dpy=0x015aaa10(:101) )
> 1.359940 ms
>
> ... 
>
> Warning: glxinfo unable to obtain openGL support.  Rendering with mesa.
>
>
> There is only one VGL diagnostic message that is displayed.
>
> Setting VGL_LOGO=1 does not show the VGL logo.
>
> I've tried setting the following over different runs with no luck:
>

> * export VGL_DEFAULTFBCONFIG=GLX_STENCIL_SIZE,8
> * export VGL_DEFAULTFBCONFIG=GLX_ALPHA_SIZE,8
> * export VGL_DEFAULTFBCONFIG=GLX_ALPHA_SIZE,8,GLX_STENCIL_SIZE,8

>
>
> I've tried with two different VirtualGL versions:
>

> * VirtualGL-2.6.1-20190101
> * VirtualGL-2.6.2-20190321

>
> I'm running on RHEL 7.6 x86_64.
>
> Does anyone have any suggestions for making StarCCM+ work with VirtualGL?
>
> Thanks,
> Jason
>
> ---------------------------------------------------------------------------
> Jason Edgecombe | Linux Administrator
> UNC Charlotte | The William States Lee College of Engineering
> 9201 University City Blvd. | Charlotte, NC 28223-0001

> Phone: 704-687-1943 <tel:704-687-1943>
> jwed...@uncc.edu <mailto:jwed...@uncc.edu> | http://engr.uncc.edu |

>  Facebook
> ---------------------------------------------------------------------------
> If you are not the intended recipient of this transmission or a person
> responsible for delivering it to the intended recipient, any disclosure,
> copying, distribution, or other use of any of the information in this
> transmission is strictly prohibited. If you have received this
> transmission in error, please notify me immediately by reply e-mail or
> by telephone at

> 704-687-1943 <tel:704-687-1943>.  Thank you.
>
> --
> You received this message because you are subscribed to the Google
> Groups "VirtualGL User Discussion/Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to virtualgl-use...@googlegroups.com
> <mailto:virtualgl-use...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGDxYfG-ymHA0Lbn5MeL0POd55UZSVXBnqW57K8YgVg%3Dgg%40mail.gmail.com
> <https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGDxYfG-ymHA0Lbn5MeL0POd55UZSVXBnqW57K8YgVg%3Dgg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

[Jason Edgecombe]

Hello,

Here is the log of what I did:

% export VGL_LOG=$(pwd)/trace.txt
% vglrun  +tr Starccmplus13-nomesa 
[VGL 0x31ca9780] XOpenDisplay (name=NULL 
Starting starccm+ 1304 (64bit)...
Current working directory: /nfs/users/jwedgeco/linux/tmp/virtualgl

Warning: glxinfo unable to obtain openGL support.  Rendering with mesa.

% cat trace.txt 
dpy=0x02603c50(:101) ) 2.616167 ms
% 

I simply closed StarCCM+ once the windows opened.

I also ran "vglrun  +tr strace -f -o strace.log Starccmplus13-nomesa" and attached the strace output.

I'm using StarNet FastX as my X proxy and VGL_DISPLAY=:1

Thanks,

Jason 

---------------------------------------------------------------------------
Jason Edgecombe | Linux Administrator
UNC Charlotte | The William States Lee College of Engineering
9201 University City Blvd. | Charlotte, NC 28223-0001
Phone: 704-687-1943

jwed...@uncc.edu | http://engr.uncc.edu |  Facebook
---------------------------------------------------------------------------
If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply e-mail or by telephone at

704-687-1943.  Thank you.

To unsubscribe from this group and stop receiving emails from it, send an email to virtualgl-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/33e0cbd7-58cb-302d-e0a6-f9301491c039%40virtualgl.org.

[DRC]

From the strace output, STAR-CCM+ appears to be running /usr/bin/glxinfo
and grepping for "OpenGL version string" to determine whether the X
server supports a minimum version of OpenGL. The only thing I can
figure is that, for reasons unexplained, VirtualGL isn't being loaded
into the glxinfo process. If VirtualGL is loaded, then the OpenGL
version string will be passed through from the 3D X server.

I don't personally have access to any commercial applications like
STAR-CCM+, so supporting them is generally not something I can do for
free. I have to either obtain a demo version from the ISV (which,
historically, has been difficult with this particular application) or
arrange to log in remotely to a machine (i.e. yours) that has the
application installed and spend a few hours diagnosing it. Either way,
it's a pain. However, I have a very good track record of solving such
problems once I have access to the application.

DRC

On 3/22/19 9:14 AM, Jason Edgecombe wrote:
> Hello,
>
> Here is the log of what I did:
>
> % export VGL_LOG=$(pwd)/trace.txt
> % vglrun  +tr Starccmplus13-nomesa 
> [VGL 0x31ca9780] XOpenDisplay (name=NULL 
> Starting starccm+ 1304 (64bit)...
> Current working directory: /nfs/users/jwedgeco/linux/tmp/virtualgl
> Warning: glxinfo unable to obtain openGL support.  Rendering with mesa.
> % cat trace.txt 
> dpy=0x02603c50(:101) ) 2.616167 ms
> % 
>
>
> I simply closed StarCCM+ once the windows opened.
>
> I also ran "vglrun  +tr strace -f -o strace.log Starccmplus13-nomesa"
> and attached the strace output.
>
> I'm using StarNet FastX as my X proxy and VGL_DISPLAY=:1
>
> Thanks,
> Jason 
> ---------------------------------------------------------------------------
> Jason Edgecombe | Linux Administrator
> UNC Charlotte | The William States Lee College of Engineering
> 9201 University City Blvd. | Charlotte, NC 28223-0001

[Patrik Pira]

Hi Jason.

StarCCM+ does run (fairly well) with VirtuaGL. You will have to edit the start-scripts a bit though. The script "starenv" does unset LD_PRELOAD, find that portion and comment it out. You might want to edit the main start script "starccm+" and increase java heap size also if your model is a bit on the larger side.

Certain combos of OS and VIDIA drivers might require the option ConstantFrameRateHint "1" in xorg.conf. Current CentOS 7.6 and latest nvidia drivers does not require this with Starccm+ version 14+.