Workspace vs Model view

About Truespace Archives

These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.

They are retained here for archive purposes only.

Workspace vs Model view // New Users

1  |  

Post by Fostman // May 9, 2009, 3:48am

Total Posts: 11
What is the difference between them. A lot of things can be done in both views. For me, Workspace is a lot easier to work with. I know, several things, like MotionStudio, can only be done in Model view, but for most thing, do I need Model view?

Post by Jack Edwards // May 9, 2009, 4:47am

Jack Edwards
Total Posts: 4062
Model side is "legacy". It's basically trueSpace 6.6 bolted on as a big plugin to provide backward compatability and the missing features that haven't been ported over to Workspace yet. Workspace side is the new core -- basically it is trueSpace 7.x.

All future development will be for Workspace side and Model side is supposed to go away with 8.0. Another advantage of Workspace over Model side is that Workspace side is very stable, where as model-side tends to crash easily when bad geometry is created.

Post by Fostman // May 9, 2009, 5:14am

Total Posts: 11
"Backward compatability." That make sense. I was wondering why 2 almost the same funtions. I was very confused. Didn´t know in which view to work. So mainly working in Workspace and only switch to Model if needed.

So if I install a new plugin and the plugin shows only in Model view, it doesn´t work in Workspace? So only the results of the changes with a new plugin in Model view are in Workspace and not the plugin itself?

Is Model view the same as the Truespace6 view?

Post by Jack Edwards // May 9, 2009, 2:00pm

Jack Edwards
Total Posts: 4062
Model view includes a few upgrades to trueSpace 6.6, like HDRI, VRay (no longer available) and some other things that I can't remember.

Model view is not completely compatible with Workspace though and it uses something called "the bridge" to transfer the data between the two different programs. So your approach of only using model-side for things you not yet available in Workspace side would be the recommended approach for new users.

Something you can do to increase performance is to turn the bridge off while working in Workspace side, and only turn it on when you need to switch to model side. Make sure to save your work before using model side tools. Also be aware that Workspace Mesh Modifiers (SDS, Mirror Modeler, Morphs, etc.) and Skeletons are not compatible with Modelside and the non-geometry info will be destroyed if the object is edited in model-side.

Another pit fall is that saving in model side does not save the Workspace data. So make sure you save Workspace side projects in Workspace and model-side projects in model side. ;)

Post by mrbones // May 9, 2009, 2:07pm

Total Posts: 1280
One thing that works well is use the model side to pick your material on object. then add a bmp map, browse to the same material and drag it into the bmp window in ME, Adjust the bmp to .5 and then repaint your object, It will automatically create a nice realtime normal map for view in the workspace window.

Not the only thing Ive seen unity between the spaces.

For Instance you can capture morph poses off the speech thing,

And use particles from model to see in workspace.

I woould like to see .swf integration

Cheers is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn