Final trueSpace 7.61 Beta 8 Unofficial Update

[trueBlue]

I've been looking into the incremental save idea and found this command for saving a scene.
It gets the current scene, then gets the basic name of the scene and finally opens a save scene dialog with the scene name pre-populated.

Code: Select all

	Library2.DlgSaveScene(Node.ShortName(Space.CurrentScene()));

Oh Cool! Let me know how you would like to incorporate it into tS.
Desktop panel, File menu, and or RMB command in the Generate new space button?
Or the way it is now with both options?
One thing I noticed is it is similar to the Insert as Scene, only with a dialog in with which you can change the name.
I would really love to find out how to save as RsObj too!

[clintonman]

I've been looking into the incremental save idea and found this command for saving a scene.
It gets the current scene, then gets the basic name of the scene and finally opens a save scene dialog with the scene name pre-populated.

Code: Select all

	Library2.DlgSaveScene(Node.ShortName(Space.CurrentScene()));

Oh Cool! Let me know how you would like to incorporate it into tS.
Desktop panel, File menu, and or RMB command in the Generate new space button?
Or the way it is now with both options?
One thing I noticed is it is similar to the Insert as Scene, only with a dialog in with which you can change the name.
I would really love to find out how to save as RsObj too!

I think the file menu might be best. I know how you feel about the RsObj save. Would be nice to have both scene and object save.

[Emmanuel]

Regarding the load/save files, I always wondered why .cob and .scn files are not available in Workpsace load/save menu.

In my personal workflow, I use Workspace as a complementary toolset, and I belive I am not the only one here . Workspace is like a big plugin to me.

So,when I want to edit in Workspace a specific mesh only from a Modeler scene, I need to :
- create a new temporary layer,
- move the object I am editing into this layer,
- hide all the other layers,
- cross the Bridge and edit my mesh in Workspace,
- cross back into Modeler,
- unhide the layers,
- move back my object in its original layer,
- delete the temporary layer.
That's pretty time consuming...

You may ask : why moving only one object rather than the whole scene ?
There is plenty of reasons for keeping the rest of the scene in Modeler side rather than crossing the entire scene : saving time when working on big scenes, keep the Workpace display simple and fast, prevent some possible crash, prevent unwanted loss or bugs in animation or material baked in Modeler, that may be broken if they cross the Bridge, etc...

Having a Load/Save .cob file in Workspace side would allow this workflow :
- in Modeler, save an object or a selection of objects as .cob file
- In Workspace (Bridge being turned off), simply load the .cob, edit the mesh, and save it in .cob
- in Modeler, delete the original mesh and re-load it the saved .cob.

TrueBlue, Clinton, Stan, do you think you could add the .cob file format in the import/export dialog box ? Or create a button/menu dedictated to .cob load/saving from Workspace ?

[trueBlue]

Like this?

[Emmanuel]

Yes, it could be like this. The challenge is to make it working when Bridge is turned off...

By the way, it would be a must-have for the Standalone edition.

[trueBlue]

I think the file menu might be best. I know how you feel about the RsObj save. Would be nice to have both scene and object save.

What do you think about having both additions? From the Desktop panel it is simple and faster.
Form the Library there is Export, but those commands are no where to be found.

[clintonman]

...
So,when I want to edit in Workspace a specific mesh only from a Modeler scene, I need to :
- create a new temporary layer,
- move the object I am editing into this layer,
- hide all the other layers,
- cross the Bridge and edit my mesh in Workspace,
- cross back into Modeler,
- unhide the layers,
- move back my object in its original layer,
- delete the temporary layer.
That's pretty time consuming...

...

Would it help if you could make everything invisible except for the selected mesh? I think that can be done with a python script.

[clintonman]

I think the file menu might be best. I know how you feel about the RsObj save. Would be nice to have both scene and object save.

What do you think about having both additions? From the Desktop panel it is simple and faster.
Form the Library there is Export, but those commands are no where to be found.

Sure.

[Emmanuel]

...
So,when I want to edit in Workspace a specific mesh only from a Modeler scene, I need to :
- create a new temporary layer,
- move the object I am editing into this layer,
- hide all the other layers,
- cross the Bridge and edit my mesh in Workspace,
- cross back into Modeler,
- unhide the layers,
- move back my object in its original layer,
- delete the temporary layer.
That's pretty time consuming...

...

Would it help if you could make everything invisible except for the selected mesh? I think that can be done with a python script.

Riccardo's plugin, RSHide, can make all objects invisible except the selected one. It works at first : only the visible mesh is shown in Worspace. But when I'm back in Modeler the plugin generates an error message "Access violation at adress 100B473D in module 'tsxapi.dll'. Read of adress 000000004" and is unable to un-hide the invisible meshes.

[clintonman]

...
So,when I want to edit in Workspace a specific mesh only from a Modeler scene, I need to :
- create a new temporary layer,
- move the object I am editing into this layer,
- hide all the other layers,
- cross the Bridge and edit my mesh in Workspace,
- cross back into Modeler,
- unhide the layers,
- move back my object in its original layer,
- delete the temporary layer.
That's pretty time consuming...

...

Would it help if you could make everything invisible except for the selected mesh? I think that can be done with a python script.

Riccardo's plugin, RSHide, can make all objects invisible except the selected one. It works at first : only the visible mesh is shown in Worspace. But when I'm back in Modeler the plugin generates an error message "Access violation at adress 100B473D in module 'tsxapi.dll'. Read of adress 000000004" and is unable to un-hide the invisible meshes.

I tried a script and it didn't work. The problem is that the change the script makes doesn't make it across the bridge. If you manually make something invisible it will become invisible on the workspace side, but if you do it via script it does not. I've attached the script for anyone interested.