[SOLVED] Auxiliary buffer from received null

[ankush.wadke]

Hello,

We are working with Unigine 2.5, using Unigine by extending a class from the App class and calling update(), render() and swap() manually. We have setup a material's auxiliary flag on from the unigine editor. But when we try to access the auxiliary buffer inside the callback set at "CALLBACK_END_OPACITY_GBUFFER" , by calling ,

Unigine::TexturePtr auxBuffer = _renderer->getTextureAuxiliary();

auxBuffer is always NULL.

setting the callback at "CALLBACK_END_AUXILIARY_BUFFER" dose not work either, what more should be check to enable the Auxiliary pass.

We tried in the Gbuffer sample, auxBuffer is not null there. Is there something we are missing out on?

Edited July 14, 2018 by ankush.wadke

[Greg.Mildenhall]

No doubt there are many things that could cause that, but one obvious one is that auxiliary rendering might be disabled. Check render_auxiliary from the console.

[ankush.wadke]

Hello Greg,

Thanks for the reply, and the "render_auxiliary"  flag is 1. and so is the "auxiliary" flag of a material being rendered in the frustum.

Edited July 16, 2018 by ankush.wadke

[ankush.wadke]

Hello guys,

We figured out the problem, the "auxiliary" state of the material was not being set in the worldLogic's init/update but some where else. Now its working fine after the material's property is being updated in the world logic.