How to generate warnings/errors when physical materials aren't assigned to collision or materials
We're facing a problem here where it's very easy to forget to tag collision primitives or materials with Physical Materials. We are dealing with this by generating ugly effects in the game when things aren't tagged and objects collide with them. For various reasons, we'd much prefer helpful warnings that help artists recognize when things aren't tagged properly instead of generating these effects.
Seems like this is just what Map Check was made for, but is there an easy way for content makers or our tech artists to generate new types of warnings - using Blueprint, instead of digging deep into C++ to create new warnings or errors?
asked Aug 12 '15 at 09:28 PM in Everything Else
Follow this question
Once you sign in you will be able to subscribe for any updates here