United3dArtists Archive

trueBlue · Post by **trueBlue** » 29 Mar 2019, 14:26

Sounds Ambitious!

Thanks again!

trueBlue · Post by **trueBlue** » 29 Mar 2019, 14:44

I have made some changes to the trueSpace 7.61 Beta 8 Unofficial Update (Full version)
Revision dated March 28, 2018
viewtopic.php?t=3732#p37396

Bridge Synchronize - Author Clinton Reese
Updated new changes and added a Help panel

Cube Widget - Author Clinton Reese
Updated the XYZ colors to the default tS76 XYZ colors

Point Edit widget 1, 2, and 3
PE Pivot Snap - Author Clinton Reese
P + LMB select the widget sets the Pivot to the selected element
New - Changed the status message so that it clears after several seconds.
New - P + RMB select the widget moves and rotates the Pivot to the selected Face
New - P + MMB select the widget moves and rotates the Pivot to the object's Center
Changed the Point Edit widget 3 back to the default tS76 XYZ colors

Background, Camera 2, Object Navigation, and Point Edit widget(S)
New - i + LMB select the widget opens it's Widget Help panel

Model File menu
New added - Tools/ Spline Polygon tool

WorkspaceMain, WorkspaceMain2, BottomBar, and BottomBar2 toolbars
* 2D Unencapsulate
Restored the original command to the Unencapsulate button and changed the tooltip to 2D Unencapsulate

trueBlue · Post by **trueBlue** » 03 May 2019, 16:10

I have made some changes to the trueSpace 7.61 Beta 8 Unofficial Update (Full version)
Revision dated May 03, 2019
viewt ... 732#p37396

Updated:
Components - Compositing library - Author Clinton Reese
viewt ... =31&t=1676
Clintons3dPlugin.rsx v.1638413 - Author Clinton Reese

Thanks Clinton!

trueBlue · Post by **trueBlue** » 23 May 2019, 18:00

I have made some changes to the trueSpace 7.61 Beta 8 Unofficial Update
Revision dated May 23, 2019
viewt ... 732#p37396

Updated the Nurbs Curves scripts - Author Clinton Reese
viewt ... 390#p54681

Added a Help button on the Notes aspect that directs you to:
http://www.clintons3d.com/plugins/trues ... urves.html

: Capture.PNG (7.46 KiB) Viewed 4542 times

Thanks Clinton!

trueBlue · Post by **trueBlue** » 24 May 2019, 23:53

I have made some changes to the trueSpace 7.61 Beta 8 Unofficial Update
Revision dated May 23, 2019
viewt ... 732#p37396

Updated the Point Clone script - Author Clinton Reese

Thanks Clinton for the updates!

trueBlue · Post by **trueBlue** » 23 Jul 2019, 18:49

So I think I have found a solution for the Bridge not working between Model and Workspace.
From what I can tell there is no synchronization from Workspace to Model and the Views from either side.
Here is a Synchronize Camera that seems to work.
Drop it into Workspace, open a Model view, and Activate it.

If you find that the Camera is not showing correctly in Model, Select the Synchronize Camera, and from Model select the View from Object
If you Minimize this node it in the Link Editor some interactions will stop working from Workspace.

Also here is a tS761 First Person Navigator version.
Select the tS761 First Person Navigator, from Model select the View from Object, and select the View button.

Files removed due to update.

clintonman · Post by **clintonman** » 23 Jul 2019, 20:36

Nicely done. You should be able to make the modelside activate the camera reliably by having it in it's own node after the Connect node. I tested by having the view through a light and then pressing the activate button and it works with the modification. Without the modification I needed to deactivate and activate again to get it to switch views.

Code: Select all

tSBridge.SuggestTSStateByAlias("SV_VIEW_VIEW_CAMERA")

trueBlue · Post by **trueBlue** » 23 Jul 2019, 21:44

Not sure what you mean, I am using that command.
Had a heck of a time getting it to work reliably. At first I had all of the scripts as one in a button script. I then broke it up.
Before if you had an object selected and then run the script, even though I had commands to unselect, object tool for model and workspace, and the select this camera, Model would use the last selected object to view from.
You would also notice that Model would change to Top view. Strange!
I have updated the script to run tSBridge.SuggestTSStateByAlias("SV_VIEW_VIEW_CAMERA") twice and that seems to work better.

clintonman · Post by **clintonman** » 23 Jul 2019, 21:59

Here's a sample of what I mean. I just added the node at the end which only has the button press code. 100% reliable as far as I can tell.

EDIT:
Needs a way to switch workspace to the camera view as well.

trueBlue · Post by **trueBlue** » 23 Jul 2019, 22:06

Yep that works as you are running the command twice.
So do you think this should be incorporated into the update?
Thinking about adding a button to the Desktop panel that calls it.
Edit: It does -> D3DView.SetActiveCamera("", '{2C152F81-45A2-4035-8896-9E49D60C8A7A}')
Is that not working for you?

clintonman · Post by **clintonman** » 23 Jul 2019, 22:26

trueBlue wrote: 23 Jul 2019, 22:06 Yep that works as you are running the command twice.
So do you think this should be incorporated into the update?
Thinking about adding a button to the Desktop panel that calls it.
Edit: It does -> D3DView.SetActiveCamera("", '{2C152F81-45A2-4035-8896-9E49D60C8A7A}')
Is that not working for you?

If you remove the first one it still works. It works because it's running last not because it's running twice.
Nope, that doesn't work for me. It would be better to not have it hard coded to the "{2C152F81-45A2-4035-8896-9E49D60C8A7A}" value if possible. I switched the main view to modelspace and have a smaller 3d view for workspace. Maybe you have the opposite or something different? In any case a computed value should work for all cases, assuming it's possible.
Just did a test copying the value I see on the D3dView/EyeCamera_{1C93CC97-5189-46E6-98FF-DDB3147F492F} node of "{1C93CC97-5189-46E6-98FF-DDB3147F492F}" and that works for me.

trueBlue · Post by **trueBlue** » 23 Jul 2019, 22:50

Okay I will add the old command in addition to the one using the WinId
D3DView.SetActiveCamera('', '')
With this command you must have the Workspace window in focus.

trueBlue · Post by **trueBlue** » 23 Jul 2019, 23:44

See if you like this setup.
Replace your System/Preferences with this one. Open up Settings and select the Synchronize Camera button on the Desktop panel.

File removed due to update.

clintonman · Post by **clintonman** » 24 Jul 2019, 01:39

It didn't work for me. Here are my modifications to make it work with any 3d window.
I'm not so sure it should delete and replace itself in the scene. Maybe it should be a special camera instead, that way there can be more than one of them and they could be used as regular cameras as well.

Code: Select all

newcam = Node.Copy("/Preferences/Synchronize Camera", Space.CurrentScene())
UserInterface.OpenPreferencesPanelViewExWithFlag('', '', newcam, 4, 1, 0, 8)

There may be a bridge issue. When I was modifying the code the camera reverted to a modelspace camera. I had to turn off the bridge to make changes, so more testing may be needed to protect against modelspace. I don't know it could only happen when trying to make code changes.

trueBlue · Post by **trueBlue** » 24 Jul 2019, 05:06

Thanks for fixing the Set Camera, works great!
I value your opinion.

Can you explain how using more then one of these could be used in a scene?
Really did not intend this to be used as a Camera. It was the only thing I could come up with to get the views to sync.
Tried using the Eye camera by Synchronizing it, but that did not work.
For me given that it does not work, if it is minimized could be an issue for a user.
I use the Link Editor's Minimize all of the time.

What I really would like to do is make this as transparent as possible.
My thought was since this males the Bridge work, having it included with the Bridge settings made sense.
Defiantly did not like having the panel show in the Settings aspect though.

clintonman · Post by **clintonman** » 24 Jul 2019, 05:55

I agree with everything you said. I thought you wanted the camera because of the matching viewport. In that case I think the "false matching camera" should match the workspace view first instead of the view matching the camera and when deactivated set the workspace view or camera if it was previously a camera view to match the final fake camera position and delete the fake camera so it's only temporary. Just some thoughts, hope this makes sense.

trueBlue · Post by **trueBlue** » 24 Jul 2019, 20:30

Not sure what you are saying but by all means show by an example.
Here is an update.
New name. Synchronize
New camera with no mesh nor material.
Upon load shows the Synchronize's Workspace aspect in Panel.
Deactivate, changes Model and Workspace to Perspective view and deletes itself. Only on the Workspace aspect button.

I notice with your set camera script it only works with two windows.
Try it in the 4View and or with the Default layout main view with two new windows, one with Model view. (The Default view window does not work.)

I could add the following code but there is a big lag in Model, even if I run the script before activating the other script.

Code: Select all

Cam = System.ThisOwner();	
Eye = Node.SubObject("/D3DView", 0);

Node.Value(Cam,"Matrix") = Node.Value("/D3DView/" + Eye,"WldMatrix");
Node.Value(Cam + "/Camera","ClippingFar") = Node.Value("/D3DView/" + Eye,"ClippingFar");
Node.Value(Cam + "/Camera","ClippingNear") = Node.Value("/D3DView/" + Eye,"ClippingNear");
Node.Value(Cam + "/Camera","Focus") = Node.Value("/D3DView/" + Eye,"Focus");
Node.Value(Cam,"FOV") = Node.Value("/D3DView/" + Eye,"FOV");
Node.Value(Cam + "/Camera","Perspective") = Node.Value("/D3DView/" + Eye,"Perspective");

File removed due to update.

clintonman · Post by **clintonman** » 25 Jul 2019, 05:44

trueBlue wrote: 24 Jul 2019, 20:30 Not sure what you are saying but by all means show by an example.
Here is an update.
New name. Synchronize
New camera with no mesh nor material.
Upon load shows the Synchronize's Workspace aspect in Panel.
Deactivate, changes Model and Workspace to Perspective view and deletes itself. Only on the Workspace aspect button.

I notice with your set camera script it only works with two windows.
Try it in the 4View and or with the Default layout main view with two new windows, one with Model view. (The Default view window does not work.)

I could add the following code but there is a big lag in Model, even if I run the script before activating the other script.
Code: Select all
Cam = System.ThisOwner();	
Eye = Node.SubObject("/D3DView", 0);

Node.Value(Cam,"Matrix") = Node.Value("/D3DView/" + Eye,"WldMatrix");
Node.Value(Cam + "/Camera","ClippingFar") = Node.Value("/D3DView/" + Eye,"ClippingFar");
Node.Value(Cam + "/Camera","ClippingNear") = Node.Value("/D3DView/" + Eye,"ClippingNear");
Node.Value(Cam + "/Camera","Focus") = Node.Value("/D3DView/" + Eye,"Focus");
Node.Value(Cam,"FOV") = Node.Value("/D3DView/" + Eye,"FOV");
Node.Value(Cam + "/Camera","Perspective") = Node.Value("/D3DView/" + Eye,"Perspective"); 

It works by looking at the current active window, so if you click the button in the link editor, the link editor becomes the active window. If you click the button in the panel view, the panel view becomes the active window. Only place I know to press the button and not change the active window is to use a floating panel or a toolbar button. If the active window is not a 3d view it chooses the last 3d view opened.

Can't image why you're getting the big lag in that code.

The way I picture it working is
1. save the state and id of the active 3d view
2. make the synchro cam match the 3d view settings
3. when done delete the synchro cam and restore the state of the 3d view

It looks like you're already headed in that direction. Only instead of setting the 3d view to perspective it would be set back to it's original state.

trueBlue · Post by **trueBlue** » 25 Jul 2019, 17:55

Thank You!
Found out the issue with the lag was that you needed to use your mouse in 3D Space.
Added Activity.Run(System.ThisOwner() + "/Synchronize Scene") to the Connect script fixes that.
Added WindowsManager.ActivateFrame(1) to the Activate script seems to help setting the cam in the main view.

Getting strange results in the 4View layout. Lower right gets changed to perspective/wireframe.

Mostly does not sync with Model.
Isometric view does not work at all.

I am going to suggest that other layouts and or other views are not supported as well as more then 3 views in the Default layout.

I do not think that I accomplished all of your suggestions, but this is the best I can come up with so far.
Also noticing that 'sometimes' this script needs to run twice (after the first time) in order for it to work properly.
Seems that Model reverts to a previous or saved state on first Activate and on Deactivate.

File removed due to update.

clintonman · Post by **clintonman** » 25 Jul 2019, 22:14

Changes:

Saves the state of the workspace window and restores it after deactivation.
Removed the hard coded window id. Will use the first 3d view found instead of the last one when the active view is not a 3d view. I think choosing the first is closer to the hard coded window id behavior.
Removed the exported Perspective connection since it was giving me some trouble.
Started to make changes to restore model view and then realized it wasn't possible to read the model space view state.

Should work in any layout. Only big thing missing is that it live in a floating panel so the active window can be selected properly.

I shrank the workview aspect button only because of editing issues here on my end.

trueBlue · Post by **trueBlue** » 26 Jul 2019, 00:13

Thanks!
Still testing...
I think we are missing something! If the Bridge worked, Model would recognize the Eye cam and we would not have to set View(s) to a camera in Workspace and Model.
So if it did work, I would think that it would not restore the previous or saved Workspace view. It would just end in that state. Same for Model. Right?

Found another issue, a Link Editor has to be open in order for it to work.

clintonman · Post by **clintonman** » 26 Jul 2019, 00:57

trueBlue wrote: 26 Jul 2019, 00:13 Thanks!
Still testing...
I think we are missing something! If the Bridge worked, Model would recognize the Eye cam and we would not have to set View(s) to a camera in Workspace and Model.
So if it did work, I would think that it would not restore the previous or saved Workspace view. It would just end in that state. Same for Model. Right?

Found another issue, a Link Editor has to be open in order for it to work.

So you want it to behave as a camera and not so much like a temporary link with no side effects. If bridge worked it would be like it's always on. In that case why not just make it into a camera and keep it active? I can go either way, since I'm only interested in the bridge syncing aspects of it. The view sync is just a nice addition.

I thought you solved the link editor has to be open limitation. Did it stop working after these last changes or before that? I'll see what I can find out.

Edit:
Just did a test and it seems to work with the link editor closed.

trueBlue · Post by **trueBlue** » 26 Jul 2019, 02:24

More test, it is working really well! Thank YOU!
I am just thinking it should not restore the Workspace view.
So as I understand what you are doing, you are transferring the Eye to Cam, which is great.
But then you are restoring the saved state before it was activated.
What I am thinking is should transfer the Cam to Eye.

Code: Select all

function Execute(params)
{
Eye = Node.SubObject("/D3DView", 0);
Cam = System.ThisOwner();
if (Node.ConExists(Node.Selection(), "Camera"))
{
Node.Value("/D3DView/" + Eye,"tx") = Space.NodeMatrixElement(Cam,'tx');
Node.Value("/D3DView/" + Eye,"ty") = Space.NodeMatrixElement(Cam,'ty');
Node.Value("/D3DView/" + Eye,"tz") = Space.NodeMatrixElement(Cam,'tz');
Node.Value("/D3DView/" + Eye,"roll") = Space.NodeMatrixElement(Cam,'roll');
Node.Value("/D3DView/" + Eye,"pitch") = Space.NodeMatrixElement(Cam,'pitch');
Node.Value("/D3DView/" + Eye,"yaw") = Space.NodeMatrixElement(Cam,'yaw');
Node.Value("/D3DView/" + Eye,"FOV") = Node.Value(Cam, 'FOV')
}

}

Edit: With no Link Editor open Cam transformation works but Object transformation does not. This happens with all other versions too.
Edit: The floating panel is already set to use, you just have to un commit the command.
I do not see a use as your new script works really well.
The reason I set it to show in Panel with the Workspace aspect, is try to avoid a user from minimizing the node in the Link Editor. I do not know how to change the aspect on a floating panel.

clintonman · Post by **clintonman** » 26 Jul 2019, 02:43

Added your code to keep workspace view state.

I moved the button deactivate code on one aspect to a Deactivate script node, because I thought the code would be added there, but it was added to the Restore script instead.

trueBlue · Post by **trueBlue** » 26 Jul 2019, 03:05

Cross post:
Edit: With no Link Editor open Cam transformation works but Object transformation does not. This happens with all other versions too.
Edit: The floating panel is already set to use, you just have to un commit the command.
I do not see a use as your new script works really well.
The reason I set it to show in Panel with the Workspace aspect, is try to avoid a user from minimizing the node in the Link Editor. I do not know how to change the aspect on a floating panel.

trueBlue · Post by **trueBlue** » 26 Jul 2019, 03:43

There was a script error in the Workspace aspect Deactivate button.
Guess it did not like the committed line.

File removed due to update.

clintonman · Post by **clintonman** » 26 Jul 2019, 03:51

Oops, I forgot to uncomment the Node.Delete line.

clintonman · Post by **clintonman** » 26 Jul 2019, 04:02

trueBlue wrote: 26 Jul 2019, 03:05 Cross post:
Edit: With no Link Editor open Cam transformation works but Object transformation does not. This happens with all other versions too.
Edit: The floating panel is already set to use, you just have to un commit the command.
I do not see a use as your new script works really well.
The reason I set it to show in Panel with the Workspace aspect, is try to avoid a user from minimizing the node in the Link Editor. I do not know how to change the aspect on a floating panel.

I added the command to switch to the workspace aspect in the floating window. The line is still commented though.
The RestoreView is checked, I thought you wanted the opposite for the default, where the view is maintained?

trueBlue · Post by **trueBlue** » 26 Jul 2019, 19:19

Yes, I guess I misunderstood the difference.
Not a big deal but if you close a window before Deactivating you will get a script error.

: Capture.PNG (10.6 KiB) Viewed 3762 times

I made a simple example on how I think this project should work.
It was easier to make then try to explain.
It was beyond my capabilities to incorporate your other scripts and I am not saying they should not be used.
The Activate button on the Default and Workspace aspect do the same thing with the exception that the Workspace button deletes the Synchronize.RsObj
The Activate button on the Default aspect works as I was hoping. Model and Workspace views do not change when you Deactivate the script.
The Workspace button does not work like the other does in with which the Workspace view changes. I guess it is the nature of the beast when you delete the Camera when you are viewing from it, as that is the way it works with other cameras. Oddly I watched the Eye camera in this process and it is not being replaced. Even though the Cam2Eye script works on the Default aspect, it does not work on the Workspace aspect. I tried several ways to get it to work to no avail.

In the end I have discovered having this setup in the Link Editor is more efficient. The Model's widget works better!
You just need to use Model and Workspace's interface to view from a camera.

File removed due to update.

clintonman · Post by **clintonman** » 26 Jul 2019, 21:19

trueBlue wrote: 26 Jul 2019, 19:19 ...

In the end I have discovered having this setup in the Link Editor is more efficient. The Model's widget works better!
You just need to use Model and Workspace's interface to view from a camera.
Capture2.PNG

I don't understand what you are showing in the picture. The script I just downloaded doesn't match it.

Edit: Interesting. All the 3D views are set as the camera view.
You have this code which doesn't make sense because the node is not aware of the meaning of %WIN_ID%, only the ui elements can see it :

Code: Select all

Node.Select(System.ThisOwner())
D3DView.SetActiveCamera('', '%WIN_ID%');
tSBridge.SuggestTSStateByAlias("SV_VIEW_VIEW_CAMERA")

This code does the same thing.

Code: Select all

Node.Select(System.ThisOwner())
D3DView.SetActiveCamera('', 'this is crazy stuff');
tSBridge.SuggestTSStateByAlias("SV_VIEW_VIEW_CAMERA")

Ah! Just checked the documentation. It's still a little crazy, but it makes sense.

Code: Select all

Parameters:
    	bsCameraName 	specifies camera name to use (empty string uses selected camera).
    	bsViewName 	specifies the name of the view which should use the camera (empty string uses all views).

"empty string uses all views", it must be ignoring bad input by defaulting to an empty string. I think the way it works is good as long as there is only 1 workspace 3d view open, otherwise it needs to use the code I had before to choose 1 window. You can see in the 4view mode.

Edit: The problem with the delete is because you call Deactivate and then Delete scripts, but Deactivate is connected to Cam2Eye and would run after it except that the Delete runs first.

trueBlue · Post by **trueBlue** » 26 Jul 2019, 22:44

clintonman wrote: 26 Jul 2019, 21:19
trueBlue wrote: 26 Jul 2019, 19:19 ...

In the end I have discovered having this setup in the Link Editor is more efficient. The Model's widget works better!
You just need to use Model and Workspace's interface to view from a camera.
Capture2.PNG
I don't understand what you are showing in the picture. The script I just downloaded doesn't match it.

Edit: Interesting. All the 3D views are set as the camera view.
You have this code which doesn't make sense because the node is not aware of the meaning of %WIN_ID%, only the ui elements can see it :
Code: Select all
Node.Select(System.ThisOwner())
D3DView.SetActiveCamera('', '%WIN_ID%');
tSBridge.SuggestTSStateByAlias("SV_VIEW_VIEW_CAMERA")
This code does the same thing.
Code: Select all
Node.Select(System.ThisOwner())
D3DView.SetActiveCamera('', 'this is crazy stuff');
tSBridge.SuggestTSStateByAlias("SV_VIEW_VIEW_CAMERA")
Ah! Just checked the documentation. It's still a little crazy, but it makes sense.
Code: Select all
Parameters:
    	bsCameraName 	specifies camera name to use (empty string uses selected camera).
    	bsViewName 	specifies the name of the view which should use the camera (empty string uses all views).
"empty string uses all views", it must be ignoring bad input by defaulting to an empty string. I think the way it works is good as long as there is only 1 workspace 3d view open, otherwise it needs to use the code I had before to choose 1 window. You can see in the 4view mode.

Edit: The problem with the delete is because you call Deactivate and then Delete scripts, but Deactivate is connected to Cam2Eye and would run after it except that the Delete runs first.

I got that command from the original Workspace Main toolbar.
I changed it to

Code: Select all

D3DView.SetActiveCamera('', '');

This works in 4View except for the ortho views.
This also works with the main view and 2 other views.

So how should I call them?
Was my understanding that I am calling the Deactivate script (It runs) and then the Delete script runs.

: Capture.PNG (12.31 KiB) Viewed 3657 times

clintonman · Post by **clintonman** » 26 Jul 2019, 23:31

Is the last script you uploaded the latest? Like I said before it doesn't match the link editor picture you showed with it. If we're looking at 2 different versions we could get messed up.

clintonman · Post by **clintonman** » 26 Jul 2019, 23:45

trueBlue wrote: 26 Jul 2019, 22:44 ...
So how should I call them?
Was my understanding that I am calling the Deactivate script (It runs) and then the Delete script runs.
Capture.PNG

Something like this should work. Set the value then only call Deactivate and let Cam2Eye call the Delete.

trueBlue · Post by **trueBlue** » 27 Jul 2019, 00:03

clintonman wrote: 26 Jul 2019, 23:31 Is the last script you uploaded the latest? Like I said before it doesn't match the link editor picture you showed with it. If we're looking at 2 different versions we could get messed up.

That picture is not the last Synchronize.RsObj that I posted.
I was just sharing another example for you that runs more efficient.
The Model's widget works better!
You just need to use Model and Workspace's interface to view from a camera.

trueBlue · Post by **trueBlue** » 27 Jul 2019, 00:41

Here is the latest.
Added your delete script and

Code: Select all

WindowsManager.ActivateFrame(1)

File removed due to update.

clintonman · Post by **clintonman** » 27 Jul 2019, 00:41

trueBlue wrote: 27 Jul 2019, 00:03
clintonman wrote: 26 Jul 2019, 23:31 Is the last script you uploaded the latest? Like I said before it doesn't match the link editor picture you showed with it. If we're looking at 2 different versions we could get messed up.
That picture is not the last Synchronize.RsObj that I posted.
I was just sharing another example for you that runs more efficient.
The Model's widget works better!
You just need to use Model and Workspace's interface to view from a camera.

Ok I see. So how do you want to go forward? We both have the same version, but you say the picture version is better. I dont' see any difference in the efficiency or Model widget working better. What am I missing?

clintonman · Post by **clintonman** » 27 Jul 2019, 00:43

trueBlue wrote: 27 Jul 2019, 00:41 Here is the latest.
Added your delete script and
Code: Select all
WindowsManager.ActivateFrame(1)

Got it.
What does the

Code: Select all

WindowsManager.ActivateFrame(1)

do?

clintonman · Post by **clintonman** » 27 Jul 2019, 01:00

Small change, This one has only 1 Deactivate and 1 Cam2Eye to work with the Delete

trueBlue · Post by **trueBlue** » 27 Jul 2019, 01:00

It Activates (gets focus) the top most trueSpace window where the File menu is.

clintonman · Post by **clintonman** » 27 Jul 2019, 01:47

trueBlue wrote: 27 Jul 2019, 01:00 It Activates (gets focus) the top most trueSpace window where the File menu is.

I did some tests and it looks like it cycles between the last active window docked to the main window and any floating windows. A value of 1 cycles one direction and a value of 0 reverses the direction.
Default layout seems to have 4 docked windows - 3d view, link editor, panel view and object info. Whichever one among the 4 to be active last will be part of the cycle.
You can try it by opening some floating windows, 3d view, link editor, scene view etc, doesn't matter what kind. Drag the script out of the panel and run it several times to see the title bars highlight. Don't run it from the LE or panel view because as soon as you click it becomes active.

trueBlue · Post by **trueBlue** » 27 Jul 2019, 02:07

Not sure what the heck is going on, as I used this example for several hours before I first posted it and worked great.
Now it does not work at all.
I totally give up!
Here is your last version with the floating panel operational and I removed the Model command that set it to Perspective.
It seems to work really well. Sorry for the distraction and wasted effort!

File removed due to update.

clintonman · Post by **clintonman** » 27 Jul 2019, 02:34

trueBlue wrote: 27 Jul 2019, 02:07 Not sure what the heck is going on, as I used this example for several hours before I first posted it and worked great.
Now it does not work at all.
I totally give up!
Here is your last version with the floating panel operational and I removed the Model command that set it to Perspective.
It seems to work really well. Sorry for the distraction and wasted effort!

Maybe the problem was relying on the WindowsManager.ActivateFrame(1) command. I suspect that you have to select the main 3d view and then not select any of the other docked windows for it to work as expected.

clintonman · Post by **clintonman** » 27 Jul 2019, 06:22

Refactored to use the DoDelete flag and simplify the button code.
No error if close the 3d view before deactivate
Works with ortho views, but does not try to match the view or restore them. Final result will be a perspective view.

Tried to match the ortho views but it was just too wonky.

trueBlue · Post by **trueBlue** » 27 Jul 2019, 12:25

Awesome!
Changes:
Camera
FOV to 0.500
Location
Rotation
Added a View button to the Workspace aspect in case you switch to a different non sync camera

