Jump to content

Kizza

Member
  • Posts

    994
  • Joined

  • Last visited

Everything posted by Kizza

  1. With this release, I think our move to Archicad is now unstoppable. We're done with manually updating viewports, worksheets and site models, amongst other things.
  2. Archicad 20 Archicad will be finally refreshing it's user interface. Archicad 20
  3. I am wondering if it's possible to modify the technique slightly to create a concrete swale with a concrete texture? Similar to this:
  4. Great Video, thanks for sharing
  5. Yep, Drawing Co-ordination is sloppy in VW. (maybe improved in VW 2016?) I have Auto Drawing Coordination on, mainly for viewport numbering. I also use a worksheet to control sheet information. Problem is, the sheet numbering in the Navigation Pallete doesn't sync with the worksheet numbering and the sheet numbering. What seems to work is to turn off Auto Drawing Coordination and turn back on again and the numbers then seem to sync. Maybe the request should be "please fix auto drawing coordination"
  6. We've looked at the Bootcamp/Parallels option and it's not for us. Two OS's to maintain. We'll probably migrate fully over to Windows 10 shortly. Main reason is we use Microsoft Office extensively and the mac version of Office is not the same.
  7. The way I structure my VW files is as follows: Layer for site Layer/s for each floor Layer/s for roof/s What I want is the ability to apply class/layer visibilities and view type (i.e. top plan, front, back etc) to the layer itself, much like saved views you could say. I also want to apply these visibility combinations to other drawings etc, hence the term "visibility style" and the request for a "visibility style" to be a resource. Then viewports are used to add final touches etc to the drawings. The majority of the graphical heavy lifting is then done in the model views. If I was a Revit user and I received a Revit file it would be WYSIWYG. If I was an Archicad user and I received an Archicad file it would be WYSIWYG. If I'm a VW user, the file would present differently depending on how the file is constructed. For example, if you received one of my files, you would have a set of saved views, someone else would use Viewports extensively and a file from you Zoomer would appear based on your last class and layer visibility selection. Presently, It all seems to be a bit all over the place...
  8. This too sounds positive. I realise VW feature requests will vary according to individual and industry needs, but without the first three we'd still be lagging behind. Top three, first post
  9. Maybe have a look at PathFinder PathFinder
  10. Just looking out for improvements, improvements and hints of improvements. And where things are going. I am usually blunt first thing in the morning without a coffee...
  11. Oh sorry, I thought this thread was about VW development.
  12. So what else is there (other than the new Resource Manager) that will improve productivity for everyday tasks in an architectural workflow? And I don't see the Resource Manager as a new feature, I see it as a fix. The existing resource browser is woeful.
  13. I posted a few years ago requesting a tool that would be able to select a line in any view and change it's attributes. Any rogue lines could be easily made transparent, and you could make lines thicker in elevations to add depth by just clicking on the line.
  14. Yes, changes to Vectorworks are welcome. Changes to be more like Autocad is going backwards though IMO.
  15. Some ideas... 1) Check that the class with the text assigned is set to use on creation 2) Check that any text styles have been assigned to the class (see Jim's post above) 3) Check the attributes default behaviour is set to "by class". see pic attached. 4) Check the organisation palette and see if there is a class in the document with a red fill. Make sure the text object is assigned to the correct class (an obvious one, I know, but if the default for the AP is set by class...) If the above doesn't work then I would try "Remove by class setting" and then reselect "by class setting" in the AP. otherwise I'm not sure..
  16. Nah, leave it as is. I think they have got the layer/class thing right, especially when you consider other disciplines use VW. What I would like to see is: 1) Improved class/layer management as described above i.e. class and layer grouping/presets as a resource 2) Auto classing of evrything. Including all annotation objects, labels, text etc.
  17. Not wanting to go off topic but... Viewport styles is a slightly different concept but viewports can be included. Layer and class visibilitys attachable to a design layer is what I would like to see. At the moment, I work mainly in saved views - saves me having to toggle layers on and off all the time when switching back and forth. If you've worked with Archicad and Revit, you will notice that visibilities are controlled in the design layer. For example, in Revit, view templates are applicable to a floor plan. VW could implement this easily by allowing us to create a preset class layer visibility based on our class/layer structure/standard, naming it, and being able to apply to a design layer, saved view or viewport. and BTW, the equivalent of VW saved views in Revit are mainly used for the camera views and other more specific project views that may be required.
  18. Zoomer's original suggestion I don't think could work in Vectorworks. Why? Because, take for example Archicad and Revit, they both use object attributes (as opposed to class attributes in VW) behind the scenes to control visibilities. If you remove the ability of classes to control attributes, then you will lose control of your graphics. What would improve the useability of VW immensely IMO (listening JimW? :grin:) is to be able to attach a group of preset class/layer visibilities to a design layer, much like a resource. At the moment, I control this via saved views but it seems like another layer of control requiring babysitting.
  19. How about a simple prompt when creating a new class in the mother file: "Do you want this class to be visible in all references?" or something to that effect....
  20. The VW handrail tool is a joke, pure and simple. It baffles me to think that the decision makers at the top have neglected this tool for so long. Quite frankly, it's an insult to expect the industry to use such an inadequate piece of coded junk. :mad:
  21. +1 The current workflow is counter intuitive. Add to the above the ability to edit classes within the referenced viewport directly from the sheet layer and not only from the design layer they are placed in.
  22. No, my experience was not related to layer or sheet imports but resulted from changing the numbering as describe by Col37400 after adding in new viewports (as opposed to copying viewports on sheet layer)
×
×
  • Create New...