John Wright wrote: >I was experimenting with this yesterday and only saw about a 25% >performance increase by using the image loading code from j3d.org vs >using Sun's "TextureLoader". So I wouldn't expect to see any large >changes. You could put in a lot of work, end up with something less >flexible and only gain a minor performance increase. > > > > It wasn't until we paired j3d.org's texture loading with the imageloader library Justin wrote did we see a really nice speed increase. This library does all of the image decoding in native libraries... obviously a portability problem, but the code ports pretty well. The j3d code allows use to use either Java's image handlers our our own depending(using the URI library by Justin) on what's loaded, similar to how Sun's TextureLoader can use JAI if its installed.
I'm not really advocating people switch over. With some work it could get there, but right now we don't have the client interest to put the time into really making that route industrial strength. Always of course looking for help or funding :) -- Alan Hudson President: Yumetech, Inc. http://www.yumetech.com/ Web3D Open Source Chair http://www.web3d.org/TaskGroups/source/ =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
