![]() You'd have to instruct users to run your tools, rather than resort to the usual workflows, but if the little effort is worth it, you shouldn't find it difficult. Provided it warns users (or even auto-fixes the issues), then starting a render could be avoided.ī) Similarly to the above, make your own render button which in actual fact first runs the sanity checker, and only if that is passed (or fixed) the render command is issued. ![]() ![]() What i could think of is one of two things:Ī) The simplest solution is to run the sanity check independently. I'm not sure what to do.Nothing at rendertime i can think of.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |