Hierarchies!!!
-
I'm really hoping they don't do anything like this...pretty soon SU will be as complex and unwieldy as a parametric modeler, or Blender. Capability should not be confused with usability.
I'd rather have a straightforward modeler which leaves the complexity to me.
-
This does not make Sketchup more complicated...on the contrary.
What Plot-Paris presents is very logical.It works just like the Windows explorer tree structure.
What's complicated about that? It provides a way to organise your file in a much better way.But I do agree with your wish to have a 'straightforward' modeler.
I just think those things can be complementary... -
@kwistenbiebel said:
This does not make Sketchup more complicated...on the contrary.
What Plot-Paris presents is very logical.It works just like the Windows explorer tree structure.
What's complicated about that? It provides a way to organise your file in a much better way.But I do agree with your wish to have a 'straightforward' modeler.
I just think those things can be complementary...One word: BRL-CAD
-
You are indeed the cynical one. That's 6 words.
-
@plot-paris said:
Nested Components
if you have a big model, with lots of components, you can easily loose your overview over all the objects in the component-editor.
therefore we now have nested components. for example, you create door-, and window-components. then you make the building a component as well - that automatically hides the door-, and window-components in the component editor.Do you think my development of namesets could help in this respect?
I should point out that at this stage floor 5 has only a bathroom (other rooms have been named but not elaborated). Selecting elements displays just the walls, spaces just the products. What is displayed is determined by the way you organise the hierarchy.
What do you think?
Chris
-
@chrisglasier said:
@plot-paris said:
Nested Components
if you have a big model, with lots of components, you can easily loose your overview over all the objects in the component-editor.
therefore we now have nested components. for example, you create door-, and window-components. then you make the building a component as well - that automatically hides the door-, and window-components in the component editor.Do you think my development of namesets could help in this respect?
I should point out that at this stage floor 5 has only a bathroom (other rooms have been named but not elaborated). Selecting elements displays just the walls, spaces just the products. What is displayed is determined by the way you organise the hierarchy.
What do you think?
Chris
What happens if you have an object that bridges typical categories, as in that project I screenshoted above? One exterior wall (a structural steel arch system) is also the roof. At other points the material rotates and becomes something that is almost a floor, or an underside of a floor surface.
This is the sort of situation where most BIM modelers lose value for me.
-
@lewiswadsworth said:
What happens if you have an object that bridges typical categories, as in that project I screenshoted above? One exterior wall (a structural steel arch system) is also the roof. At other points the material rotates and becomes something that is almost a floor, or an underside of a floor surface.
This is the sort of situation where most BIM modelers lose value for me.
Namesets require that you give the same instructions to Sketchup as you would to those responsible for the real thing (both code and work is object oriented). So considerations include: who supplies the products (or model - preferably from the same source), the location in relation to the whole (hierarchy) and setting out dimensions (common). Namesets allows you to crosslink to unique names; the parents of the named component, collection or cluster (ozzie) can be manifold - floor, roof, people scarer, whatever.
Does this make sense?
Chris
-
at first, thank you all very much for your comments (it is a great thing to post something before going to sleep and finding a wonderful discussion about it in the morning
)yes indeed, the blended materials would be a fine thing.
I have to rethink the interface though (when I have got the time). the linked materials should not appear among other materials - that confuses things. they sould be shown directly below the preview thumbnail, thus instantly being identified as linked blend materials...
what you say about the slowdown, kwistenbiebel, is absolutely true. it is already annoying enough sometimes. but for that we have the ultimate formula: SketchUp 7the components window need rethinking too. it has to be as simple as possible. perhaps SketchUp should remember which subcomponents are used more often and auto expand their parent component. others that are not used anymore (for example an oldfhasioned window with glass planes as subcomponents) will stay collapsed...
(@chrisglasier, your namesets may come in very handy when needing a neat workflow from design to production. but I am looking for a completely embedded interface, that does not change much in the way the component editor works. we simply need some means to order the mass of components in large models. if you import a component, you can choose to hide or show it's subcomponents already. however, an optical representation of which subcomponent belongs to which parentcomponent is missing...)however, I am completely satisfied with the way, layer grouping and scene grouping could work (in the above image).
@lewiswadsworth said:
...pretty soon SU will be as complex and unwieldy as a parametric modeler, or Blender. Capability should not be confused with usability.]
I completely understand your fear. that is why I tried to think of a way to implement additional control over different functions by sticking to already known systems (the tree structure as we know it from the outliner; the grouping command for creating these structures, as we already use it in modelling).
there is definietly a lot of rethinking necessary in some places. but thats what this thread is for.
and it already started!
-
@plot-paris said:
Scene Hierarchy
I believe Rick from Smustard is working on something like this; only one level deep though, from what I recall.
@plot-paris said:
Layer Hierarchy
Yup, would like to see something like this as well.
@plot-paris said:
Blended Materials
This is moving into the territory of other commercial texture creation apps, wouldn't mind to see it though, but as already mentioned could tax SU even more performance wise. Here's to hoping that the next version of SU (or one pretty darn soon) will have major performance increases linked to contemporary hardware capabilities (read: SMP support, amongst others).
@plot-paris said:
Nested Components
Yup, would like to see this as well.
-
plot-paris,
thanks for sharing your thougths.... they go in the same directions as my wishes do, though I would not have been able to demonstrate my ideas in such a clear way... implementing the hierarchy suggestions would make much sense and be a great help to manage complex structures in very logical and easy-to-handle way. I would use it each and every day.
Cheers,
Franziska
Advertisement