![]() This occurs, for example, with MaterialFilenameResolve Ops as these Ops are created implicitly when a file name needs to be resolved, so no Katana node is identified as the creator. ![]() In cases where the Op was created implicitly, the node name will equal _NoName_ and the type will equal _NoType_. In cases where an Op is spawned directly by a Katana node, the name and type of that node are recorded. Note:The name and ID do not need to correlate. For example, an OpScript Op may have name op74, type OpScript.Lua and ID 77. The name, type and numerical ID of the Op.Įach Op has name, type and a unique numeric ID.The overhead of capturing profiling data during a Preview Render with Profiling is minimal, and there should not be significant slowdown compared to a normal Preview Render.Ī Preview Render with Profiling captures the following information for each Op that is executed during scene traversal: ![]() If the renderer implements the finalize() method of the Geolib3-MT runtime, these profiling reports will be created when the runtime is finalized otherwise reports will be written when the render finishes. This option will be available for any renderer that already supports a Preview Render, and requires no additional work on the part of the renderer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |