Horde3D

Hi,

I am trying to use a

created renderable texture as a render target. How do I set this up in the pipeline definition? I tried:

which fails with:

From the source code in egPipeline.cpp it seems clear that it does.

My question is: What is the right way to submit such a texture as a valid rendering target for a pipeline stage?

Any help will be greatly appreciated.

Henrik

You need to bind your renderable texture as output buffer to a camera (CameraNodeParams::OutputTex) and call Horde3D::render with that camera. Inside the pipeline you just bind no render target in order to write to that output buffer. From the docs:

Thanks. That works great.

At least most of the time. Sometimes the textured polygon is just black, no rendered image appears. Restarting the application often helps. Can this be a timing problem? It looks non-deterministic?

Also, how can I enable the depth buffer for my render target? Normaly this seems to be done with the depthBuf attribute on the RenderTarget element.

Henrik

At the moment you can't have a depth buffer for renderable textures outside the pipeline. This should be enhanced in the future.

I have tried to follow the steps you suggested (set OutputTex, render the camera, unbind targets), yet my supposedly-rendered-to-textures come out all black.

I create an empty texture with:

This is bound to a camera (the camera uses the forward pipeline that comes with the demos) with:

The render-to-texture camera is rendered before the main camera, and finalizeframe is called after the main camera render.

The texture (texRes with name "NewRenderTexture") is referenced in a material file:

Yet the geometry drawn with this material comes out all black. If I render the render-to-texture camera after the main camera, Horde3d switches to the debug renderer.

Any ideas?

You should create the renderable texture before the material using it is loaded (otherwise the texture already has been added by the material and will be non-renderable). If Horde switches to debug view, it could mean that the pipeline used for rendering is not found or not valid. Are there any debug messages in the log?

Hmm. It seems that I'm seeing the same non-deterministic behavior as monophon.

I created a special pipeline that does nothing but clear buf0 to red. On one computer it never works (the render-to-texture textured boxes which should be red are black). On another computer it works maybe 30% of the time, but using the forward pipeline in RTT never works. On a third computer both the red pipeline and the forward pipeline work in RTT about 80% of the time (although the lack of depth buffer makes the result look quite weird).

The computer on which it never works has the best graphics card of the three (an nvidia gtx260), so I doubt the problem stems from a lack of graphics card capability.

My program is running all the graphics from a single thread, and I'm sure that everything happens in exactly the same order every time.

Hmm, difficult to say what goes wrong here. If you could provide a minimal sample, I can test it on my machine. You could also try to step into the Horde code with your debugger to see if there are some obvious problems.

I'm working with Wakka. I've created a minimal test by modifying the Chicago demo, and attached the added and changed files (just app.cpp and app.h and some additional resources). If you uncompress the zip into the horde3d folder of beta 3, it ought to work.

When it works there should be a blatantly obvious square with RTT working on it right in front of you when you start the chicago demo. To get around the no depth buffer on output textures, it uses a forward pipeline that renders everything to an intermediate buffer first and then copies that to the output target (a texture in this case).

On this computer, it works all the time provided you run outside of debugging mode. If you run in debugging mode, the RTT texture is just black. Additionally, I got an assertion failure once (complaining that there was an opengl error).

Ok, using Pyry's patch on this machine (Pentium D w/ GeForce 9800GT running Ubuntu Jaunty), I am getting about a 50% hit rate. That is, 50% of the time, when I start the modded Chicago, I get an RTT square, and 50% of the time I get a completely black square. I've restarted it about 40 times, and I can't see any pattern predicting when it will work.

Thanks for the repro case. I can see the problem but some quick debugging did not yet reveal what's going wrong.

The problem is hopefully fixed now in the latest svn version. Could you please confirm that using your application?

Hay! Can any one tell me how to implement "Render To Texture" on H3D.................. or any working demo link would be fine.................. I mean rendering from a different camera( in this case i called it 2nd camera) into a texture, and i don't want to show that 2nd camera rendered buffer on the screen but into a texture so that i can use it as a texture for a CCTV model...............

_________________
~@AlmahmudRony@~

You should probably use render to texture somewhat like this:
1) Load pipeline (a custom one or a standard) for the second camera
2) Create second camera with this pipeline
3) Create texture and mark it as renderable. h3dCreateTexture( "tex1", width, height, H3DFormats::BGRA8, H3DResFlags::TexRenderable)
4) Set output texture for the second camera. h3dSetNodeParamI( cam2Idx, H3DCamera::OutTexResI, textureIdx)
5) h3dRender with the second camera
6) Apply the texture id to the material of the desired object. h3dSetResParamI( matID, H3DMaterialRes::SamplerElem, 0, H3DMaterialRes::SampTexResI, textureIdx)

I have not tested it, so it may not be fully functional.

Thank you Irdis............. its working but still having some problem.... if i use forward pipeline with 2nd camera its rendering the texture with alpha transparent ........... and if i use deferred pipeline with the 2nd camera its making something crazy, actually its rendering depth buffer only ....... You can take a look to those screen shot.............

_________________
~@AlmahmudRony@~