When falling back on pbuffer from the FBO mode these tests ate 1G+ memory and couldn't start with my gf6200. Can I switch off fallback to pbuffer? Previously (before 1.0rc1) it run (naturally without the effect) because there was no pbuffer fallback. Also, is this normal or is this a bug?
Note: I've added ResourceLocatorTool to help it loading the textures correctly with 1.0rc1.
Hmm, well first off… running TestQuadWater locally from eclipse I don't see any texture issue.
Second, running using FBO, task manager claims I am using 69M of memory and I'm running at ~950FPS
If I force a fallback to pbuffer, I am now using 72M of memory and I'm running at ~1025FPS
Not sure where to go from there for you…
2007.09.19. 16:05:59 com.jme.app.BaseGame start
INFO: Application started.
2007.09.19. 16:06:00 com.jme.system.PropertiesIO <init>
INFO: PropertiesIO created
2007.09.19. 16:06:00 com.jme.system.PropertiesIO load
INFO: Read properties
2007.09.19. 16:06:11 com.jme.input.joystick.DummyJoystickInput <init>
INFO: Joystick support is disabled
2007.09.19. 16:06:11 com.jme.system.lwjgl.LWJGLDisplaySystem <init>
INFO: LWJGL Display System created.
2007.09.19. 16:06:11 com.jme.system.lwjgl.LWJGLDisplaySystem getValidDisplayMode
INFO: Selected DisplayMode: 320 x 200 x 32 @60Hz
2007.09.19. 16:06:11 com.jme.system.PropertiesIO save
INFO: Saved properties
2007.09.19. 16:06:11 com.jme.app.BaseSimpleGame initSystem
INFO: jME version 1.0 alpha
2007.09.19. 16:06:13 com.jme.renderer.lwjgl.LWJGLRenderer <init>
INFO: LWJGLRenderer created. W: 320H: 200
2007.09.19. 16:06:14 com.jme.app.BaseSimpleGame initSystem
INFO: Running on: nv4_disp
Driver version: 6.14.10.7400
NVIDIA Corporation - GeForce Go 6200/PCI/SSE2 - 1.5.3
2007.09.19. 16:06:14 com.jme.renderer.AbstractCamera <init>
INFO: Camera created.
2007.09.19. 16:06:14 com.jme.util.lwjgl.LWJGLTimer <init>
INFO: Timer resolution: 1000 ticks per second
2007.09.19. 16:06:14 com.jme.scene.Node <init>
INFO: Node created.
2007.09.19. 16:06:14 com.jme.scene.Node <init>
INFO: Node created.
2007.09.19. 16:06:14 com.jme.scene.Node attachChild
INFO: Child (FPS label) attached to this node (FPS node)
2007.09.19. 16:06:15 com.jme.scene.Node attachChild
INFO: Child (Text) attached to this node (FPS node)
2007.09.19. 16:06:15 com.jme.scene.Node attachChild
INFO: Child (Text) attached to this node (FPS node)
2007.09.19. 16:06:15 com.jme.scene.Node <init>
INFO: Node created.
2007.09.19. 16:06:15 com.jme.scene.Node <init>
INFO: Node created.
2007.09.19. 16:06:15 com.jme.scene.Node attachChild
INFO: Child (north) attached to this node (skybox)
2007.09.19. 16:06:15 com.jme.scene.Node attachChild
INFO: Child (south) attached to this node (skybox)
2007.09.19. 16:06:15 com.jme.scene.Node attachChild
INFO: Child (east) attached to this node (skybox)
2007.09.19. 16:06:15 com.jme.scene.Node attachChild
INFO: Child (west) attached to this node (skybox)
2007.09.19. 16:06:15 com.jme.scene.Node attachChild
INFO: Child (up) attached to this node (skybox)
2007.09.19. 16:06:15 com.jme.scene.Node attachChild
INFO: Child (down) attached to this node (skybox)
2007.09.19. 16:06:17 com.jme.scene.Node attachChild
INFO: Child (skybox) attached to this node (reflectNode)
2007.09.19. 16:06:17 com.jme.scene.Node <init>
INFO: Node created.
2007.09.19. 16:06:18 com.jme.scene.Node attachChild
INFO: Child (Torus) attached to this node (objects)
2007.09.19. 16:06:18 com.jme.scene.Node attachChild
INFO: Child (box1) attached to this node (objects)
2007.09.19. 16:06:18 com.jme.scene.Node attachChild
INFO: Child (box2) attached to this node (objects)
2007.09.19. 16:06:18 com.jme.scene.Node attachChild
INFO: Child (box3) attached to this node (objects)
2007.09.19. 16:06:18 com.jme.scene.Node attachChild
INFO: Child (box4) attached to this node (objects)
2007.09.19. 16:06:18 com.jme.scene.Node attachChild
INFO: Child (box5) attached to this node (objects)
2007.09.19. 16:06:18 com.jme.scene.Node attachChild
INFO: Child (objects) attached to this node (reflectNode)
2007.09.19. 16:06:18 com.jme.scene.Node attachChild
INFO: Child (reflectNode) attached to this node (rootNode)
2007.09.19. 16:06:18 com.jme.renderer.lwjgl.LWJGLTextureRenderer <init>
WARNING: FBO not supported.
2007.09.19. 16:06:18 com.jme.renderer.lwjgl.LWJGLPbufferTextureRenderer setMultipleTargets
INFO: Render to Texture Pbuffer supported!
2007.09.19. 16:06:18 com.jme.renderer.AbstractCamera <init>
INFO: Camera created.
2007.09.19. 16:06:19 com.jme.renderer.lwjgl.LWJGLPbufferTextureRenderer setupTexture
INFO: setup tex8: 128,64
2007.09.19. 16:06:19 com.jme.renderer.lwjgl.LWJGLPbufferTextureRenderer setupTexture
INFO: setup tex9: 128,64
2007.09.19. 16:06:19 com.jme.renderer.lwjgl.LWJGLPbufferTextureRenderer setupTexture
INFO: setup tex10: 128,64
After this it uses about 30-40 MB of memory and 1G+ and more and more Virtual memory...maybe a driver issue? It doesnt start, just eats and eats...
Nvidia 6200Go
How can I force pbuffer off?
sort of off topic, but why would disabling FBO actually INCREASE performance? Shouldn't it be the other way arround? Or if the overhead of the native FBO causing that?
good eye… I wrote the fps backwards… sorry.
There's no easy way to force it off… but I'd suggest trying to update your drivers. Your card should support fbo.
renanse said:
There's no easy way to force it off... but I'd suggest trying to update your drivers. Your card should support fbo.
Sounds okay, but I want it to work with no-FBO cards too, for my game is to be run on older cards too. So I will add some tricky force waterrenderpass pbuffer off switch to the game anyway, for problems with older cards/drivers + water and pbuffer.
Upgrading the driver I can run it with fbo.
Screenshot:
