|
|
Player vs. Modeler
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.
Player vs. Modeler // Roundtable
Post by etrasti // Apr 26, 2006, 6:54am
|
etrasti
Total Posts: 7
|
Can anyone enlighten me as to why certain tools only show up in the player and not the modeler window? For instance, the blender or add a loop tool doesn't show up in the modeler, but they seem like modeling activities to me. It just doesn't make sense to me as far as workflow to have to switch between 2 different windows when doing the same type of tasks. |
Post by TomG // Apr 26, 2006, 7:07am
|
TomG
Total Posts: 3397
|
You'll find this discussed a lot :)
This is because trueSpace7 has a completely different underlying architecture than previous versions. The code is new, the way it handles data is new, all new.
This means that it took a long time to develop, and a lot of the work went into creating this new code. This leaves only a certain amount of time to develop tools within that new architecture. tS tools represent 10 years worth of development, and seeing all those tools under the new architecture overnight is just not possible.
Also, all the old plugins etc will not work under the new architecture at all, and changing them will not just be a minor issue for developers as sometimes it has been in the past (a quick recompile with a few lines of code change).
So in order to keep ALL the functionality people are used to, plus keep all their plug-ins, plus give them something familiar rather than everything strange, trueSpace6.6 runs inside trueSpace7 somewhat like a plugin, to over-simplify but it makes the point.
If you want to use trueSpace6.6, then it is in the Modeler window. If you want to use trueSpace7 (with the new and much improved tools and views etc) you use the Player window. The names modeler and player are not necessarily self-explanatory, we agree :) Again that oversimplifies, but it gets the essence across.
Some tools are only in the Player because they use the new architecture. You can't do them in the Modeler because they are not written for tS6.6 architecture. Some tools are only in the Modeler because they run only under tS6.6 architecture, as it is not possible to have duplicated all functionality in the new architecture.
It is a compromise, of course, but then any solution would be a compromise ("nothing but tS7, so no more plugins that you are used to, and not all the tools you have been using for the last few years" ; "old architecture only, so no future for tS as the old architecture is limited and some of the things users have requested for years are simply not possible, or incredibly hard, under the old architecture" etc)
HTH!
Tom
PS: The "player" is not just for playing that is the biggest problem with the name, though it would be hard to know what to name it; eventually there will be no modeler as everything you could possibly want for modeling will be in the "player" window (ie within the new architecture and not reliant at all on the old). So the name is not the most self-explanatory in the world, we agree.
HTH again :)
Tom |
Post by etrasti // Apr 26, 2006, 7:46am
|
etrasti
Total Posts: 7
|
Thanks Tom....just the answer that I was looking for. Knowing the why's and what's where will make getting used to TS7 a lot easier! Thanks again!
Erik |
Post by Alien // Apr 26, 2006, 9:57am
|
Alien
Total Posts: 1231
|
PS: The "player" is not just for playing that is the biggest problem with the name, though it would be hard to know what to name it; eventually there will be no modeler as everything you could possibly want for modeling will be in the "player" window (ie within the new architecture and not reliant at all on the old). So the name is not the most self-explanatory in the world, we agree.
How about some sort of competition to pick a better name to replace "player"? |
Post by splinters // Apr 26, 2006, 10:05am
|
splinters
Total Posts: 4148
|
How about some sort of competition to pick a better name to replace "player"?
Awful lot of reprinting to do....:confused:
Then again, how about Realtime View, Pre-viz or DXView ;) |
Post by Alien // Apr 26, 2006, 10:16am
|
Alien
Total Posts: 1231
|
Awful lot of reprinting to do....:confused:
When have Caligari ever done an updated print run for a point-release? :confused:
Then again, how about Realtime View, Pre-viz or DXView ;)
I have tried to think of alternatives myself, but... http://homepage.ntlworld.com/alien42/smilies/dunno.gif
Hence the idea of a competition. |
Post by noko // Apr 26, 2006, 11:32am
|
noko
Total Posts: 684
|
I thought the names where well chosen :o, the Player is realtime and interactive with instant gratification :D , while the modeler is, well a place where you model and then have to render to get to the fun part of your creation. As time goes on I like the two being somwhat separate, different but connected, sounds like marriage ;). |
Post by TomG // Apr 26, 2006, 11:51am
|
TomG
Total Posts: 3397
|
In time, the name won't matter so much, as the Player will be come the dominant view, used almost all the time, if not all the time. Then there really wont be a modeler and player any more, it will all just be the one view. Hopefully no-one has a marriage like that ;)
I dont think there is a perfect name - I do think Player can sound a little static, like you can only view things and not change things, which is the one downside, if you think of "dvd player" for instance, just showing pre-made content. And it is much more than that :)
In the end though the name won't matter too much, so long as people understand what each is and what it does.
Thanks!
Tom |
|
