Unfortunately, this is just the way Direct3D 9 reports the amount of
available video memory. It makes even less sense on windows Vista because
video memory is virtualized there and is basically limited by your
swap size.
Earlier releases used DirectX 7 where the amount of vram reported
was closer to the real thing.
Thanks,
Dmitri
jav...@javadesktop.org wrote:
Windows XP, SP3
java -version 1.6.0_11-b03
nvidia 8400GS with 512mb of Vram
In earlier builds calling GraphicsDevice.getAvailableAcceleratedMemory() seemed
to return a proper vram value. I've noticed that in more recent versions it is
returning inaccurate values. On this particular machine calling it returns a
value of 610 MB (639631360 bytes).
On a newer vista 64 machine with an 512MB nvidia graphics card the call returns
a large negative value. (about -1500MB).
On a third winXP machine with a 128MB nvidia 5900 card it returns 176MB.
The values are similar if I call the method right after creating the
GraphicsDevice, after creating a buffer strategy, or after creating a seperate
volatile image.
Is this a known bug, or did something change?
[Message sent by forum member 'donmc' (donmc)]
http://forums.java.net/jive/thread.jspa?messageID=334127
===========================================================================
To unsubscribe, send email to lists...@java.sun.com and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
lists...@java.sun.com and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to lists...@java.sun.com and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
lists...@java.sun.com and include in the body of the message "help".
