Please vote the “Java2D quality issues” image interpolation bug.
I don’t really know how much Sun takes our bug-votes in consideration, but I think it’s quite important for the whole community to let them know that bug reporting is so important for Java.
http://developer.java.sun.com/developer/bugParade/bugs/4950176.html
Cheers,
Mik - (Javazoid)
+1
+1 
dont forget AffineTransformations are software rendered, i DO NOT Use em because if i would my framerate drops to 5 FPS.
Wait until java 1.5 has complete D3D or OGL support
indeed,
When they start using HW acceleration my guess is all the bugs in Javas software renderer will simply go away (or rather, be hidden until another day ???)
Someone told me that Java2D will not use OpenGL on win32 Java2 1.5.
Are you sure that we will have HW acceleration on this platform ?
[quote]Someone told me that Java2D will not use OpenGL on win32 Java2 1.5.
Are you sure that we will have HW acceleration on this platform ?
[/quote]
All i said was ‘When they start using HW…’, I didn’t say when when was
(and from what trembovetski has said, it seems doubtful when will be 1.5)
I forgot to mention my +1…
OpenGL HW acceleration is in 1.5 for Linux and Solaris, Win32 will use DirectX for it’s HW acceleration still - basically because it is generally better supported on Windows… at least that’s the line of reasoning that I recall hearing.
Win32 may get OpenGL acceleration after 1.5. In any case it doesn’t so much matter which tech they use, so long as the transformations are accelerated some way… of course if some Java bugs go away because of this, some driver bugs may be exposed 
[quote]I forgot to mention my +1…
OpenGL HW acceleration is in 1.5 for Linux and Solaris, Win32 will use DirectX for it’s HW acceleration still
[/quote]
I keep asking myself why they’re using DirectX on Win, when OpenGl is a widely diffused standard on any platform. Using OpenGL they could use the same glue code for any os.
I have another consideration about the drawing loops in drawImage et similia: using DirectX Sun will probably be forced to use software loops still in 1.5. I can only think this is a good direction only if they fix the loops.
Someone from the Java 2D team mentioned before that the reason they stick to DirectX on windows is the support for older graphics cards. Alot of crappy graphics cards support hardware 2D but not 3D, so the OpenGL driver ends up being pure software. However, the DirectX driver normally get proper hardware support.
The same chap did mention being able to enabled the OpenGL pipeline on windows tho.
Kev
+1
11 votes so far… oh…
votes++; ;D
You guys have a long way to go. Check out this rfe:
http://developer.java.sun.com/developer/bugParade/bugs/4932968.html
2000 (!) votes in two weeks =)
Please don’t do something like this, or the responsible engineer will have a heart attack =)
Vietnamese support is only for Vietnamese.
Java2D is for everyone
All: please follow the discussion on Javalobby:
full OGL support in java2d would be nice, your image quality bug will also be fixed and a lot of other things 2.
If you haven’t been over to check out the discussion in the javalobby link above, Chet wrote a very nice explanation of the reasonings for and uses of the various APIs on the different platforms. At least it’s the most comprehensive explanation I’ve seen in any one spot.
Anyway, I’m with swpalmer, all I want for Christmas is hardware accelerated transforms whatever the underlying API might be.
Yes, Chet as been very clear and helpful.
I think that Sun is going in the right direction but they should also take care of the bugs, while going on with the innovation.
…and please tell Santa that I want the same ;D
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4950176
Bug fixed in Mustang ! Looks like there are some nice speed/memory footprint improvements too.
All my best to the Java2D team!