Jump to content

Kevin C

  • Posts

  • Joined

  • Last visited


83 Excellent

Personal Information

  • Occupation
    Chartered Architectural Technologist
  • Homepage
  • Location
    United Kingdom

Contact Info

  • Skype

Recent Profile Visitors

1,334 profile views
  1. I was really pleased to see the wall component wrapping in this years release, unfortunately it still has some major implementation issues. The entire wrapping does not work with windows if you have a cill - funny enough, cills are a pretty basic element as the cill completely obscures the wall component wrap in plan view Again with cills, he wrapping does not extend down to include for a cill and leaves odd gaps at the jamb. Not sure if the same situation appears with door thresholds (haven't tried it yet). As an office, we have just started last week to use 2022 in anger, so it will be a while before we are at that level of detail for most projects. Had a look at the changes to stairs - it's a start, but VW is still miles off what the rest of the industry is able to do.
  2. Anyone noticed that the 'Trim' command seems to be broken or is it me??? When trying to trim lines in VW 2022, it doesn't seem to work. See attached screen recording. This has just started happening in VW 2022 - has never happened before. Screen Recording 2021-10-12 at 10.51.40.mov
  3. The offset for windows and doors has now been moved out of window and door settings and into the main OIP. See screenshot below. I think I see why VW has done this, but they have missed a trick. The 'Insertion relative to' tab should be relative to components and not just to 'jamb' Eg. Insertion Relative to "outside face of jamb" attached to 'Inside face of external leaf". This would allow all windows (and doors) to be set out to the correct detailing position irrespective of wall thicknesses etc.
  4. Daft laddie question. I see that there are some additional functions in worksheets - yeahhhh!!. However, there are still a great number of basic mathematical functions that are available in excel that we do not have (or I can't find them). One such situation is trying to get a worksheet to show the pitch of a stair. I can now get the rise and going (which is a good start), but nowhere can I get the pitch displayed. I wasn't that worried as it is a simple inverse tangent function as there is a simple formula: Going = X Rise = Y Pitch = tan-1(x/y) VW has a "Tan" function - but not an "Inverse Tan" function. Or am I missing something. Over 30 years since I did trig at school.
  5. I didn't keep it. Sorry. Every time with that file. It is definitely the 'geo-referencing tab that is causing the crash as the tab is not selectable unless there is site data in the file. This is going to be problematic moving forward as we have to issue co-ordinates for building and plot setting-out etc. and all site engineers require dwg files.
  6. Nina, I have submitted a bug report. The issue is with the 'geo-referencing' tab being selected. VW exports fine if the geo-reference is not enabled, but if it is selected - VW crashes (every time).
  7. Just exported the same file to 2021 and it exported to dwg perfectly - Bug methinks
  8. Anyone having any issues exporting to dwg in 2022? VW is crashing on a standard export profile.
  9. @Tom W. Hi. For items such as insulation / membranes etc. we have removed all of them from the main model as show them at the detail level only. It is just not worth the hassle. The problems with doing things on an annotation layer in a drawing sheet is that if anything changes whatsoever, you have to meticulously go through everything to make sure it still lines up. Too many possibilities for errors and just not worth the risk.
  10. Tom. Yes, that is correct - the roof face is the only item that is created by VW. One of the biggest disappointments in Vectorworks is it's inability to efficiently produce construction level detailing at a scale any higher than 1:50. I had a long discussion with VW support regarding this a couple of years ago, where it was said quite clearly that the software was not designed for that. Yes, in theory I could model an entire project, but the file would be so bloated that I don't think I would be able to run it. Silly things like membranes, insulation and other sundry items all have to be added in as annotations in the sheet layer, so any changes to the model whatsoever means that they all have to be re-drawn. Also, construction level detailing is on a scale of 1:5 or 1:10 (generally) and this is outwith the scope of VW, so why should we change from detailing in 2D (which VW is very quick and efficient at) to a LOD that it 100% reliant on the stability on a piece of software that is known throughout the industry as one of the most unstable architectural design tools in existence. Don't get me wrong, when VW works properly, it is great, but the amount of times on a daily basis I hear through from the drawing office the expletives of "that f*****g Vectorworks has crashed again" - and there are only three in the DO. Vectorworks does not understand anything of the following critical building components for me to trust it to construction level detailing: Windows: There are 2 cills in every window (independent of each other) and everyone knows that, but VW doesn't. There are lintels in every window (sometimes they are combined into a composite steel lintel), but sometimes they are not - again VW has no concept of that There is no way for VW to carry out daylight and opening calculations (it's either one or the other) Could go on - the list is endless Doors: There are industry standard door sizes (especially for external doors) The 'bodging' required to make doors fit into horizontal and vertical coursing means that schedules are generally useless without massive over-rides Roofs: Don't get me started on roofs I could go on, but my response to the original point was regarding the capability of VW to add flashings, valleys, roof detailing etc. to basically 'consent' level drawings - I.e no greater detail than 1:50). VW is currently not capable of creating a model that can be produced efficiently and to a LOD that is suitable for construction without massive 'annotation' overrides etc. I should add that the primary construction method used in our country for nearly all of residential and domestic projects is timber frame. We do have a six storey block of flats and that is an RC frame with SFS infills - again 1:50 level model only with 2D detailing. If I tried to do it any other way, my practice would just not survive as I would not be able to justify (in terms of fees) the time and manpower it would take to model the to LOD required. What I find frustrating in that regard is Please correct me if I am wrong.
  11. I would agree. There needs to be a fully comprehensive review of the roof tool. We have just taken on a commission to produce full working and construction drawings for an architect firm and every time I take on a project, it is a school day. I decided this time that before the 're-worked' plans were issued to the drawing office, that to improve productivity that I would at least try and model as much as I could before the working and construction detail was added. This is the front elevation of one of the housetypes (NOT MY DESIGN) Everything has been modelled with the exception of the annotations and dimensions. One thing I have now found with the roof is to basically throw away anything with the actual roof tool and multiple components, as VW just cannot deal with anything slightly complicated. Simple features like gable ends cause VW to keel over and die - This is basic stuff. This also allows me to create trusses etc. and they will be accurate. On the whole, I am really just using roof faces now, with a single component (usually the concrete roof tile and 20mm thick). This allows me to to be accurate in terms of setting out vertically (something again which VW has never been able to do successfully - A roof is set out from the wall head). I can chose the soffit level, facia level etc. based on extrudes, just wish there was more control over how extrudes and solids are displayed in plan views etc. I can and do have valleys and hips as part of the roof, the ridge-piece above and the gable verge pieces are just a "receptive units" of 3D symbols. Because all of the doors / windows / features etc. are all objects and symbols, they really just have to be placed in the correct position and VW will do the rest. PS only half of the semi was drawn. What would make the process much smoother is the be able to store viewport class and layer settings as styles so that they can be used across projects (also being able to edit the style in a worksheet would be a real bonus, can only dream). On another point. It is disappointing to hear the age old statement 'non-architects'. There are many competent and fully qualified architectural designers / consultants that are more than capable of managing and running projects from conception to completion. As a Chartered Architectural Technologist, one of my practices USP's is that we provide an architectural service from a technical design perspective applied across the whole of the project.
  12. Again having real trouble getting a vgx file to be of any use. See attached link: https://cloud.vectorworks.net/links/11ebc9c8c0ef895a85ba12bd733fbe07/ This is a 55 unit housing development from which I can generate all the static views I need, but with nomad / vgx I am unable to share with my client, as it basically doesn't work. I remember discussions with the VW staff at the Open Day in April and was told that changes are coming - afraid to say, not soon enough. Models simply do not load.
  13. One Drive is pretty good, it's just that you have to do quite a few workarounds to make it work properly with VW. We don't use Project Sharing - Tried to implement a few times over the past two or three years, but found it extremely unreliable and when pairing it with the continual instability of VW, it is just not worth the trouble. Within our NAS server I have synced OneDrive for Business to the Projects folder which means that everyone accesses the projects through project shares on One Drive and it writes back to the server. This seems to work quite well, but it is dependent on everyone's internet connection (still all working from home). The frequency of syncing can be changed to suit; by default on a Synology NAS it is 600 seconds - I have changed it to 60 seconds, which means that file locks etc. are usually pretty well up to date and we haven't had more than a handful of conflicts in total.
  14. I don't believe that the problem is with anything other than VW. It is the only program on my Mac which gobbles up this amount of memory. I am using the current service pack of VW 2021 and the current version of MacOS (Big Sur 11.2.2) - and the problem still exists. It has been going on for years and all VW has ever had to say is that it is the user fault and that we should try and upgrade to the most recent versions. Well we have - and the issue is still there. This is from this morning.
  • Create New...