The geometry files are cached separately from the palette files, allowing for greater sharing. However, you must give each instance a unique name so that they do not end up sharing geometry inadvertently. xgen file to be used multiple times in order to populate a forest or a crowd. The palettes are cached based on their name, which includes the name of the nameSpace. If the palette has already been cached, then the file is not read, but instead the process skips ahead and begins emitting the face procedurals for the named patch. It then emits face procedurals for all of the faces on the named patch. If it determines that this is the first time that the given palette has been hit, it loads in the palette file, reads the appropriate geometry for the motion samples, and caches it. When a patch procedural is cracked, it parses the parameters. The bounding box should bind all motion samples for that patch. If it is too large, the procedural cracks open too soon and memory is wasted. It must bind all of the faces and all of the primitives that are to be rendered. A bounding box must be given for the patch procedural.
It is the patch procedural that takes all of the flags given below.
#RENDER VIEWER USING MAYA ONE INSTEAD OF RENDERMAN IT CRACKED#
It is only when the face procedural is cracked that primitives are generated and therefore any real rendering begins. XGen expands those into face procedurals when, and if, the patch procedural is cracked open. The rib generator is responsible for putting the patch level procedural calls into the rib.
There are two forms of the XGen RenderMan procedural: patch and face.
0 kommentar(er)
