Jump to content

Kevin C

  • Posts

  • Joined

  • Last visited

Everything posted by Kevin C

  1. Anuyone had failures in updating to SP6? It corrupted our VW and we had to roll back to SP5
  2. It would be useful to be able to combine 'align and scale' in a single command. This would be extremely beneficial when overlaying imported files (images / pdf's etc) onto a model. The current scale is very 'brute force' and only scales up from the centre of an object meaning that even if you exactly what scale to apply, you have to manually reposition and potentially rotate etc. to get the correct overlay. I don't like quotuing old AutoCAd commands - but this has been around for decades, you can select the scale origin and select by distance on a drawing or entered data; it even aligns 2D objects to 3D planes (something the 3D rotate should be able to do).
  3. As a sidenote - we as a practice cannot work in projects that have been imported from earlier versions (2022) and use spaces as the conversion process splits a space into a space and Datatag - making it nearly impossible to work with. Well done VW another 'user improvement' that makes life harder again.
  4. From my simplistic viewpoint, they have taken a tool which was really difficult and not user friendly and just made it 10 times worse. Spaces in VW have always been problematic, they are actually provide very little use, but they are needed. As we have now moved forward onto Datatags and spaces being intrinsically linked, one of my biggest gripes is that I cannot associate a space with it in the Datatag OIP or at least give us an option of changing the way 2D locus are represented on screen so that we can see the!!! There should be a way of selecting the space without having to scowl round the drawing trying to find a 2D locus which, by it's design is nearly impossible to find if there are any objects in the drawing.
  5. Has anyone tried to import a file into 2023 where they have been using spaces? I am testing out 2023 before rolling it out to the office and noticed a potential serious bug. Any file imported into 2023 with spaces (styled or otherwise) splits the space into a Data Tag and a space, however the space itself is no longer editable, although it seems to be locked to the data tag and the data tag itself is all but useless. Have tried with numerous files and all have the problem. Just asking the question before submitting a bug report.
  6. Interesting that no-one from Vectorworks has entered this discussion. It is very telling that VW are always quick to blame the users saying that we are not using the program as it is intended and that items are 'working as designed' and that there is a very good reason why the software is now operating in the way it does. Can someone from VW please step up in and tell us why you have removed the 'none' marker setting ?? Also, I am not a programmer - why should I have to use a code to fix something which was not broken in the first place. This one is almost up there with the debacle of the Title Block borders a few years back. Or do we roll back to SP1 - as everyone knows that SP2 didn't actually work and that all bugs were meant to be sorted in SP3???
  7. I am using Flixo energy for linear thermal modelling (I am on version 7 - think it is now on v8.1)- not cheap, but extremely reliable & robust and most importantly I can calculate in accordance with EN ISO 10211:2007 and BR497. This is the website: https://www.flixo.com For my energy design I use Elmhurst DesignSAP (again a windows only product). I used to use NES Plan Assessor, but they were bought over by Elmhurst a few years ago and so I had to change.
  8. Pat Thanks for your views. As an office, we have been operating Macs as the primary hardware for at least 10 years. However within my standard setup, I have to run Parallels on the iMac due to the fact that Apple is not capable of running all the software that is used in normal day to day business - Energy design and thermal modelling software, something that Apple does not support. All of our business software is licence transferrable - so no cost or issue there. There are very few differences between Windows and Mac OS nowadays - with the vast majority of software completely interchangeable - if anything it is easier to operate on Windows than Mac - Networking / Microsoft Office all run 100% native on Windows and to be honest, a lot of Microsoft Office products have reduced functionality on a Mac, which has irked me for years. As far as hardware replacement is concerned, a 4 to 5 year cycle is acceptable in today's world - Mac's provide support for 5 years with their operating systems - free upgrades etc., but I can see this changing dramatically with the new apple business model that enforces a hardware change in a defined number of years due to the extremely limited user interventions that can be made. On the flip side, Windows has always been the hardware system that is fully user upgradeable and the downside of the OS used to be that Windows used to charge for OS upgrades, but Windows seems to be going the same way as Mac with free OS upgrades, as long as the hardware supports it. I have simply come to the business decision that Macs are simply no longer suitable for purpose in terms of adaptability and flexibility. They are fantastic pieces of hardware, however, that on its own does not justify keeping them. I also don't agree with your statement that Windows users don't upgrade - yes, that used to be the case, but that is no longer the norm. The main software that we use is Vectorworks and Microsoft Office - I am the only one who is certified to use the energy software. There are also very few differences nowadays between the two pieces of software a large proportion of work is done in the cloud. Thanks for your thoughts though on the Mac - that ship has sailed though, I am changing to Windows OS.
  9. Hi all. Been thinking about moving the office from iMac's to PC's for a while now and we have a couple of workstations that are way overdue for replacement and the price of iMac's have been going through the roof - for basically an average computer paired with a fantastic monitor. The spec I am currently looking at is as follows: AMD Ryzen 7 5800X Eight Core CPU (3.8GHz-4.7GHz/36MB CACHE/AM4) 64GB Corsair VENGEANCE DDR4 3000MHz (4 x 16GB) PNY QUADRO RTX A4000 16GB GDDR6, 6144 CUDA CORES - 4 x DP 512GB PCS PCIe M.2 SSD (2200 MB/R, 1500 MB/W) 1TB SEAGATE BARRACUDA SATA-III 3.5" HDD, 6GB/s, 7200RPM, 64MB CACHE Windows 11 Professional 64 Bit - inc. Single Licence Samsung LU32J590UQRXXU 32" 4K UHD Monitor The cost is coming in at under £2,800 (with 3 Year Collect & Return, 3 Year Parts, 3 Year labour - equivalent to AppleCare). The similar spec mac comes in at £4,029 excluding AppleCare, but the Apple Store normally throws it in at nil cost due to my business account. I am not confident that the new iMac due out later this year is going to be more affordable - and it will definitely be less upgradeable, so do I take the plunge now or wait?? Any thoughts??
  10. I think there are more issues than just the stability of SP2 for VW2022. As an office we had to roll back to SP1.1 as there are a fundamental errors in SP2. Most notably you cannot have multiple item attached to some walls. Symbols such sockets / furniture / switches etc... which you could previously snap to walls the face of walls create full wall breaks - irrespective of the setting, meaning ANY project cannot be used in SP2. Until this is resolved we as a business are basically stuck with SP1. We have been using this feature in VW for years - We cannot go back and change every single project and drawing. This was first notified to VW when SP2.0 came out for VW2022 - we are now on SP2.1 When we contacted VW - we were told, they were aware but not a priority and will be fixed in SP3. If this is not a priority - what is? When will SP3 be released.
  11. 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.
  12. 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
  13. 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.
  14. 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.
  15. 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.
  16. 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).
  17. Just exported the same file to 2021 and it exported to dwg perfectly - Bug methinks
  18. Anyone having any issues exporting to dwg in 2022? VW is crashing on a standard export profile.
  19. @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.
  20. 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.
  21. 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.
  22. 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.
  23. 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.
  24. 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...