jMonkeyEngine.org

I’m also looking forward to this maven update, thanks for the effort

Well yes, the main difference is, that the actuall Buffers used are just slices, so the allocation costs are near zero (even with that kinda inefficient loop I use currently, a binary tree would be more suited for […]

Looks like he allocates one huge buffer and then just returns slices of it… so at least all of the core allocation routines have changed. In theory, fragmentation is the only danger. I assume the JNI layer is […]

Can you explain what you changed?

Mhh ok, i guess the data is not in the image but in the framebuffer
look at how it’s done in the ScreenShotAppState […]

Hi again,

So is this normal if I still see an empty image in my texture after waiting for the first render (I always let the game begin before adding the breakpoint, so I am sure the render is occurred) ?

I […]

Well, I waited to see the cube on my screen before adding the breakpoint in Netbeans, so I am pretty sure the render has occurred at least once…

@orabeyrolles said:
I don’t understand, what do you mean by “don’t have to deal with the texture itself” ? My final goal is to get the raster contained (somewhere) in the texture (I realize I didn’t explicit […]

@nehon said:
Maybe you should try to use several viewPorts and just add a processor to each viewport, so you wouldn’t have to deal with the texture itself.

I don’t understand, what do you mean by “don’t […]

Maybe you should try to use several viewPorts and just add a processor to each viewport, so you wouldn’t have to deal with the texture itself.

See TestMultiViews […]