I'm wondering if you can export a usd file programmatically using python.
I noticed that there isn't a usd format id listed under the SaveDocument documentation
Is there another way?
Latest posts made by lionlion44
-
exporting usd with python
-
RE: 'Octane Renderer' menu settings not appearing when I switch render data to octane with python.
I have found what seems like a solution:
ID_OCTANE_RENDERER = 1029525 render_data = doc.GetActiveRenderData() render_data.InsertVideoPostLast(c4d.documents.BaseVideoPost(ID_OCTANE_RENDERER)) render_data[c4d.RDATA_RENDERENGINE] = ID_OCTANE_RENDERER c4d.EventAdd()
I just needed to insert the video post. I am yet to test it, but it at least looks correct.
-
'Octane Renderer' menu settings not appearing when I switch render data to octane with python.
I am trying to switch the renderer to octane using python, I've achieved this with the following:
ID_OCTANE_RENDERER = 1036219 render_data = doc.GetActiveRenderData() render_data[c4d.RDATA_RENDERENGINE] = ID_OCTANE_RENDERER c4d.EventAdd()
However if I do this to a fresh document it doesn't seem to initialise some settings. The 'Octane Renderer' menu item doesn't appear unless I switch back and forth to a different renderer manually.
What I want:
What I get:
Is there anything else that happens when you set the renderer manually that I need to account for?
Thanks -
RE: Automatically solo objects by using the 'path' of the object manager?
Hey @ferdinand ,
Thanks for the quick response. To describe my request more specifically, I was wondering if the path bar in an object manager could be used to solo objects. This way I could have multiple nulls containing different parts of the project, then by setting the root of the path bar to a null it would solo the things in that null. This would also mean I'm only seeing the soloed objects in the object manager. That's what I meant by continuity, the object manager and the viewport would have the same content.
Ultimately, I'm trying to find a workflow that allows for isolating chunks of the project to be worked on one at a time but the basic solo feature is a bit. After doing a bit more research it looks like layers is the way to go. When using layers the solo feature hides the other layers in the viewport and the object manager. If the original idea is still possible I'd be interested, simply because I think it would be a bit more frictionless (no need to add object to layers, soloing tied to object hierarchy, workspaces inside of workspaces). But I understand it's a strange request. I'm comfortable using the standard layers and soloing features for now.
Cheers,
Leo -
Automatically solo objects by using the 'path' of the object manager?
Hey there,
I'd love to be able to automatically solo the object that are inside the current 'path' parameter in the object manager. Is this possible using python or an easier method. This way the object manager and the viewport would have continuity with each other.
Thanks