Notice that if you Ctrl+ Drag a copy of the Synchronize.RsObj in the Link Editor it gets deleted.
Also if you select the Activate/Deactivate button on the Default aspect, the FOV changes to 3.00
Wonder if it would be better to set the Bridge to On verses Auto?

File removed due to update.

clintonman · Post by **clintonman** » 27 Jul 2019, 13:30

trueBlue wrote: 27 Jul 2019, 12:25 ...

Notice that if you Ctrl+ Drag a copy of the Synchronize.RsObj in the Link Editor it gets deleted.
Also if you select the Activate/Deactivate button on the Default aspect, the FOV changes to 3.00
Wonder if it would be better to set the Bridge to On verses Auto?

I don't remember is this supposed to be a camera or a single item. If a single item there is no way to stop ctrl+drag in link editor deletion. If more than 1 is allowed the delete all others should be removed.

The FOV change to 3 is a test I forgot to comment out. It's there because when testing the orthogonal views the fov was set to low values and when things went wrong I couldn't see in the perspective view cause the camera was in the way.

Will have to research On vs Auto. Don't really know what the difference is.

trueBlue · Post by **trueBlue** » 27 Jul 2019, 15:30

clintonman wrote: 27 Jul 2019, 13:30
trueBlue wrote: 27 Jul 2019, 12:25 Notice that if you Ctrl+ Drag a copy of the Synchronize.RsObj in the Link Editor it gets deleted.
I don't remember is this supposed to be a camera or a single item. If a single item there is no way to stop ctrl+drag in link editor deletion. If more than 1 is allowed the delete all others should be removed.

What I do not understand, is why it happens when it is not Activated.
The Auto Load script is setup to delete more then one upon loading, but that looks like it is not running after it loads.

clintonman · Post by **clintonman** » 27 Jul 2019, 16:01

trueBlue wrote: 27 Jul 2019, 15:30
clintonman wrote: 27 Jul 2019, 13:30
trueBlue wrote: 27 Jul 2019, 12:25 Notice that if you Ctrl+ Drag a copy of the Synchronize.RsObj in the Link Editor it gets deleted.
I don't remember is this supposed to be a camera or a single item. If a single item there is no way to stop ctrl+drag in link editor deletion. If more than 1 is allowed the delete all others should be removed.
What I do not understand, is why it happens when it is not Activated.
The Auto Load script is setup to delete more then one upon loading, but that looks like it is not running after it loads.

I don't follow, it seems to do it as far as I can see.
1. drag into le
2. drag second into le - it's name will be Synchronize, 1
3. second one deletes itself because it's name is Synchronize, 1

trueBlue · Post by **trueBlue** » 28 Jul 2019, 03:31

Just another senior moment.

What I did was, within the Link Editor, I ctrl + dragged a copy of the Synchronize.RsObj to an empty space. Kind of surprised me that the copy got deleted. I now realize it was just the Popup script running. I was under the impression that only worked when loaded into a scene.

Would it be okay to add

Code: Select all

Node.Value("/Preferences/Desktop", "_Widgets_Select_Camera") = 0

to the Activate script and

Code: Select all

Node.Value("/Preferences/Desktop", "_Widgets_Select_Camera") = -1

to the Set Camera script?

clintonman · Post by **clintonman** » 28 Jul 2019, 03:56

trueBlue wrote: 28 Jul 2019, 03:31 Just another senior moment.
What I did was, within the Link Editor, I ctrl + dragged a copy of the Synchronize.RsObj to an empty space. Kind of surprised me that the copy got deleted. I now realize it was just the Popup script running. I was under the impression that only worked when loaded into a scene.

Would it be okay to add
Code: Select all
Node.Value("/Preferences/Desktop", "_Widgets_Select_Camera") = 0
to the Activate script and
Code: Select all
Node.Value("/Preferences/Desktop", "_Widgets_Select_Camera") = -1
to the Set Camera script?

Sounds ok to me.

trueBlue · Post by **trueBlue** » 28 Jul 2019, 17:50

Did not have any success hiding the camera widget. Guess that the script runs to fast.
Have you tried a scene widget?
Here is a very beginning attempt using the tSBridge.SynchronizeObject(Space.CurrentScene()) command.
Not very useful as of yet but it does work without having a Link Editor open.
So far only one Middle Mouse button gesture.
Move an object and select your Middle Mouse button.
Removed due to update

clintonman · Post by **clintonman** » 28 Jul 2019, 18:53

trueBlue wrote: 28 Jul 2019, 17:50 Did not have any success hiding the camera widget. Guess that the script runs to fast.
Have you tried a scene widget?
Here is a very beginning attempt using the tSBridge.SynchronizeObject(Space.CurrentScene()) command.
Not very useful as of yet but it does work without having a Link Editor open.
So far only one Middle Mouse button gesture.
Move an object and select your Middle Mouse button.

I tried a modified object widget. It didn't work.

trueBlue · Post by **trueBlue** » 28 Jul 2019, 21:12

I got it to work and a Link Editor does not have to be open.
I used the same idea as you Auto Keyframing.
So far I have the Background and Object widgets.
In Workspace using the Eye camera, it updates Model view's object transformation, but not camera transformation.
From Model you have to view from a camera for both transformations.

Do you have a script from your Auto Keyframing project that updates all of the Object widgets?

clintonman · Post by **clintonman** » 29 Jul 2019, 05:03

trueBlue wrote: 28 Jul 2019, 21:12 ...

Do you have a script from your Auto Keyframing project that updates all of the Object widgets?

The code is in the /Scripts/CustomCommands/AutokeyWidgets/ProcessWidgets. It copy's and connects nodes.

trueBlue · Post by **trueBlue** » 29 Jul 2019, 13:11

Thanks, I had already found it, modified it, ran it, and it worked great! Awesome little script there to make a long process super easy!
It worked for Bars and Boxes but did not work for Triangles and Arcs.
To quote you "this is crazy stuff"!!!

Sooo… back to the original Synchronize.RsObj
Sadly does not work unless a Link Editor is open. I created a Synchronize layout that has a minimized Link Editor that works. Workspace animation is in sync with Model too! Includes a RsScn.

File removed due to update.
Found another issue to, if you set the Bridge to off and then run the Synchronize.RsObj, Sync from Model, you will run into the problem that your ProtectWorkspace takes care of. I do notice that your Bridge Synchronize.RsObj/mysendkeys.js might help with the above.
And or maybe incorporate your ProtectWorkspace.RsObj?

Found a Model Animation toolbar:

Code: Select all

tSBridge.CreateTSToolbar('AnimationToolbar','/tSBridge/tSMainWnd',0,0)

Here is the latest.
Removed the set FOV for testing.
Added a View button to the Workspace aspect. Helpful if one switches cameras and it stops working. It runs Activate.

File removed due to update.

clintonman · Post by **clintonman** » 29 Jul 2019, 15:25

trueBlue wrote: 29 Jul 2019, 13:11 ...

Found a Model Animation toolbar:
Code: Select all
tSBridge.CreateTSToolbar('AnimationToolbar','/tSBridge/tSMainWnd',0,0)
...

That's interesting. How did you find that?

trueBlue · Post by **trueBlue** » 29 Jul 2019, 15:37

From YOU

http://clintons3d.com/plugins/truespace ... pTS711.txt

I found some more:

Code: Select all

tSBridge.CreateTSToolbar('LeftBar','/tSBridge/tSMainWnd',0,0)

This one looks to have all of the toolbars that can be loaded.
Also found that they are created from an xml file.
You can find them here:
C:\trueSpace761\tS\Scripts\UI

BTW... here is some notes from a tS developer:

Code: Select all

		//Make sure the Bridge is On	
		
		// Next line is not so necessary, you should use
		// it only if you want be sure all synchronization
		// events are already passed into Modeler.
		// This line is used in this demo, but it is not
		// necessary if bridge is running at its maximum speed.
		tSBridge.FlushSyncEvents();

trueBlue · Post by **trueBlue** » 01 Aug 2019, 15:07

tS71 Synchronize Workspace Bridge

: Capture.PNG (8.64 KiB) Viewed 3867 times

Updates:
Bridge Controls
Workspace animations to Model <- Clinton's - Bridge Synchronize Script
Runs from the Activate and Deactivate buttons
Set the Start and End frames in the Workspace's Animation View and then Render scene to File in Model.
Select Workspace in Animation from the Render to File dialog.

File removed due to update.

clintonman · Post by **clintonman** » 01 Aug 2019, 18:44

trueBlue wrote: 01 Aug 2019, 15:07 tS71 Synchronize Workspace Bridge
Capture.PNG
Updates:
Bridge Controls
Workspace animations to Model <- Clinton's - Bridge Synchronize Script
Runs from the Activate and Deactivate buttons
Set the Start and End frames in the Workspace's Animation View and then Render scene to File in Model.
Select Workspace in Animation from the Render to File dialog.

Couple of questions/comments
The "Set Play Range" is set to run every time the time changes. Should it be hooked up like above instead? Yellow shows original lines removed.
What does the "Activity.KillAll()" do for this?
I think the On/Off Auto should be 3 buttons. There is no way to go directly from Auto to Off like in the desktop bridge dropdown list.
"Only works in this expanded Default aspect Open a Model and Workspace view" - that's not true anymore, is it?

trueBlue · Post by **trueBlue** » 01 Aug 2019, 21:52

clintonman wrote: 01 Aug 2019, 18:44 Couple of questions/comments
The "Set Play Range" is set to run every time the time changes. Should it be hooked up like above instead? Yellow shows original lines removed.

OOPS

That also broke synchronization!!!
Thanks I fixed that and isolated it.

clintonman wrote: 01 Aug 2019, 18:44 What does the "Activity.KillAll()" do for this?

It stops all Activities. I discovered in my Animation panel project where I have a scrubber that moves the Time in the AE, creates an issue in tS7 with the Watch Dog Event. As you can surmise it can run a script many times!
Here is a demo that you can try.
Removed due to update

clintonman wrote: 01 Aug 2019, 18:44 I think the On/Off Auto should be 3 buttons. There is no way to go directly from Auto to Off like in the desktop bridge dropdown list.

Thanks I fixed that.

: Capture2.PNG (7.98 KiB) Viewed 3856 times

clintonman wrote: 01 Aug 2019, 18:44 "Only works in this expanded Default aspect Open a Model and Workspace view" - that's not true anymore, is it?

Nope. You can try it by minimizing the Synchronize.RsObj. Also a Link Editor must be present in your layout.

Here is the update:
Removed due to update

clintonman · Post by **clintonman** » 01 Aug 2019, 22:51

trueBlue wrote: 01 Aug 2019, 21:52 ...
clintonman wrote: 01 Aug 2019, 18:44 "Only works in this expanded Default aspect Open a Model and Workspace view" - that's not true anymore, is it?
Nope. You can try it by minimizing the Synchronize.RsObj. Also a Link Editor must be present in your layout.

Here is the update:

Ah, I misunderstood. I thought it was referring to the Expanded Layout.

trueBlue · Post by **trueBlue** » 02 Aug 2019, 01:57

So Stop Activity, In or Out?
What do you think about incorporating your Workspace Protect script?
I would be really happy

if it was transparent!
Meaning, upon Activate your script runs and upon Deactivate it restores and deletes all of the Workspace Protect nodes.

clintonman · Post by **clintonman** » 02 Aug 2019, 14:47

trueBlue wrote: 02 Aug 2019, 01:57 So Stop Activity, In or Out?
What do you think about incorporating your Workspace Protect script?
I would be really happy if it was transparent!
Meaning, upon Activate your script runs and upon Deactivate it restores and deletes all of the Workspace Protect nodes.

I would say out, until it's needed. There's no benefit and killing script activity could have unforeseen side effects if some other unrelated script is running.
I'll get back to you on the Workspace Protect. I'm almost done with a trueparticles simulation I plan to render with YafaRay, that will need some protection. I need to work out how other scripts can hook into the protection.

trueBlue · Post by **trueBlue** » 02 Aug 2019, 15:53

Thanks I have been testing it this morning.
This setup seems to work.

Capture.PNG: (8.14 KiB) Not downloaded yet

Hey why does the picture not show? Bug in the new update?

Protect - loads the ProtectWorkspace and runs BackupWorkspaceData. It is hooked up to Activate.

Backup - runs RestoreWorkspaceData. It is hooked up to Deactivate.
Restore - runs BackupWorkspaceData.
Delete - removes all of the nodes.
And the (Workspace aspect Deactivate button) removes all of the nodest.

I have mentioned this before, there is an issue with the unofficial light's changes (perhaps other changes) that cause them to not work as before. Like the Enable Shadow.
I wonder how name changes are going to cause issues too, like your workspace layer system?
Seems to me that any and all changes should be restored.
Removed due to update

trueBlue · Post by **trueBlue** » 03 Aug 2019, 16:08

@Clinton
Trying to fix the Shrink Play Range on the Animation Editor.
Can you try this script?
What I noticed when doing this, you can lose the Time line control in the AE.
So I am setting that in the OnOff button.
Removed due to update

clintonman · Post by **clintonman** » 03 Aug 2019, 19:15

trueBlue wrote: 03 Aug 2019, 16:08 @Clinton
Trying to fix the Shrink Play Range on the Animation Editor.
Can you try this script?
What I noticed when doing this, you can lose the Time line control in the AE.
So I am setting that in the OnOff button.

I don't see the problem and the script doesn't seem to do anything. Does the statement "What I noticed when doing this, you can lose the Time line control in the AE." refer to the current Shrink Play Range or this new script button?

trueBlue · Post by **trueBlue** » 03 Aug 2019, 19:33

clintonman wrote: 03 Aug 2019, 19:15 I don't see the problem and the script doesn't seem to do anything. Does the statement "What I noticed when doing this, you can lose the Time line control in the AE." refer to the current Shrink Play Range or this new script button?

Answer: The new script button. The current Shrink Play Range button script is creating errors and problems with the AnimMng. Try it without the try catch error.
Try the new script button with these settings in the AE and AnimPref panel.

You can see what I mean by losing the Time line control in the AE by removing these lines in the button script.

clintonman · Post by **clintonman** » 03 Aug 2019, 20:24

trueBlue wrote: 03 Aug 2019, 19:33
clintonman wrote: 03 Aug 2019, 19:15 I don't see the problem and the script doesn't seem to do anything. Does the statement "What I noticed when doing this, you can lose the Time line control in the AE." refer to the current Shrink Play Range or this new script button?
Answer: The new script button. The current Shrink Play Range button script is creating errors and problems with the AnimMng. Try it without the try catch error.
Try the new script button with these settings in the AE and AnimPref panel.
Capture.PNG

You can see what I mean by losing the Time line control in the AE by removing these lines in the button script.
Capture2.PNG

I don't see the time line control getting lost with the new script. Any specific steps that cause the loss?
The error in the old script disappears if you read and write the node values on different lines.

Original Errors occur:

Code: Select all

RsTime.AnimStart = RsTime.EvalAnimStart('')
RsTime.AnimEnd = RsTime.EvalAnimEnd('')
Node.Value("/Preferences/AnimPref", "PlayRangeStart") = Node.Value("/AnimMng", "AnimStart")
Node.Value("/Preferences/AnimPref", "PlayRangeEnd") = Node.Value("/AnimMng", "AnimEnd")

No Errors:

Code: Select all

RsTime.AnimStart = RsTime.EvalAnimStart('')
RsTime.AnimEnd = RsTime.EvalAnimEnd('')
animStart = Node.Value("/AnimMng", "AnimStart")
Node.Value("/Preferences/AnimPref", "PlayRangeStart") = animStart
animEnd = Node.Value("/AnimMng", "AnimEnd")
Node.Value("/Preferences/AnimPref", "PlayRangeEnd") = animEnd

trueBlue · Post by **trueBlue** » 03 Aug 2019, 21:49

I am having a hard time to duplicate the steps that get the AE in a funk but it has happened to me several times!
When it is messed up, this is what the AnimMng looks like:

: Capture.PNG (4.59 KiB) Viewed 3928 times

I think what you are doing that is different from myself, is I am using the AnimPref's Start and End panel, where as you are using the AE to set the play range?
There is a disconnect using the AnimPref's Start and End attributes and the AnimMng.
Pretty sure when setting the AnimPref's Start and End attributes, and then selecting the original Shrink Play Range button is when problems happen in the AE.
Never the less what is sure, when setting the AnimPref's Start and End attributes, and then selecting the original Shrink Play Range button and your new Shrink Play Range script, it does Not work when you change them on a second attempt. It resorts back to the last settings.

My new script does work from the AnimPref's Start and End attributes. This is what I am trying to fix.

clintonman · Post by **clintonman** » 03 Aug 2019, 22:26

trueBlue wrote: 03 Aug 2019, 21:49 I am having a hard time to duplicate the steps that get the AE in a funk but it has happened to me several times!
When it is messed up, this is what the AnimMng looks like:
Capture.PNG
I think what you are doing that is different from myself, is I am using the AnimPref's Start and End panel, where as you are using the AE to set the play range?
...

That code was only to show how to fix the error message. It should behave the same as the old original script but without the need for try catch. So it was just FYI, so the error condition can be avoided in the future.
I'll see if I can recreate the problem using the info from the image you posted.

Edit. Try this - it's basically the same style of fix I was trying to mention earlier. Not setting Node.Value write to Node.Value read directly

Code: Select all

prs = Node.Value("/Preferences/AnimPref", "PlayRangeStart")
Node.Value("/AnimMng", "AnimStart") = prs
pre = Node.Value("/Preferences/AnimPref", "PlayRangeEnd")
Node.Value("/AnimMng", "AnimEnd") = pre
Node.Value("/AnimMng", "AnimTime") = prs
ScriptObject.RunCmd("graph package/conreset command", "Node", "/AnimMng", "Con", "SelAnimEnd")
ScriptObject.RunCmd("graph package/conreset command", "Node", "/AnimMng", "Con", "SelAnimStart")

clintonman · Post by **clintonman** » 03 Aug 2019, 22:40

I think I found out how it's happening. If you drag the green region so the play range isn't visible and then push the button the timeline control disappears? Is this what you are seeing? outside of the crazy numbers on the node.

trueBlue · Post by **trueBlue** » 03 Aug 2019, 22:45

Yeah!

clintonman · Post by **clintonman** » 03 Aug 2019, 22:50

clintonman wrote: 03 Aug 2019, 22:40 Capture.PNG
I think I found out how it's happening. If you drag the green region so the play range isn't visible and then push the button the timeline control disappears? Is this what you are seeing? outside of the crazy numbers on the node.

Looks like we cross posted.
If the above is true, switching between Dopesheet, Story and FCurve brings the timeline back into line.

trueBlue · Post by **trueBlue** » 03 Aug 2019, 22:56

clintonman wrote: 03 Aug 2019, 22:40 Capture.PNG
I think I found out how it's happening. If you drag the green region so the play range isn't visible and then push the button the timeline control disappears? Is this what you are seeing? outside of the crazy numbers on the node.

Things that happen when the AE is not working:
Loose the AE time line control.
Loose mouse control in the AE and causes problems like mouse dragging on the outside of the selection.
Loose the ability to change the Start and End in the AnimPref panel.
Etc...
Most of the time the only way to fix it is to reset the default context.

clintonman · Post by **clintonman** » 03 Aug 2019, 23:14

trueBlue wrote: 03 Aug 2019, 22:56
clintonman wrote: 03 Aug 2019, 22:40 Capture.PNG
I think I found out how it's happening. If you drag the green region so the play range isn't visible and then push the button the timeline control disappears? Is this what you are seeing? outside of the crazy numbers on the node.
Things that happen when the AE is not working:
Loose the AE time line control.
Loose mouse control in the AE and causes problems like mouse dragging on the outside of the selection.
Loose the ability to change the Start and End in the AnimPref panel.
Etc...
Most of the time the only way to fix it is to reset the default context.

Wow, ok I think you're on your own there. I haven't seen any of those things and I've run out of guesses.

trueBlue · Post by **trueBlue** » 03 Aug 2019, 23:18

Okay I think the problem is the AnimPref's Start and End attributes. I am going to work on those. I think I know their problem.

