Jump to content

Kizza

Member
 View Profile  See their activity

  • Posts

    994

  • Joined

  • Last visited

 Content Type 

Posts posted by Kizza

    handrail tool

    in Architecture

    Posted

    If I understand correctly:

    Distance between posts is controlled via Upright Spacings.

    But there is no control for distributing a given number of posts within a handrail length.

    Saved Views and Class visibilities

    in General Discussion

    Posted

    Thanks Pat.

    Sometimes I'm a bit sloppy with the none class - it becomes a temporary dumping class.

    Design Layers and Saved Views seems to be an awkward marriage at times.

    Two improvements would tidy things up.

    System Wide auto classing

    Class visibility templates attachable to the design layer.

    Rant over.

    Saved Views and Class visibilities

    in General Discussion

    Posted

    An annoying situation sometimes arises in my workflow with the "None" class when switching between Saved Views and Sheet Layers.

    Suppose I'm working on a Saved View (or on a duplicated saved view) and I've turned off the None class for that saved view. When I switch back to my sheet layers, which contain viewports; unless the active class is the None class, the viewports have disappeared. Obviously, this is because the viewports are in the None class.

    How do others manage this scenario? Am I missing something? Or is the solution simply to class the viewports in their own class e.g. Annotations>Viewports

    As there seems to be no way to "exit" a saved view, I'm thinking that one possible solutuion could involve creating a "Dummy" Saved view which has a set of visibilities applied to it so that a "default" view can returned to.

    My top wishes for 2016

    in Wishlist - Feature and Content Requests

    Posted

    For anyone who cares to listen :)

    1) Live sections (i.e. possible to make adjustments to model in a section view)

    2) Section attributes assignable within a class (or a new "materials" feature)

    The above two are the achilles heel in my workflow.

    3) 3D reference planes or levels, which can be given a vertical height and show in elevations and section views. One way to possibly achieve this - a checkbox next to a storey layer which generates a visual 3D level.

    4) Better stair generation and a useable handrail tool

    5) Ability to attach a class and layer visibility preset to a design layer i.e. WYSIWYG design layers (saved views should be just for uniques views IMO)

    6) Default Hidden Line render mode

    7) Pictorial Window and Door schedules

    8) Windoor or similar tool

    The Marrionette and Subdivision tools are all well and good, but not at the expense of everyday productivity improvements.

    Custom Title Block Blues

    in General Discussion

    Posted

    Is your title block in a class which has text attributes assigned to the class? (i think text attributes assignable to a class is a new feature of 2015?)

    Have you used a new font? TTF are best. OTF fonts are dicey.

    Other than these, I don't know...

    What is wrong with those story levels?!

    in Wishlist - Feature and Content Requests

    Posted

    @Kizza

    Correct. Levels are a feature of the Story/Level/Layer "system".

    -B

    Thanks, not the answer I wanted though.

    What if I don't want/need to use the storey feature?

    Another half-baked feature from Nemetschek.

    This is how it should work:

    levels can be bound to layers (for most situations including alts and adds)

    layers can be bound to storeys (for those requiring multi storey project management)

    Why can't levels work program wide? Who on earth is making these decisions?

    What is wrong with those story levels?!

    in Wishlist - Feature and Content Requests

    Posted · Edited by Kizza

    Good analysis Benson.

    I can see how storeys could benefit a user when working on larger multi-storey projects. The benefit of having layers "linked" together (which essentially is what the storey feature does) comes into play when making adjustments to floor or ceiling heights on those types of projects.

    But I mainly work on small alterations and additions, where I'd rarely go over 2 storey in heights. So storeys aren't that important to me.

    Levels, on the other hand, has my interest. I have VW 2012 so I'm not familiar with the VW level concept within storeys (levels introduced in VW 2015).

    One of the first things I do on a project (like everyone else) is to resolve floor and ceiling heights. I draw a series of horizontal lines on paper, give them an RL, then away I go.

    VW 2015 would give me the ability to create a level and bind objects to them but there is no visual reference to the levels within any of the drawing's views.

    FWIW, I think if Nemetschek gave us the following:

    1) ability to create levels

    2) bind objects to levels and layers

    3) turn desired levels or layers into benchmark elevations viewable in sections and elevations

    4) link layers together

    we would have all the functionality of stories without the storey container.

    Personally, a renovation feature would be of more use to me than the storey feature

    Cannot draw 2D rotated rectangle in 3D view

    in Architecture

    Posted

    OK. When I do cut a section viewport in the Top Plan view it automatically puts in a title block with the generic "Drawing Title." When I go to the Object Info and change it nothing happens. I hit Update. Nothing happens.

    I can't test your file because I have an older version but:

    Your section viewport which is now on a sheet layer can be named either in the OIP or in the Organisation dialogue under Viewports>Drawing Title. Then, when you create a drawing label for your viewport, the drawing label will be populated with the drawing title.

    You can also give the viewport a drawing title by adding a drawing label in the annotation space of the viewport.

×
×
  • Create New...