Please test with JDK 6 first and let us know what you find. It would be a big help if you could do a "set J2D_TRACE_LEVEL=4" and then run the same Java2D app, first with DirectX enabled, then again with DirectX disabled, and provide us with the output in each case. That will give us a better idea of why the OGL pipeline might be disabled in the latter case. Also, the graphics board name and driver version are required as usual.
In the end, it may just be driver-specific behavior that we have no control over, but I'll reserve judgment until I see the info requested above. BTW, have you run into a lot of computers that have DirectX disabled? I'd like to know more about why you are concerned with machines that have DirectX disabled (it doesn't seem to be common in our experience). Thanks, Chris On Aug 21, 2006, at 7:06 PM, [EMAIL PROTECTED] wrote:
Well now my ogl-pipeline jnlp definitely works, but still the Java2D olg-pipeline isn't working on Windows computers when directX is disabled. To test it, disable Direct-X by running dxdiag.exe & going into the settings tab. JOGL apps work fine but the Java2D ogl-piepline does not (on Java 1.5). Why does the status of directX impact on Java2D's ogl-pipeline? Thanks, Keith. PS: I haven't tested it on Java 6 yet. [Message sent by forum member 'commanderkeith' (commanderkeith)] http://forums.java.net/jive/thread.jspa?messageID=145372 ====================================================================== ===== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
=========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
