OGL pipeline improvements

[Linuxhippy]

Hmm, just came arround another strange issue with Opengl enabled.

I have some UGLY code that does water-animation, basically it does nothing more than first create some wave-images of the original picture and after this it blits them over and over.

When running on X11 I don't have any problems, and also with OpenGL and many wave-images (more than 6) everything works.
This happens, because the code allocates one big image and just moves it to negative x-coordinates to just draw the area which should be shown.
If using more than 6 images, the image reaches over 4096 pixel -> no accerlation...

If you want I could send you the code as PM, should I?

lg Clemens

[Spasi]

If using more than 6 images, the image reaches over 4096 pixel -> no accerlation...

You're surpassing the maximum texture size supported by modern graphics cards (4096 on NV, 2048 on ATI).

[Linuxhippy]

well I know - if I use big textures I do not get accerlation -> the it works. Re-read my post!

However I was able to track down the problem, it was also caused by the no-VolatileImage-Size-Bigger-Than-Window bug, but it was not my code so I did not know it was caused by this problem...

lg Clemens

Games published by our own members! Check 'em out!

[selendic]

OK guys, just to notify you, it seems that OGL acceleration doesn't want to start on Linux with newest NVidia drivers (1.0-7664).

[Linuxhippy]

same here, so not even pass the initializing stuff

[campbell]

OK guys, just to notify you, it seems that OGL acceleration doesn't want to start on Linux with newest NVidia drivers (1.0-7664).

Thanks for the post.  I was planning to install the new drivers today.  I tried their beta drivers a few weeks ago and everything was okay, so I'm not sure what happened yet.  Really, this sort of thing should not be happening, since Nvidia should be running our "basic acceptance test" before shipping new drivers.  Grr... I'll contact them to find out what happened.

BTW, I've been on jury duty for the past couple weeks, and it will go another couple weeks, so bear with me.  I'm still finding some time to make some nice improvements to the OGL pipeline though.

Thanks,
Chris

[swpalmer]

BTW, I've been on jury duty for the past couple weeks, and it will go another couple weeks, so bear with me.

Was the perp wearing WIDE pants that were halfway down his ass?  If so then he's definitely guilty, specially if he wasn't wearing a shirt at the time of the crime and has lots of tattoos.  ;-)

[campbell]

OK guys, just to notify you, it seems that OGL acceleration doesn't want to start on Linux with newest NVidia drivers (1.0-7664).

FYI: The relevant bug report should be visible on bugs.sun.com tomorrow under bugid 6281130.  I've already been in touch with the Nvidia engineers.  The bug report has more information about the underlying issues.  I'm meeting with them this week to ensure regressions like this don't occur in the future.

Thanks,
Chris

[campbell]

OK guys, just to notify you, it seems that OGL acceleration doesn't want to start on Linux with newest NVidia drivers (1.0-7664).

FYI: The relevant bug report should be visible on bugs.sun.com tomorrow under bugid 6281130.  I've already been in touch with the Nvidia engineers.  The bug report has more information about the underlying issues.  I'm meeting with them this week to ensure regressions like this don't occur in the future.

Thanks,
Chris

Update: Nvidia has released a minor driver update (7667) for both Linux and Solaris that resolves the initialization issue described earlier.  A more complete fix will come in Mustang sometime next month, but with 7667, both JDK 5.0 and JDK 6.0 apps should work once again with OGL enabled.  There are still a couple remaining issues in 7664 and 7667 that affect the OGL pipeline, but they are minor and should be fixed in their next driver release.

Chris