Jump to content

Search the Community

Showing results for tags 'freezing'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Roadmap
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
    • Forum Feedback
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • ConnectCAD
    • Energos
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
    • Data Tags
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

Calendars

  • Community Calendar
  • Training Calendar
  • Webinars
  • Community Groups

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Occupation


Homepage


Hobbies


Location


Skype

Found 4 results

  1. Hello everyone, I might need to open a proper ticket but thought I might give it a shot here as I'm kinda lost. I just built a new Windows 10 workstation for the studio and I'm having a lot of issues with VWX and, when compared to my personal M1 Max, it gets destroyed. All tests were done using the same file. First, opening the file takes longer on PC and the whole software freezes (without showing it in the title bar, I had to open Task Manager to check that) for more than 2 minutes (it takes roughly 10 seconds on Mac) before switching from a sheet layer to the design layer view. Then if I select the orbit tool and perform an action, for example, it freezes again for another minute before actually moving the camera, then it seems to work just fine orbiting and panning/moving. Also switching between other tools at that point seems to work just as on the Macbook, even though, if I move an object like a lighting instrument or a 3D object it seems it takes longer than the macbook to perform it. Switching between Wireframe, Plan View, Shaded or any other mode causes a lot of lag that is not present on Mac. Publishing the same sheets takes roughly 15-16 minutes on Mac and 22 on PC, starting from the same out of date viewports. Finally, closing the software on PC causes it to freeze again and takes about 2-3 minutes to close completely. The VWX install was made today right after the build and the installation of a fresh copy of Windows 10 Pro, run all the updates and installed all the drivers. The system doesn't appear to have any stability issues as benchmarks came clear and runs good with anything else. Specs of the system as follows: Motherboard: Asus TUF GAMING B760M-PLUS WIFI CPU: Intel Core i9-13900K (not overclocked) RAM: 64 GB DDR5 @ 6000MHz GPU: Nvidia GeForce RTX 4090 Founders Edition (not overclocked) OS: Windows 10 Pro (Build 19045.3086) Software: Vectorworks Spotlight 2023 SP5 - Build: 702742 What I was able to notice is that Vectorworks never used more than 20% of my CPU at any time during any of these operations. Also, this list is not comprehensive as I didn't have to inspect the issue any further today and I'm writing from home right now but hopefully this is enough information to start investigate into this as I was really caught by surprise by the really underwhelming performance of this system that I was expecting to upgrade our workflow. Thanks for your time
  2. Hi, Newbie here; I am currently trying to export a render of my work as an image file - however whenever I choose the settings and then save, it works for a little while (with the timer counting for a while) and then Vectorworks goes into 'not responding' mode. This has happened every time that I've tried to export. At the risk of losing work I have just left it, and after about 5 hours it unfreezes and the image saves; but surely this is not necessary!! I am exporting at around a 4000x2000 px size, and have tried down to 75dpi (where it has still frozen.) Is there a way to fix this? Thanks
  3. Hi I'm experiencing many problems with vectorworks, it keeps freezing and crashing when ever I open a file. it takes a long time to move line work and the rendering is not working either, it takes too long and produce pixelated images with missing information. What should I do? I never experienced these problems when I used vectorworks 2013! Kind regards BAne
  4. I upgraded to 2017 and have enjoyed some of the new features but having problems with bugs. Because of 2017 freezing or crashing, I am running both 2016 and 2017. When I try to copy items from 2016 into 2017 they show up as a flat pdf. Is this something new and is there a way around this? Thought it was strange that when copying items from 2016 to 2017 they flatten into a pdf. Also, I am having problems in 2017 where items are disappearing and random center lines and grids are showing up over top of items. I have attache 2 images below. They are from the same diagram and items will just turn off and disappear. If I zoom in or make any changes the items are still missing. I am working on a mac and if I change views to top view, the items show up for a second and then go away. Only way I have found to work around is to change to orthogonal then back to 2d and it seems to work for a bit. Really hope the bugs get worked out quickly so I can work in just 2017 without worrying about freezing, crashing, or items disappearing! gone.pdf Back.pdf
×
×
  • Create New...