Is you engine acting on OpenGL state such as the glViewport coordinates, or the near and far clip planes ?

Also, you may want to check thr Background Texture Access sample, which shows how to render the video texture on a mesh, and illustrates all the OpenGL commands involved in the process.

This might shed some light on possible conflicts with your engine.

My engine is at an upper level, it is based on OpenGL, but there are some objects such as perspertive camera, orthographic camera, Modelinstances for 3D objects.

The 2D objects can be rendered via a batch based on an ortho2D projection, but the settings are a mystery for me, even with the vuforia examples.

I also tried to get the image buffer to make the BG render by myself, but the buffer had issues beeing converted to a texture...

In order to render the Video Background, you can use the method bindVideoBackground() (instead of using drawVideoBackground);

this method simply binds the video BG texture, so you should not need to copy any buffer into a texture (i.e. Vuforia generates the texture internally and inds it);

then you could try to apply the texture to a geometry of your choice, such as a simple Quad; if this works, then you could resize the quad so to fit the screen.

The Background Texture Access shows the maths for computing the quad size for rendering the BG texture.

If you experiment a bit using the biindVideoBackground(), it should be possible to find the correct setup.

So, If I bindVideoBackground instead fo rendering it, do I need to make something more ?

Are there some limitations ?

For now, each frame I call begin() then bindVideoBackground(n), [Here I try to render a quad with the binded texture in my 3D engine] and of course end()

Thanks.

The bindVideoBackground simply binds a texture; this is equivalent to binding a texture in OpenGL; 

this emans that any subsequent geometry that you render will be textured by that texture (the video background), provided that:

- you don't bind another texture in your own engine (i.e. you don' overwrite the video texture with your own)

- your mesh has texture coordinates

Ok thanks.

I thing I got it, it's more or lesse running, I'll fix some issues.

Maybe you'll be interesseted in an article on vuforia integration with libgdx 3D engine when working ?

Yes, that would be nice.

A little more question if you don't mind : 

How the texture coordinates are managed on the binding ?

I mean, is the texture full of camera's pixels ? I have some black borders on my rect rendering the texture, and my UV's are from 0 to 1.

Thanks!

Edit : 

This is in my logs :

01-28 10:41:41.366: I/Vuforia_Sample_Applications(10499): Configure Video Background : Video (640 , 480), Screen (854 , 480), mSize (854 , 640)

That's correct; the video background texture may contain some black areas (borders), due to the difference between the texture size and the actual width/height of the video image; check the Background Texture Access sample code, which shows all the maths involved to compute the right UV texture coordinates so to be able to capture only the relevant part of the texture.

where can I find the "Background Texture Access sample code" you mentioned`?

If you download the Vuforia samples, you will find one that is called "BackgroundTextureAccess".

ok i think i found what you ment:

         VideoBackgroundTextureInfo texInfo = Renderer.getInstance()
            .getVideoBackgroundTextureInfo();
        // These calculate a slope for the texture coords
        float uRatio = ((float) texInfo.getImageSize().getData()[0] / (float) texInfo
            .getTextureSize().getData()[0]);
        float vRatio = ((float) texInfo.getImageSize().getData()[1] / (float) texInfo
            .getTextureSize().getData()[1]);

To conclude on how to make a Vuforia integration with libgdx, here is a sample on how to render a 3D object using the vuforia bind() method : 

https://gist.github.com/VinceAngel/8707565

Nice, thanks for sharing.

Hi, I found this thread looking for how to display the videobackground. I tried your code and got the same effect. 

To fix it I took a different approuch that what this thread shows.

When setting the camera up the position was set to (0, 0). I changed this to half width and half height like so: