The Source for Java Technology Collaboration

Home » java.net Forums » Java Desktop Technologies » Java 2D

Thread: upper memory limit to vmem cached images with direct3d pipeline?

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 1 - Last Post: Aug 11, 2008 8:39 AM by: Dmitri Trembove... Threads: [ Previous | Next ]
john_t

Posts: 1
upper memory limit to vmem cached images with direct3d pipeline?
Posted: Aug 10, 2008 11:03 PM
  Click to reply to this thread Reply

hi

i'm working on a touchscreen interactive for an australian museum. the project uses a number of historical and modern panoramic images running across two 30" displays (5120x1600 total pixels). i'm using the scene graph project to load in multiple huge images (max 26,300x1600 pixels (i've spilt these into 1024x1600 tiles)) and to allow the user to scroll and zoom around them. its all working very well. it's very impressive watching images of this size smoothly scroll and zoom with subpixel positioning and virtually no CPU usage. obviously the accelerated pipelines are working very well!

i was running this on a nvidia 8800GT 512MB, however as the number of images has increased it gets to a point where some of the images are no longer accelerated (which is painfully obvious). so i recently upgraded to a GTX280 1GB. when the program is running with the direct3d pipeline there still seems to be the same limit (in terms of number of images) as the 512MB card. whereas running with the opengl pipeline allows approximately twice as many images. so it would seem that there is some sort of hard coded limit with the direct3d pipeline. is this a limitation with direct3d itself or with the pipeline?

i realise this is a somewhat extreme case, but if the vram is sitting there its a shame not to use it ;-) obviously i can use the opengl pipeline but i have generally found the direct3d pipeline to be more consistent/stable (opengl driver issues i guess)

i've been building graphical interactives like this using java for 5 or 6 years. the performance improvements in java2d since java6 was released have been very significant. thanks to all involved, its really allowed a new class of graphical applications to be built.

john

Dmitri Trembove...
Re: [JAVA2D] upper memory limit to vmem cached images with direct3d pipeline?
Posted: Aug 11, 2008 8:39 AM   in response to: john_t
  Click to reply to this thread Reply

Hi John,

glad to hear that the d3d pipeline works for you. Which release are you
using?

There's no Java2D-induced limit on the amount of VRAM that the application
can allocate, it's handled by the Direct3D runtime.

Run your application with J2D_TRACE_LEVEL=4 environment variable
set and see if it prints "out of video memory" errors on the
console.

Thanks,
Dmitri


java2d@JAVADESKTOP.ORG wrote:
> hi
>
> i'm working on a touchscreen interactive for an australian museum. the project uses a number of historical and modern panoramic images running across two 30" displays (5120x1600 total pixels). i'm using the scene graph project to load in multiple huge images (max 26,300x1600 pixels (i've spilt these into 1024x1600 tiles)) and to allow the user to scroll and zoom around them. its all working very well. it's very impressive watching images of this size smoothly scroll and zoom with subpixel positioning and virtually no CPU usage. obviously the accelerated pipelines are working very well!
>
> i was running this on a nvidia 8800GT 512MB, however as the number of images has increased it gets to a point where some of the images are no longer accelerated (which is painfully obvious). so i recently upgraded to a GTX280 1GB. when the program is running with the direct3d pipeline there still seems to be the same limit (in terms of number of images) as the 512MB card. whereas running with the opengl pipeline allows approximately twice as many images. so it would seem that there is some sort of hard coded limit with the direct3d pipeline. is this a limitation with direct3d itself or with the pipeline?
>
> i realise this is a somewhat extreme case, but if the vram is sitting there its a shame not to use it ;-) obviously i can use the opengl pipeline but i have generally found the direct3d pipeline to be more consistent/stable (opengl driver issues i guess)
>
> i've been building graphical interactives like this using java for 5 or 6 years. the performance improvements in java2d since java6 was released have been very significant. thanks to all involved, its really allowed a new class of graphical applications to be built.
>
> john
> [Message sent by forum member 'john_t' (john_t)]
>
> http://forums.java.net/jive/thread.jspa?messageID=292523
>
> ===========================================================================
> To unsubscribe, send email to listserv@java.sun.com and include in the body
> of the message "signoff JAVA2D-INTEREST". For general help, send email to
> listserv@java.sun.com and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
listserv@java.sun.com and include in the body of the message "help".





 XML java.net RSS