Rhino 8 Features for Architects

So lets recapitulate what is there for architects in v8:

-drafting
.minor thing introducing round frames
EDIT. adding line cap styles and linetype scaling

-blocks
.blockmanager change but no change to blocks themselvses, not even matching acapulco plugin capabilities, editting in place is still as bad as always

-modelling
.push and pull is very useful

-else
.snapping to clipped geometry

-bugs and lack of trivial features untackled at all
.cap is oriented to world not cplane
.dimension text when placed outside are too far (very silly indeed due to one BAD formula how the distance is calculated)
.make 2d is total mess most of time (i spend hours of cleaning the outputs)
.text dont have superscript subscript
.text cant have width factor
.no way to batchplot multiple pdfs (i believe this might eventually be in v8 because is see every layout can store print settings, hopefully)
.cant clip linked blocks
.no dimensioning possiblity in layouts besides parallel projection views
.cant intersect meshes and surfaces with the same command

Personally i find this too little for a new major version. It feels rather like a small update. But the worst is reluctance to fix obvious long standing bugs making rhino feel more unreliable.

Whats the opinion about this from arch folks here?

5 Likes

Per object linetype scale is pretty nice for drafting. Also endcap-styles in the linetype options.

Altho dashed/dash-dot linetypes are broken in WIP since forever, the PatternBySegment setting in LineTypeDisplay still does nothing

End cap style is nice but linetype scaling if using layouts should result in good (as defined) linetypes scales all the time. Of course when having multiple vies in model space in different scales then is convenient to set linetype scales accordingly.

Hi Ivan,

Could you maybe ask for this and the responses to be split off into its own thread? This one is specific to the UI and your topic is on functionality. If we spread the jam too thin we lose the flavour…

Regards
Jeremy

1 Like

Unfortunately, I have to agree,

there are some minor things like e.g. layer based clipping but not really something I am really exited about…

E.g. middle mouse popup, which I use quite intensively is pretty messed up right now.

Let´s hope they fix this before they release it…

2 Likes

One happy improvement is that all viewports/layouts/details now have their own local layer visibility toggle, and all share the same global toggle. That’s clean!
There’s even a “New Detail On” column, which hasn’t been mentioned a lot, as it looks.
image
At least now layouts don’t get messed up anymore just by working layers in model space.

Architect features missing? The list is a mile long without VisualArq, and a little shorter with it.

  • Am I the only one that feels the whole system of how geometry is “styled” in a view is… convoluted? It’s based on concepts from the 80ies, and should be redesigned from the ground up. Do we really need a distinction between viewport and print display? ‘Style’ parameters are strewn across display mode, layer panel and object properties, and even after 10 years I sometimes struggle finding the right place to tweak.
    A system of style overrides for views should be there, easy to apply and exchange as a whole. Snapshots get close to this, but they should be a property of any view or layout. Needs some proper UI designing…
  • New section tools are kind of nice (where did the menu vanish to in the latest WIP?), but I don’t like that they target only model space, just like Make2D does. 2D extractions should go someplace else, layout space was my initial suggestion, or even some new kind of 2d space.
  • Scheduling… non-existent, except with plugins or Grasshopper hacks.
  • Blocks cannot contain text that shows the block’s coordinates, do they. Thus no simple spot elevation symbols etc.
  • No dynamic blocks.
  • No dynamic Make2D.
5 Likes

I just looked at this with high expectations, since it would address a HUGE problem we are facing with our layouts on a day to day basis.

However I cannot see the use case of the new “New Detail On” column / switch in the WIP, maybe someone can enlighten me with an example?

For me the problem of existing details being filled up with unwanted new elements can only be addressed by introducing a detail mode wich is:

Show only user selected elements by default and automatically hide all new created elements.

That way we would be able to create a detail, the default state would be (when this mode is activated) that no object at all would be visible. Now the user can add elements with “! _ShowSelectedInDetail” to his liking.
When he continues to draw new elements in his model, their default state for that detail would be “hidden”.

This would ensure that:

a) existing objects that have been selected for a certain layout would still be updated when they are edited.
b) new generated elements would not accidently mess up existing layouts.

As you know, any Detail (or Layout) has a second column of layer visibility toggles, which is local to the Detail.
When you create a NEW Detail, all layers where this
image

is turned off will have their local visibility
image
off per default.

Hi Eugene,

Yes, I (think) I understand what it technically does, however I do not see what problem this is supposed to solve.

Can someone give me a practical example of a real life situation?

My problem is not that a new layout has layers that I do not want to be visible, but rather that all my existing layouts gets contaminated by newly created stuff over time rapidly.

If I open a layout after having spent a day working on other stuff in model space within the file, I have to spent a lot of time to clean up everything again, since all new geometry now is visible on this detail.

IMHO there should be an option that new created elements are invisible in the detail by default. THAT would help the details from becoming corrupt.