trueBlue · Post by **trueBlue** » 04 Aug 2019, 01:32

Thought it was the Tab Order. Nope!
It is a limitation of AnmPerf panel in which you can not set a Play Range outside of a set Play Range.
You can set another inside the set Play Range but you can not Expand it.
So my problem was trying to expand it.
The Time line control was getting lost because it was outside the set Play Range.
This is what I am proposing for the panel. The three buttons on the right set the Start and End for the
AniStart = 0 and AnimEnd = 300. The other does both.

Thank you for your help!
Nice to have a Shrink Play Range that does not have hidden errors.

clintonman · Post by **clintonman** » 04 Aug 2019, 03:08

trueBlue wrote: 04 Aug 2019, 01:32 Thought it was the Tab Order. Nope!
It is a limitation of AnmPerf panel in which you can not set a Play Range outside of a set Play Range.
You can set another inside the set Play Range but you can not Expand it.
So my problem was trying to expand it.
The Time line control was getting lost because it was outside the set Play Range.
This is what I am proposing for the panel. The three buttons on the right set the Start and End for the
AniStart = 0 and AnimEnd = 300. The other does both.

Thank you for your help!
Nice to have a Shrink Play Range that does not have hidden errors.

Glad you got it working. As far as the 3 buttons I don't understand but they should be labelled somehow.

clintonman · Post by **clintonman** » 04 Aug 2019, 04:48

: synchronizeRestoreNames.jpg (57.96 KiB) Viewed 3865 times

Changes to the Synchronize and ProtectWorkspace scripts:

Floating Synchronize panel shows the aspect button - still defaults to workspace aspect
New Restore names button on Synchronize default aspect
Move code from the Activate button into the Set Play Range node
Removed all previous protect workspace scripts from Synchronize

Modified ProtectWorkspace so it can be called from other scripts
Added delete nodes to the ProtectWorkspace

After the Synchronize Activate button is pressed, it calls ProtectWorkspace and tells it the next node inside Synchronize to run. So the backup data is created then it continues inside Synchronize normally.
When Synchronize Deactivate is called it calls ProtectWorkspace to restore the nodes.

Modelspace is very aggressive about renaming. If a modelspace view is open, incompatible items will be renamed immediately, preventing the protect workspace script from restoring the names. That's the reason for the Restore names button.

The Clintons3dPlugin has been updated to read a nodes persistent ID number. This stays constant making restoration of names possible. The older method of renaming can fail for example if you already have items in the scene named "Node, 1" and "Node,1" because it would try to rename "Node, 1" to the same name. Now it gives the nodes a semi random name. Node names are only an issue if they have the "comma space number" naming and it is visible to modelspace.

Synchronize workspace aspect: The user must remember to close modelspace views before deactivating, otherwise the node names will not be restored.
Synchronize default aspect: Has a Restore names button to recover if modelspace view is still open during deactivation.

trueBlue · Post by **trueBlue** » 04 Aug 2019, 19:37

Awesome Clinton!
I got an error using the Restore names button.

: Capture.PNG (11.26 KiB) Viewed 3853 times

Question: How does the Restore View check box work? Is user interaction needed or does it run from code?
The Workspace aspect Deactivate button does not remove the Protect nodes, and does not rename the nodes.
I am running ProtectWorkspace from Scripts/CustomCommands.
Here is a New Scene where I have started changing the lights and camera for when you run File/New scene
Changes:
Spot lights have their preferences exported.
Infinite lights have not been modified as I believe that are okay. (?)
Camera has a Watch Dog Event/Synchronize Object. Making it compatible with Synchronization.
Synchronize:
Removed the Mouse attributes from the Default aspect.
Added:

Code: Select all

Node.Delete(Space.CurrentScene() + "/ProtectWorkspace")
Node.Delete(Space.CurrentScene() + "/MatrixBackupData")
Node.Delete(Space.CurrentScene() + "/MiscBackupData")
Node.Delete(Space.CurrentScene() + "/NameBackupData")
Node.Delete(Space.CurrentScene() + "/MaterialsBackup")

to the Workspace aspect Deactivate button.

Is there anything I am missing or need to be changed?

Also please run this scene in tS761B8.4 from the Default layout without any Link Editor open when you first load it.
Not a big deal, it works, but I have to select the sync cam and View from Object in Model.
Thanks again!
Removed due to update

clintonman · Post by **clintonman** » 04 Aug 2019, 20:24

Error and no renames is cause by a bug.

Change Restore Names to:

Code: Select all

function Execute(params)
{

	scene = Space.CurrentScene();
	owner = System.ThisOwner()


	if(Node.Exists(scene + "/ProtectWorkspace"))
		protectWorkspace = scene + "/ProtectWorkspace";
	else
		protectWorkspace = "/Scripts/CustomCommands/ProtectWorkspace";

	if(Node.Exists(owner + "/NameBackupData") && Node.Exists(protectWorkspace)) {

		namesNode = Node.Copy(owner + "/NameBackupData", scene)

		Node.Value(protectWorkspace + "/ReturnFromRestore", "ReturnTo") = "";

		//data not surviving the copy process - copy data manually
		temp = Node.Value(owner + "/NameBackupData", "NodeValues")
		Node.Value(namesNode, "NodeValues") = temp;

	}
}

Change Restore Names Step2 to:

Code: Select all

function Execute(params)
{

	scene = Space.CurrentScene();
	owner = System.ThisOwner();

	if(Node.Exists(scene + "/ProtectWorkspace"))
		protectWorkspace = scene + "/ProtectWorkspace";
	else
		protectWorkspace = "/Scripts/CustomCommands/ProtectWorkspace";

	if(Node.Exists(owner + "/NameBackupData") && Node.Exists(protectWorkspace)) {

		Activity.Run(protectWorkspace + "/restore WS Names");

		//dont delete because modelspace view may be open
		//Node.Delete(owner + "/NameBackupData");
	}
}

Remove the Node.Delete s from the Deactivate buttons, They are deleted inside the ProtectWorkspace script.

The Restore View resets the view to the state before synchronization is activated. Unchecked it maintains the views state on deactivation. User interaction is required to change it's value. Only thing missing is official code to make the default unchecked. So add this to the bottom of RestoreView:

Code: Select all

// ---------------------------------
// Advanced handlers 
// ---------------------------------

function OnDefaultValue(params)
{
	conName = params.Param('conName');
	switch (conName)
	{
		case 'RestoreView':
		// set default value for particular connectors like this, if desired :
		  	params.Param('vtData') = false;
			params.Param('bHandled') = true;
			break;
	}
}

The checkbox for the ui is wrong - change checkbox next to Restore View label to use RestoreView instead of DoDelete.

Actually, after typing all that it's just easier to do a new upload for it, so see below.

Edit: Oops, forgot to remove the mouse stuff like you said above.

Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update

Re: Final trueSpace 7.61 Beta 8 Unofficial Update