Jump to content

Asemblance

Member
  • Posts

    211
  • Joined

  • Last visited

Everything posted by Asemblance

  1. We need to be able to model ramps compliant with building regs (UK; but presumably every country has similar reg's / codes). This would be much easier if: Essential: 1. The ramp steepness could be set and dispalyed as a 'gradient' rather than 'rise over run' (i.e. 1:20, 1:12) 2. You could add landings at set distances (building reg's require landings every few metres. i.e. a 1:14 ramp requires a landing every 5m) Nice to have: 3. More options for construction and buildup of ramps; more like stair tool 4. Ideally it would be great to have some smart features that would help you work out the most efficient ramps between two points. But this is more of a nic to have.
  2. Also bump - but from the UK! Think I might start a new thread under feature requests..
  3. Thanks Matt - good to know. We will do some tests our end in vwx 2024 and let you know if we have any difficulties.
  4. Hi All, Setting up a new project file from a new 3D Revit model we have received (from a surveyors firm; we also will have 2d dwgs coming in).. Is there any consensus on which of the below is the best way to set up our proposed plans files yet? Thanks,
  5. Just stumbled across this fairly lively thread from a couple of years back, and wondering if there has been any further development? Is anybody using Nomad regularly, and if so how are you finding it? Wondering if its worth the time and effort experimenting with in 2024..
  6. Hi Jeremy, Thanks for the response - apologies I've only just seen it. The signature I was using was out of date - I've just updated to show the correct specs for my current systems (both suffer from similar problems). Drivers are up to date on both, and between them covering Windows 10/11, and NVidia/AMD GPUs. The same issues and crashes occur on both systems, and were less frequent in 2022 on both machines.
  7. Since installing Vectorworks 2023, I have been suffering significantly more crashes than with 2022. The most common appears to be a result of having multiple files open simoultaneously; presumably the system is running out of Memory. It hangs and becomes unresponsive for about 20 seconds, then Vectorworks simply ceases. No error message, no crash report, just silently disapears. This is typically upon opening a third or fourth file. The files are not huge, and this is on a practicaly brand new high end desktop machine running up to date Windows 11, with 32gb of RAM. Vectorworks SP5 installed (but has been an issue through every service pack so far). Is this a known issue? Why has this only started occurring on vwx2023? Also worth noting; 2023 seems generally less polished than 2022. When first opening the programme, the vectorworks logo in the loarder appears pixelated. The new welcome screen starts in a window which is bigger than my WQHD (2560x 1440) monitor and so is partially off screen (perhaps optimised for 4k only?). In use 2023 also seems slower to redrawn information when moving around, starting pixelatd and then gradually sharpening; slower and less useful for moving around a drawing compared to 2022. The whole experience of 2023 has been pretty disapointing so far. Has anybody else noticed these issues?
  8. It is a new custom workspace set up on a fresh 2023 installation, tried a repair and unfortunately didn't seem to find anything. Thanks for the thoughts though!
  9. After vectorworks has been running for a while, 'Edit Current Workspace' and 'Tools -> Workspaces -> Workspaces' stops working. i.e. I click and nothing happens, no pop-up menu appears. Not only that, but after trying to open the workspaces (after it fails to open), this then appears to stop all menu commands from working. i.e. if I then go and click 'tools -> options -> vectorworks preferences', nothing happens. Restarting vectorworks fixes this issue. I have been unable to work out what exactly triggers this behavior to start, but have noticed it more frequently occurs with more Vectorworks files open at once. This is using the latest version of Vwx 2023 SP4, on Windows 11 build 22621.1413
  10. Wondering if somebody from Vectoworks could give an update on the best GPU to get the most bang for buck in the software. When buying new hardware for our studio, sellers try and push NVidia Quadro cards as they are supposedly more geared towards studio environments. However previous feedback from the Vectoroworks team and subsequent discussions suggest Quadro cards carry no particular benefit for Vwx, and you're best off going for the comparable GeForce card which will give best performance for the price. Is this still the case? Any guidance on where vwx is at now in terms of GPUs - and where its headed in the future? Are there any advantages to the Quadro cards?
  11. Thanks - Both sound like much more sensible approaches than what we are doing currently, will try out and report back!
  12. So nowadays most of our projects use BIM sheet numbering and classes. Which is all good and dandy. But sometimes those long sheet numbers can be a real pain. For a start, you have to use way larger navigation windows, because the first 10 digits or so are generic information common to every sheet. So for instance in this example, the only bit you really need to see is the bit in bold: ABC01-ABC-ZZ-ZZ-DR-A-0001. But often the useful bit is outside the right hand end of the column. This causes more practical problems all along your workflow. The one that has just caused me to jump on here and post this is trying to use Detail Callouts; great tool, but these is no option (that I know of) to shorten the sheet number and hide the generic information. For instance see below; a tiny font has to be used, and the sheet number still sails well outside the boundaries of the symbol. Am I missing some key feature or workaround here? Or does everybody else have this problem on a day to day basis? Recommended solutions; 1. The 'Sheet number' could be adjusted to allow it to be split into multiple portions matching the various BIM title format; so you can select which parts to display at any given time, and the key information can be easily seperated out. 2. Better text wrapping control, so you can more easily fit these long and unwieldy numbers into the default symbols. Let me know your thoughts if you have some good workarounds for the time being!
  13. Hi Vectorworks Team, Can somebody please paint an updated picture of which bits of Vectorworks and Renderworks use how many processor cores these days? It would really help us out with picking hardware specs. I assume most Vectorworks processes are now able to use multiple cores... How many should we be aiming for? Also please let us know any changes in the pipeline that might appear over the next couple of years i.e. enabling more processor threads.. Thanks! A
  14. Yep just found it @markdd thanks! Weirdly in all my years of Vectorworks I've never used the 'details' bit of the organisation - viewports dialogue before
  15. (I immediately just answered my own question - looking in 'Organization - Sheet Layers (Details tab)'. Perhaps this will be of some use to someone trying to do the same thing in the future one day!)
  16. Hi All, In a large project with multiple sheets, and a good hundred or so viewports spread across these sheets - is there a way of navigating to one particular viewport, or of finding out which sheet that viewport lives on? Unfortunately the viewports have not been named so are generally called 'Viewport-1' etc.. no clue as to their location in the file.. What I am specifically trying to achieve; I can see that the visibility for a layer is only turned on in one viewport. I want to find this viewport and review the information shown there, but short of going through each sheet manually is there a quicker way of finding it?? Thanks, A
  17. @Tom W. thanks for your reply - useful to know that ideal offer this. However it still involves a lot of extra steps for very early stage design, where really I would expect generic details which comply with the standards to be pretty much a tickbox exercise on the door symbol itself. i.e. an option for default door symbol of 'Doc M compliant' which then gives you all these items without having to hunt for them or load them in yourself.. Bare in mind we use these in literally every project we do (outside of small scale standard residential projects) so it comes up quite often!
  18. Thanks @zoomer that fits with what I've read elsewhere, I think we'll stick with radeon/ geforce then! It would be great if Vectorworks could issue some official guidance on this, covering futureproofing as well (presumably there are things on the roadmap for Vectorworks that we don't know about which may affect hardware requirements going forwards..)
  19. Any chance of an update to this list and a bit more info, based on the latest hardware/ vwx software combo's? Would also be good to get an idea of.. 1) How the more modern integrated graphics (i.e. from the current gen ryzen 7 and intel core i7 chips) perform in comparison to discreet gpu's as well. 2) Whether quadro's / firepro cards are worth paying extra for, or if better off with run of the mill radeon / geforce cards.
  20. Yes unfortunately how we also have to do things, but it is a pain and results in a lot of uneccessary duplication of viewports. Thus the wishlist!
  21. I also sometimes use the layer referencing method for this exact reason - but generally the viewport referencing method is better. So would like to have this same flexibility.. I've tried with the checkboxes both ticked and unticked, doesn't seem to make a difference to the visibility of classes in referenced viewports; either I'm missing something obvious, or the overrides don't work for this particular scenario! Its quite easy to replicate, simply make a file with a few lines on different classes, then reference into a new file. Create a design layer reference viewport, then create a sheet layer with a viewport containing the referenced viewport. The visibilities of the sheet viewport won't affect the objects in the reference viewport. See screenshots from test file below. I am aiming for the pink line to have disapeared in both boxes, but as you can see it is still present on the right hand box. In order to get it not to display, it has to be turned off in the reference viewport on the design layer. But of course if I am referencing this information in more than one sheet, I may want it turned on in some cases but not others.
  22. Hi All, It is a constant frustration that when using viewports on sheets, which in turn show content from reference viewports in the modelspace/design layer, you cannot override the visiblity of the reference viewport. i.e. I have a section referenced in from another file. The reference viewport displays some information which is useful for my working process (room data tags or levels, say), but I want these turned off on the sheet output. Unless I have missed something, there is no way to override the visibility of classes in the sheet viewport; instead you have to turn off information in the design layer (reference) viewport. P.S. If there is already a way to do this, please someone let me know!
  23. Great to hear! Any chance of a seminar / video on this now that its all operational?
  24. Has there been any development on this in the last couple of vwx releases? Having a similar (although much less severe) version of this issue now and was hoping for a quick fix..
  25. Thanks - when I follow your example seems to work fine! I wonder what I was doing previously then... perhaps I didn't have the first vertex mode selected. I 'll see if i can repeat the issue and follow up if I run into trouble again..
×
×
  • Create New...