mirror of
https://github.com/TorqueGameEngines/Torque3D.git
synced 2026-02-13 03:33:48 +00:00
don't trace setShaderConsts or onNewMessage callbacks
they spam up the console to uselessness when using the trace(true/false) command
This commit is contained in:
parent
ccd30a19cc
commit
83a3ef877e
2 changed files with 8 additions and 1 deletions
|
|
@ -44,6 +44,7 @@
|
|||
#include "materials/shaderData.h"
|
||||
#include "postFx/postEffectManager.h"
|
||||
#include "postFx/postEffectVis.h"
|
||||
#include <console/consoleInternal.h>
|
||||
|
||||
using namespace Torque;
|
||||
|
||||
|
|
@ -1126,8 +1127,10 @@ void PostEffect::_setupConstants( const SceneRenderState *state )
|
|||
Con::setFloatVariable("$Param::NearDist", state->getNearPlane());
|
||||
Con::setFloatVariable("$Param::FarDist", state->getFarPlane());
|
||||
}
|
||||
|
||||
bool tracing = Con::gTraceOn;
|
||||
Con::gTraceOn = false;
|
||||
setShaderConsts_callback();
|
||||
Con::gTraceOn = tracing;
|
||||
}
|
||||
|
||||
EffectConstTable::Iterator iter = mEffectConsts.begin();
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue