FMaterialCompiler::IsCurrentlyCompilingForPreviousFrame

The compiler can run in a different state and this affects caching of sub expression, Expressions are different (e.g. View.PrevWorldViewOrigin) when using previous frame's values If possible we should re-factor this to avoid having to deal with compiler state

Windows
MacOS
Linux

References

Module

Engine

Header

/Engine/Source/Runtime/Engine/Public/MaterialCompiler.h

Include

#include "MaterialCompiler.h"

Syntax

virtual bool IsCurrentlyCompilingForPreviousFrame() const

Remarks

The compiler can run in a different state and this affects caching of sub expression, Expressions are different (e.g. View.PrevWorldViewOrigin) when using previous frame's values If possible we should re-factor this to avoid having to deal with compiler state

Help shape the future of Unreal Engine documentation! Tell us how we're doing so we can serve you better.
Take our survey
Dismiss