The only way I can think of to get this to work for base.render is to attach a new node to render then force this back into builtins so any subsequent call to “render” will give this new node. A new feature in Premiere Pro lets you take a clip on the timeline and render it into a different format, and replace the original automatically. Keeping base.cam would be easy enough just create another camera for the editor to use. movie and automatically replace them with the rendered file in your comp.

In order for a developer to maintain their coding style it would be necessary for base.camera and base.render to point to their game nodes and not those the editor uses. But, did you know that you can save the RAM Preview right from memory as a. This stops unwanted behaviour like being able to pick your own manipulators or saving them out to file, as the scene is only interested in what is below its own root.įor the most part this approach works well, but now I’m getting into interesting territory where the user can drop scripts onto objects.

In developing my editor I’ve come to a point where it might be useful to replace the scene graph root, aka “render” with another node.Ĭurrently each scene created by the editor has its own root node.

What does render and replace do