|
|
some feature requests for TS 7.6
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.
some feature requests for TS 7.6 // Feature suggestions
Post by GraySho // Jan 20, 2008, 2:26am
|
GraySho
Total Posts: 695
|
I'm repeating myself and perhaps many others here, but simply give WS the functionality of ts6.6 and blow that bridge which is causing so much trouble already (memory usage, crashes, 2 programs to learn etc.). Everyone who needs old plugins has an older version of ts to use them, so no excuses. A simple importer brings in your old files.
One unified interface, one workflow for all renderers and tools and objectives. Don't change proofed workflow to make it look new or different, let users customize their interface and navigation.
How many experienced and good artists are getting tired of repeating the same things over and over again???
On the top of my list:
Booleans
Layers
New material editor with unified interface for all renderers
LSCM (hey, as far as I know this code is free)
Scene editor/tree view a la cinema4d
cameras and lights displayed as wires |
Post by splinters // Jan 20, 2008, 8:51am
|
splinters
Total Posts: 4148
|
I do some work for Caligari and I realise that they are stuck between a rock and a hard place.
They need to add new functionality to keep competitive against other programs and so new features are developed for wS while most of us (me included) are crying out for the 'old' features to be ported over.
The ideal would, of course, be a full feature set running on wS code and a UI that can be set up similar to model with full access to all renderers such as LW, Vray, Dribble and maybe others.
I really feel for them sometimes but we need to use this program after all-some of us for our living. |
Post by Steinie // Jan 20, 2008, 9:32am
|
Steinie
Total Posts: 3667
|
2008 is going to be a very interesting year for Caligari and it's users. With the Bridge gone the Model lovers will have to make a decision what direction they want to go. They might decide to be Legacy users and be happy at that. A few may decide to use two versions of tS to achieve their goal. The last group will move on with the future direction of the application, perhaps nostalgic but allowing the benefits of the new UI take hold. I feel for all three groups since all three still share a common bond, the love of creating 3D using some form trueSpace. A trueSpace 2.0 user gets as much enjoyment from this software as the 8.0 future owner will have.
For Caligari to even survive as a Company the move they made was necessary. They knew full well the gripes we might have. We tend to complain about trueSpace in cycles here. Like a faithful marriage we still love tS at heart, no matter what they look like after so many years.
When I updated from tS4.3 Caligari asked me which version I would want to use next tS6.6 or tS7.0 with the bridge to 6.6?
I want the new stuff I answered knowing it was a WIP. I'm in on the ground floor of some exciting times. I wanted my feet wet now not later. |
Post by Tiles // Jan 20, 2008, 10:10pm
|
Tiles
Total Posts: 1037
|
I have always the feeling that there is a big misunderstanding. Workspace is not finished yet, nor really suited to work with. No matter what you touch you end in a bug or in a not implemented feature.
So what's this decision talking about using a legacy 6.6 or a future 7 architecture? There is no real decision as long as the workspace is not finished. You HAVE to use the old architecture to get work done. Still, after years. And to benefit from the few working Workspace features you have to battle with the Bridge. Which is a nasty beast.
So to repeat myself: my biggest wish is that all the bugs and quirks gets fixed first. Nothing else. First fix the bugs. Then go on with throwing in half finished eye candy buttons without function.
Fix the bugs not only in the not public developer version, but release a bugfix for the Users. And when possible in my lifetime. A year is not really a useful timespan for a bugfix release. That's the timespan to scare users away.
Fix the bugs so that we have at least a few tools working. I haven't found this much tools in workspace that works as thought so far. And there are lots of tools.
And no, i don't talk about the modeler side here. I talk about the workspace side. |
Post by Steinie // Jan 21, 2008, 2:25am
|
Steinie
Total Posts: 3667
|
Tiles, just so we maintain some class please edit your last post please. I don't disagree with anything you said, just the language used. Thanks. |
Post by splinters // Jan 21, 2008, 3:11am
|
splinters
Total Posts: 4148
|
Gotta agree with Steinie Tiles, I see your point and you are right to be frustrated but one of the nice things about this site (that differentiates from many others) is the use of language. Not sure I have ever seen an expletive on these forums that wasn't in this (f***) format. |
Post by Tiles // Jan 21, 2008, 4:08am
|
Tiles
Total Posts: 1037
|
Done :)
(this is for the "Message too short" warning when i just wanted to post the "Done :) ". Does anything here work as thought? Oh my, even the Forum ... :p ) |
Post by Docwolph // Feb 6, 2008, 6:30pm
|
Docwolph
Total Posts: 20
|
1) Cloth simulation.
2) water simlutaion. At least surface water.
3) Subdivide at render
4) "normal" object hierarchy. The current system is awkward and barely works as is. |
|
