Object Rendered by Visualizer Flicker when the TAA option is enabled

[liu.yan]

If TAA in render options is enabled, the solid sphere rendered by Visualizer::renderSolidObject will flicker violently.

 

The renderSolidObject is called every time when the world updates or renders.

 

What can we do to solve this problem?

[silent]

liu.yan

 

Is there full source code available for the stable reproduction?

Thanks!

[liu.yan]

like this:

int CLBUNAppWorldLogic::init()

{

Unigine::Console::get()->setInt("render_antialiasing", 2);

return 1;

}

 

int CLBUNAppWorldLogic::render()

{

Unigine::Visualizer::get()->renderSolidObject(pCurrentObject, Unigine::Math::vec4(0, 1, 0, 1));

return 1;

}

[silent]

What is pCurrentObject? Is there .mesh file available for that geometry?

[liu.yan]

Use the default material ball in default project.

 

I mean, use the default material ball shown in the picture below,  you would reproduce the problem.

[silent]

liu.yan

 

Thanks, I've successfully reproduce this issue. Flickering is happens because real geometry is interfering with visualizer. 

Maybe disabling rendering of the object will help in your case? 

 

For example:

mesh_0 = ObjectMeshStatic::create("material_ball.mesh");
mesh_0->release();
mesh_0->setTransform(translate(Vec3(-2.0f, 0.0f, 0.0f)));	
mesh_0->setMaterial("mesh_base", "*");
mesh_0->setViewportMask(0, 0);

Unigine::Visualizer::get()->setEnabled(1);
Unigine::Visualizer::get()->renderSolidObject(mesh_0->getObject(), Unigine::Math::vec4(0, 1, 0, 1));

In that case there will be no flickering and visualizer will display correctly.

 

Thanks!

[liu.yan]

The code fragment you had provided does solve the problem, thanks.

In TAA, we still can't render mesh and Visualizer solid together, will you solve that in future version?

[silent]

liu.yan

 

It's hard to say right now. The issue is not critical and there is a simple workaround available. In case of any updates I will surely let you know.

 

Thanks!

[liu.yan]

Morning, silent:
   Our next version development is about to start. Is it possible that this problem shall be solved in your recent release?
   I am reluctant to bother you on this unimportant problem, but our product manager had developed various applications based on this issue.

[silent]

liu.yan

 

I'm afraid, this issue is still persist in the latest update.