I'm doing bridge tests to hopefully solve some problems.
There is a bug where if more than 1 object is selected and you run tSBridge.SynchronizeObject then the objects get copied.
this image shows the reason why. Model will temporarily group selections into a "Selection" group object.
The sequence of events is this:
2 items selected
model creates the Selection object
run the synch command - it sees Selection on Model side so it copies the missing objects
but the objects already exist so it renames them
now the 2 halves are out of sync - model has copies of the original selected items and workspace has the renamed copies
This is all weird and confusing, but the root cause is the temporary Selection group that exists in Model but not in Workspace.
Bridge Synchronization Investigation
- clintonman
- Captain
- Posts: 5422
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
- clintonman
- Captain
- Posts: 5422
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
Re: Bridge Synchronization Investigation
According to the docs an empty string will sync the scene
This creates a copy of the scene in Model. It is a group with the name of the scene
If you explicitly tell it to sync the scene then the group object is not created in Model
Code: Select all
tSBridge.SynchronizeObject("")
Code: Select all
obj = Space.CurrentScene()
tSBridge.SynchronizeObject(obj)
Re: Bridge Synchronization Investigation
Yikes!
Running Synchronize
Running Synchronize
Re: Bridge Synchronization Investigation
Discovered that using the tSBridge.SynchronizeObject() command generates an error when rendering Workspace's - Render to File animation
Even using the tSBridge.SynchronizeObject() command within a Try & Catch (Error) does not work! Works fine when using Model's Render to File
Even using the tSBridge.SynchronizeObject() command within a Try & Catch (Error) does not work! Works fine when using Model's Render to File
- clintonman
- Captain
- Posts: 5422
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
Re: Bridge Synchronization Investigation
Workspace Render to File animation doesn't work with command scripts. That's why the command script processing stuff is in the d3d render scripts.trueBlue wrote: ↑26 Mar 2021, 16:54 Discovered that using the tSBridge.SynchronizeObject() command generates an error when rendering Workspace's - Render to File animation
Even using the tSBridge.SynchronizeObject() command within a Try & Catch (Error) does not work!
Bridge Synchronize Script ERROR.png
Works fine when using Model's Render to File
Re: Bridge Synchronization Investigation
Workspace's Render to File animation doesn't work with command scripts because it will throw an error
Workaround with Synchronize running
Use Model's Render Scene to File with Animation set to Workspace
Have you noticed that Lightworks background color & image is not working when rendering a Workspace animation from Model?
Workaround with Synchronize running
Use Model's Render Scene to File with Animation set to Workspace
Have you noticed that Lightworks background color & image is not working when rendering a Workspace animation from Model?
- clintonman
- Captain
- Posts: 5422
- Joined: 21 May 2009, 21:08
- Type the number ten into the box: 0
- Location: California
- Contact:
Re: Bridge Synchronization Investigation
Makes sense since it's rendering workspace and not modelspace.trueBlue wrote: ↑29 Mar 2021, 13:53 Workspace's Render to File animation doesn't work with command scripts because it will throw an error
Workaround with Synchronize running
Use Model's Render Scene to File with Animation set to Workspace
Have you noticed that Lightworks background color & image is not working when rendering a Workspace animation from Model?