Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by line-weight

  1. I use a regular laser measure. Aiming at the target can be a pain, especially when there are things like furniture or foliage in the way. And it's not much good for outdoors measurements on a sunny day. And while it can give me very accurate straight-line measurements it won't give you relative elevation heights. Those always have to worked out after the event. I can see the attraction of the device in the OP. Presumably these types of things are going to become gradually cheaper and more commonplace.
  2. I also think they are quite decent so far. Unfussy and have enough to convey a sense of what the space would be like. The only obvious problem I see is that the multiple downlights are casting sharp-edged shadows, which is quite distracting. If you could adjust those so that they are more diffused, I think that would help a lot.
  3. If you leave it to render multiple viewports, does it gradually eat up all of the 32GB until everything grinds to a halt? I think this question is quite important for anyone considering a new machine - it's clear that VW struggles somewhat with 16GB but the question is whether shelling out for 32 or 64GB solve this memory problem, or just mean that you have a little bit more time before things clog up.
  4. I feel like I've experienced stuff like this - not necessarily with referenced files, but with files converted from a previous Vectorworks version. Somewhere, the height info for things like walls and roofs gets invisibly messed up, and copying&pasting into a different document may or may not produce the right result. Eg
  5. VW just doesn't deal with multiple screens well at all. It's way behind other applications in this regard. Recently I've been using DaVanci resolve a bit (video editing). It has various workspace options that span over two screens. These are robust in the sense that once you choose the setup, it generally stays like that, and the application fully fills each window. And you can put various combinations of docked elements on either monitor. In VW, the second screen is always unreliable. You can't dock palettes there. You can try having various floating palettes (eg the resource manager) but in my experience they often pop back onto the main screen, or get lost when switching between applications, and so on. Floating panes in VW are in my experience more trouble than they are worth. I keep trying to make use of them, and having one on my second monitor, but there are multiple issues with them. This is very frustrating, because if they were stable and reliable, they'd make the drawing process much better. Instead they just cause problems. Floating panes are yet another example of a feature that was introduced, is potentially really useful, but has just enough problems that I end up avoiding them. The various issues with them have been raised but I'm not aware of any these having been addressed since the initial release.
  6. I hardly ever use it on a deign layer - but use it all the time on sheet layers; can be a quick & easy way to export or print just a certain portion of a sheet.
  7. The tool just to the right of the pointer tool in my screenshot. At least in my workspace, it's combined with the pan tool (click and hold to alternate).
  8. Another option could be to move the page area (ie the "printer" bounds) so that it sits over your desired drawing, and then use the "fit to page area" button in the top bar.
  9. So you want to go to a design layer, and view it with a specific pan & zoom location? I would use a saved view for this.
  10. yes, I have similar experiences. It would be interesting to see on a mac with 32GB shared memory, doing exactly the same thing, whether it will be idling at 7.9GB ... or 15.8GB...
  11. The reason I asked what was happening in the Memory section of activity monitor (not CPU) is that a gradual slowdown until a re-start sounds like what I see when there is basically some sort of memory leak, and the memory usage just increases and increases. I see this while rendering viewports, not so much when just navigating in shaded view.
  12. Could I suggest anyone having problems with the VW-TM direct link workflow, post on this thread also https://forum.vectorworks.net/index.php?/topic/88266-direct-link-to-twinmotion-resets-all-my-materials-each-time/page/2/ The direct link to TM was sold to us as a major feature of VW2022. As a reminder here is the promotional video https://www.youtube.com/watch?v=hPPiMY5_2GE But the reality seems to be that it simply doesn't work properly, and it's starting to feel a bit like it's going to be one of those things that's just quietly abandoned. I don't think that's acceptable. It's one of the things that influenced my decision to pay for VW2022, and if it's not sorted by the final SP of 2022 then I think I'm going to start complaining to my distributor because I'm fed up with this kind of thing happening with every release of VW.
  13. What happens to your memory usage in macos Activity Monitor when you are having these problems?
  14. Have a look in macos Activity Monitor while this is happening. Is there very high memory usage?
  15. I'm interested to know what this is based on - I'd put my money on the majority of VW users not managing to use the EAP tool successfully. The documentation for EAP remains incomplete and misleading in VW2022.
  16. These problems of materials resetting are known - it's not just your hardware that's responsible. I see you've already found the thread about this issue On that thread, there is no answer on the question of whether anything is being done about it. Regarding your question about alternatives for rendering - are you doing stills or video? If it's stills, then Renderworks can get you good results. In my experience Redshift (as implemented in VW) is *slower* than Renderworks, but I think it can depend on what exactly you are rendering. If you want to do video (fly-through animations etc) then don't waste time trying to get good results in VW. The animation tools are terrible and largely seem to have been abandoned.
  17. Agree 100%. The reasons you list, are the main ones why I generally don't submit bugs and prefer to raise issues on the forums here. One benefit of raising your problem here, is that you can get some gauge on whether there's any serious interest in getting it sorted. Often it becomes evident that there's not, but then at least you know you should probably give up waiting, or that it's not worth upgrading. When you submit a bug it simply disappears into the void. Actually I keep meaning to start a thread that suggests everyone should boycott the "bug submit" process until it's made more transparent and trackable.
  18. Just came across this, an interesting account of photogrammetry being used by structural engineers http://www.billharveyassociates.com/photogrammetry
  19. Thanks, yes, I'm aware of most of those potential issues. But at some point, however careful you are about not including unnecessary geometry, a file may reach a size that VW struggles with from a memory point of view. And my experience is that it's this threshold that is the bottleneck, rather than what the CPU can deal with. It is exacerbated by what seems to be some kind of memory leak problem - which is what eventually makes a certain file size completely unmanageable.
  20. Is this something we can hope to see the end of, in the next SP release?
  21. How about memory demands though? Because when I have problems it seems to be related to memory, rather than processing power. Most of the time VW barely taxes the processors (which is why these memory issues are frustrating).
  22. I have used similar approaches but really it's a bit of a workaround for the limited capabilities of EAP and I don't think it should have to be this fiddly in 2022. The main problem is that once you have created an assembly like this, it is a bit of a pain to edit it. Firstly, in most cases where you want to edit one of the profiles, you will want to edit it relative to something on another of the profiles - or edit other profiles at the same time. Secondly if you want to edit the path - well, you're going to have to go and edit multiple instances of it, or at best do a "paste in place" into multiple EAPs. Lots of clicks to achieve a simple change. Some of these issues could be solved if it were possible to use a symbol as a path or as a profile. And another thing ... it's not unusual for these kinds of assemblies to have a start and end point that is slightly different for each element (think of a wall with a coping that overhangs a little at each end, for example) and my experience is generally that if you mess with the start point of a "path" post-creation, all sorts of things are liable to go wrong, on top of the fact that the NURBS objects created are often much more awkward to edit than the objects you originally drew to create them.
  23. For me, the problem seems to be related to file size. I have one large file (>1GB) where things get slow enough that it becomes pretty much unusable. Then I have some smaller files (in the region of 100-300MB) where VW2022 seems not to struggle in the same way. It would be interesting to know if others have noticed some kind of file size threshold where things start to go wrong.
  24. The files in which you have issues; were they created in VW2022 or in earlier versions? One thing I have noticed in my own files with similar problems, is that it's worst when I try to view a sheet layer that would have been created in a previous version of VW, and one that I may not have looked at or edited since converting to VW2021 or 2022.
  • Create New...