From: Rob H. <rha...@ze...> - 2002-06-20 13:03:48
|
Sven Goethel <sgo...@ja...> said: > puhh - sounds very funny > 'cause you say, it (your configuration + opengl) works nice for > native applications, well, gl4java must be one ingredient .. C/C++ OpenGL apps work at both 16 and 24 bit depths (by "work" I mean they don't hang X, and I get OpenGL output). Only GL4Java apps hang the machine at 16, and so far they do it consistently. On the other hand GL4Java apps consistently work at 24 bit. One minor exception to C OpenGL apps "working" is that display list share groups seem to be broken with RedHat 7.3 and the accompanying NVIDIA driver set. Hard to say what's going with that since the NVIDIA GLX "source RPM" doesn't have much source in it :-/. This is unfortunate since when using GL4Java you can cut down on your JNI overhead by using display lists, and now sharing is broken in the base GL implementation. It seems wasteful to have to initialize display lists in every context we create to get around this issue. Sigh... I'm not sure what to think about the GL4Java issue yet, and haven't had time to descend into the source to see what's going on. All I know for sure is that the behavior has been repeatable across a number of machines at our location running various versions of RedHat with appropriate NVIDIA kernel/GLX drivers on each. The only thing common to all of them is they're all dual-processor machines running a SMP kernel. I'm going to continue doing some experimentation with this between other things, and will post if I figure out what's going on. Thanks for the feedback, Rob Hatcherson ZedaSoft, Inc. |