David Poiron

  • Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About David Poiron

  • Rank

Personal Information

  • Occupation
  • Homepage
  • Location
    Nanaimo, BC
  1. Here is a VW 2018 file and screen shots - pointing up or pointing down - there is no graphic difference. stair_2018.vwx
  2. It it just me or is the point direction pop-up menu of the stair tool broken in 2018?
  3. I would like to see a checkbox in the OIP of a worksheet to turn on or off the database header(s) without having to go into the worksheet.
  4. When using the grid bubble tool and dual dimensions, the brackets are grouped together when the grid bubble is mirrored, instead of being on ether side of the dimension text. See attached. Is anyone else having this issue? It would be nice to have the ability to change the dimension style in the OIP instead of having to create it from scratch every time (unless I am missing something).
  5. We are shifting our workflow into using stories. In past multi-family-residential projects where many units are the same, we've put these units in symbols so that we can make wide scale changes to them. However, when creating a symbol of the units with wall styles bound to story levels, the walls show up as having no height. There is a story aware checkbox in the create symbol dialogue box but I'm unclear to what it really does. Do styled walls work within symbols or do we need a new set of unbounded wall styles? Any tips relating to multiple unit type arrangements using stories would be appreciated.
  6. I've been trying to figure out levels and stories recently and the interface certain hampers this effort. I think there are a lot of issues including the level type button being in the Design Layer tab, and the confusion of layer types and multiple possible level elevations being in a list that you check off. I think the graphic in the current UI is useful as a confirmation, but the entry method is flawed. What Thomas shows above is a good start. To me this is a possible workflow/interface: 1. Define the layer elevations (absolute height) in the deign layer dialogue as normal if desired. 2. Create a list of stories 3. Create a list of levels for each story from a default (user-modifiable) list of level names (without elevations or layer affiliation) 4. In the list of levels assign a relative height of each level to the storey, and then assign an existing layer to each level if appropriate. The layer elevations will then show up and could be modified in the same interface. The absolute levels would then be shown for each level in the UI graphic of the stories. I think this would be better than the mish mash of dialogue boxes we have now.
  7. I have a long narrow roof that I would like to create a centre valley with multiple drains and saddles in between each drain. I can link the first two drains together and create a saddle but when I try to link the second two it gives me an error about 160 degree angle (see attached). Is there a way to do this?
  8. I know this is the convention. However, I would like to have the option to show imperial scales as 1/4" : 1'-0" and still have them use the correct scale of the viewport instead of typing a custom value.
  9. This may seem like a peculiar request, but it would be nice to be able to select "=" or ":" for metric or imperial scales. I like to use ":" when using imperial because scale is still a ratio to me, not an equal.
  10. It would be great if viewports retained the last render time in the OIP so you can see how long it took when you have to leave it do its thing. I saw on a video concerning maxwell that there is a setting to enter a rendering time in that software and it will produce the best quality rendering for it. A plugin for maxwell would be great too - seems to be available for other nemetschek products, just not VW.
  11. I recently changed my workflow on some projects to allow me to use the auto document coordination. I used to setup sheets to show multiple pages at once. With ADC I have to have only have one page per sheet layer for it to reference properly. It would be nice to have a view of individual sheet layers on a larger canvas and still have ADC work.
  12. It seems that when you "enter" a slab object it does not show the context objects like when you enter other similar object types. Not sure if this is a bug or something not implemented or I am doing something wrong. I often have to modify the underlying geometry and snap to surrounding objects.
  13. It would be nice to have some indication that there are objects in the annotations level of a viewport. Maybe this is shown as an icon that can be switched on an off directly on the viewport, or some notice in OIP. Or maybe a dialogue box that alerts you to the objects after you try to delete the viewport if you forget.
  14. I would like to use the clip qube to be the basis for renderings in other than OpenGL. My workaround so far seems to viewport a clip tube view as a section viewport to a design layer and then viewport to a sheet layer and use renderworks on that. however the clipped plane does not poche the objects but makes them hollow. Image shows this.
  15. I figured out the problem. The original objects were not set to show the fill colour by class and so the viewport could not override them.