I can confirm that the new prerelease build works for us too.
2014-03-27 19:23, DRC skrev:
A new pre-release build with the infinite drawing loop fix is now available:
http://www.virtualgl.org/DeveloperInfo/PreReleases
So at least it should now work as well as 2.3 worked. I will keep you
Sorry for the delay on this. Both issues have been reproduced, and I'm
investigating.
On 3/3/14 1:25 AM, Patrik Pira wrote:
Yes, flickering does occur with VGL 2.3. It does go away when I switch
to software opengl.
2014-02-28 18:39, DRC skrev:
OK, fair enough. I'm working with Altair in
You mean the native Windows viewer? Which version? And also, which
version of the TurboVNC server are you using?
On 2/28/14 1:12 AM, Patrik Pira wrote:
I wasn't aware of that there is a java viewer also. I use the native one
when the problem appears.
I start it with:
$ vglrun hm
In
OK, fair enough. I'm working with Altair in parallel to try and
diagnose this, and they've confirmed that the infinite loop issue occurs
with VGL 2.3.3, but I'm trying to nail down whether the flickering issue
is also VirtualGL's fault. Can you confirm whether the flickering
occurs with VGL
Altair is looking into it. Are the visual anomalies specific to a
particular viewer? Do you, for instance, see them with both the Java
and the native viewer on a particular platform?
On 2/27/14 1:17 AM, Patrik Pira wrote:
I also tried hypermesh 11.0 and it also deadlocks with VirtualGL
I wasn't aware of that there is a java viewer also. I use the native one
when the problem appears.
I start it with:
$ vglrun hm
In the end, the file hmopengl is executed which is native 64-bit code.
To reproduce deadlock, create a 1-dimensional, standard section, HYPER
BEAM, thinwalled box.
Hello
I'm having problems running Altair hypermesh with the latest version of
VirtualGL (2.3.3). Application sort of deadlocks when creating a
hyperbeam section and rapidly just redraws the opengl drawing area
without responding to input. Only way out is to kill the process.
After some
What version of HyperMesh? Altair actively sells VirtualGL and TurboVNC
as part of their grid service offering, so I know that it has been
tested. The only possibility is that a new version came out that broke
something, or perhaps there is something different about your environment.
What
Hypermesh 12.0, which seems to be the latest version released according
to their website.
We use NVIDIA cards, I believe these servers have a Quadro 4000 or
similar card. Driver version 310 or 320 something on RHEL6 x86_64. I am
not at work right now so I can't check the exact version.
As it
I also tried hypermesh 11.0 and it also deadlocks with VirtualGL 2.3.3.
Works fine when downgrading to VirtualGL 2.3.
2014-02-26 20:24, Patrik Pira skrev:
Hypermesh 12.0, which seems to be the latest version released according
to their website.
We use NVIDIA cards, I believe these servers
10 matches
Mail list logo