Jump to content

mike m oz

Moderator
  • Posts

    4,689
  • Joined

  • Last visited

Everything posted by mike m oz

  1. This article on the revamp of the Sydney Opera House might be of interest to Spotlight users. The movie showing what they have done includes footage of the ceiling space. The sub linked article 'Concert Hall Transformation' has 23 images of the work that was done over the last two and a half years. https://www.smh.com.au/culture/art-and-design/no-longer-hideous-opera-house-unveils-150m-upgrade-of-concert-space-20220506-p5aj3u.html
  2. The gist of this request appears to be to have 'non plot' like classes, eg. Guides, visible while you are working but not visible when you print. The simple way to get that is to use Sheet Layer Viewports for your output. In those you can make any class you want not appear in your printed output by making it non visible in the Class Properties for the Viewport. the only thing you need to be mindful of is that setting a 'Container Class' of an object to invisible will make the whole object invisible. Non plotting Classes v2021.vwx
  3. Josh, one problem still remains. In any non orthogonal 3D view, including isometric, you can no longer draw a 2D shape to define a Viewport crop for that 3D view on a Sheet Layer. You have to create an overall Sheet Layer Viewport and then crop it on the Sheet Layer.
  4. Valid point as Groups can already contain objects that are on different planes. Having a Group plane option could lead to unintended consequences so probably not desirable.
  5. The issue with Groups is that they can contain 2D, 3D and hybrid objects. That makes it nigh on impossible to have a plane option for Groups. I wonder though whether a plane option for Groups could be added when they only contain 2D Planar objects.
  6. Pete, try this and see if it gives you a way around your problem. Copy the 2D objects you have drawn in say plan view. Switch to an Elevation view and paste them. With the 2D objects still selected change their Plane from 3D to Working Plane on the OIP. I would probably then Group them so you can move them as a single entity to where you want them.
  7. I get a different problem in the March 13, 2021 file. With the Push Pull tool active I can hilight all of both wall faces that can be seen. If I pull on the left visible wall face it moves. Afterwards though I can't hilight the right visible wall face and the left wall remains active even though I have deselected it. I can't prevent the Push Pull tool from hi lighting its various faces and moving them. Very weird. Edit: I'm intrigued as to why you need to Push Pull a whole wall face.
  8. Line-weight, I'm running Vw2022 on an M1 Mac Mini and I don't have any problem selecting any of the faces of the white object in your view.
  9. Landartma, the subtlety with this operation is that once you have drawn the 2D object on the object face you have to start the Push Pull operation while the 2D object is 'red' hilighted and then press the Windows Alt key or Mac Option key. If you press that before you start Pushing or Pulling it won't work. If you pull the 2D shape away from the object you will get a solid addition. If you push the 2D shape into the object you will get a solid subtraction. I find it best to have the auto selection plane on.
  10. I switched to an M1 Mac mini early this year and I haven't had any significant issues.
  11. I'd like a way to lock down docked pallets as well. I regularly accidentally undock the Basic tool palette and I wish there was a way of stopping that happening.
  12. First thing to note is this replaces the old plan view only component wrapping functionality. To enable the new Functionality: Right click on the Door or Window object and and select Plug-in Object Options. Then check mark the Use wall closure option. This will enable the Wall Closure option on the OIP. (Note that there is a Wall Closure Profile Offsets button in this dialog as well.) You will now be able to access the Wall Closure functionality on the OIP. The Wall Closure functionality can be defined by the Object or by the Wall Style. There are separate tabs for Profile and Wrapping. Defining them by the Wall Style is very similar.
  13. Have you checked that your Windows OS version is compatible with Vw 2018? https://www.vectorworks.net/sysreq?version=2018 Also check that you have the latest graphics driver for your graphics card.
  14. I bought a Samsung UHD monitor and it occasionally just goes black for a few seconds. It can also be difficult to wake up after the computer has gone to sleep. Nudges also don't always show immediately. There can be a slight delay.
  15. I'm doing just small to moderate size projects and it is coping well but there isn't a gee wow time improvement in rendering times. For bigger projects I think you are going to need a lot more cores than the current M1 chip has for there to be a substantial improvement in rendering times. Caveat - this is Rosetta and I'm hoping that the M1 coded version of Vw will see an improvement in rendering times.
  16. It needs to be more than a bigger monitor. If you want to future proof yourself it also needs to be a much better chip. The existing M1 chip is good, but you will need more grunt than it has for larger projects.
  17. I've had no problems with Vw 2020 on the Mac mini. Vw 2021 is a bit laggy on OIP maths, drag Wall moves and marquee Wall moves.
  18. Two observations with the M1 Mac mini's graphics: - Google Maps Globe View doesn't work well when zooming in and out. The image takes a surprisingly long time to regenerate in both 2D and 3D. Standard aerial view seems to take a little longer to regenerate as well. - black and white TIF images of drawings imported into Vectorworks briefly reverse themselves when you zoom in. ie. the background becomes black and the linework white. It then reverts.
  19. I have a file that is 284 Mb with Viewport cache on. It has: - 49 Design Layers - 202 Sheet Layes - 188 regular Sheet Layer View Ports - 157 section Sheet Layer Viewports and uses Custom Renderworks rendering. It took just on half an hour to update all of the viewports and did it without a glitch. My iMac would have stalled if I had tried to do that. Activity Monitor showed 1600 - 1650 CPU threads and approximately 400 CPU processes. When Renderworks was working the CPU time hovered around 98%. The system uses just 1.5% of the CPU time. That is Rosetta performance so pretty impressive. I'm looking forward to seeing how it goes once it has Apple native code.
  20. Vectorworks 2021 has now installed and is up and running on my M1. A big thanks to Gunther at Vectorworks Inc. for his helpful advice. I'll post my experiences.
  21. I'm not having any monitor issues. I'm liking most how quickly the applications open, especially Vw.
  22. My 16GB + 1 TB M1 Mac mini finally turned up and I've been using it for two days now: - Vw 2021 won't install (Australian version) and it crashes the computer during the install. I have bug reported that. - Vw 2020 installs and works fine. I'm not doing very complex work at the moment - mostly drafting and some simple modelling. So not particularly taxing for the computer. I did have an issues with some 3D polygons for a DTM repeatedly bringing up the spinning beach ball of death. After I simplified the 3D polygons I didn't have that problem. I checked the more complex 3D polygons on my iMac and had the same spinning beach ball of death behaviour. Some positives are how quickly Vw starts up and quits on the M1. On my iMac with Catalina both are slow. Start up can be excruciatingly slow. The M1 also starts up in a fraction of the time it takes my iMac to start up.
  23. M5d, I'm looking forward to the transition and will report back on my experiences.
  24. Just had an email saying that the ETA is 2-3 weeks. Christmas and New Year shutdowns are likely to blow that timeframe out so I am guessing sometime in January. Early January if I am lucky.
×
×
  • Create New...