Jump to content

bjoerka

Member
  • Posts

    453
  • Joined

  • Last visited

Everything posted by bjoerka

  1. you can try to install and run a utility from microsoft called DEVCON this can rescan the usb bus and should bring all devices back if they are lost https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon
  2. you can open the updater and click on advanced options while holding the option key. there is an entry -change version- maybe you can select sp3 manually from there
  3. usually new releases are shared on tuesdays ,-) very very soon means tomorrow??? 😉
  4. but this only works on even days...
  5. maybe this is something that has to do with it. after closing and reopening vw i worked with 2 drawings. mixture of 2d and 3d as long as i worked in wireframe the ram usage raised up to 2.5 to 2.8gb after i switched to opengl it rapidly jumps to 7.4gb changing the visibility of one class for more objects it goes up to 9gb switching back to wireframe does not release any memory... the lid of the macbook is closed. connected display is a lg curved, 3440px by 1440px
  6. i watched this the last hours... as i had opened 8 drawings, vw took nearly 15gb of the available ram. the machine i am working on has got 32gb ram other applications that were running are chrome, mail, rhino. closing 5 of the larger drawings leads down to 9gb. closing the tabs and reorganising took several seconds (nearly about 8-10) in which vw was not responding (spinning wheel)
  7. what i see is that, the more drawings are opened, things get slower the longer you work without restarting vw. after a restart and the same amount of opened drawings, in the beginning it is normal but gets slower the longer you work...
  8. in some cases this helps, in others it does not make any difference. i opened another question regarding different activation times when selecting special object types. here it seems that undocking the oip speeds up this selection and showing the appropriate info in the oip. but - selecting 4800 lines (the result of an hidden line render) takes 18 seconds... in vw2018 it takes 9 seconds in vw2017 it takes a bit more than 1 second.... didn´t test this in sp2. still sp1.1 here... this is more than a dramatic slow down...
  9. you are right... but the machine i am working on right now is a brand new mbp... i really hope that all the speed issues that are discussed here, are adressed to sp3... but please submit a bug report 🙂
  10. as i posted in another topic, vw2019 is quite slow with certain functions. especially sp2 compared to sp1.1 but, as i came across today, it even get´s slow in sp1.1 when you are working with special object types. i did a screen capture while editing a model. the object that is selected was originally drawn as a "extrude along path" object. the graphic representation , which is quite loose, made me think about why that is so. so i did a redraw of that object as a "sweep object" it seems much more accurate, but that is another thing. much more obvious is, that when selecting the "extrude along.." obj. vectorworks takes much more time to display the objects info in OIP. selecting the same geometry, redrawn as "sweep obj", makes the OPI much more faster showing up what has to be displayed. editing the "extrude along path" also takes some time to get up the dialog what object should be edited... editing the "sweep.." is fast responding... in the screen capture the purple curved pipe is the "extrude along..."object, the light green one the sweep object (degree set to 1º) changing the values in the vw preferences (2d and 3d resolution) doesn´t change anything. also the settings of the degree in the "extrude along..." settings don´t change something... also mind the cpu load while the objects are selected. is that a known issue or does this come along with all speed issues known to vw2019? activating_pathextrude_vs_sweep.mov
  11. take a closer look to your activity monitor... i wrote something about it. maybe there is a similar behauvior and you can write somethin about it. regarding this topic the vw team was able to reproduce these things and i think (hope) that with the next service pack the problems will be adressed...
  12. i think today i even did not recall a sheet layer. only working in design layers... quitting an reopening might be a workaround, but these things occur so fast that this is not an option for daily work process. after effects had a similiar problem after opening files in cc18... but only on windows. straight after launching the app grabbed all available memory and didn´t release it...
  13. i guess we have a similar machine in our office. if i´ll find the time tomorrow i´ll drop my designer license onto that... what exactly is a no go? sp1.1 runs better for me than sp2 does
  14. it´s only the internal display the whole day over. undo operations are set to 20
  15. today i looked a bit more into what´s happening on my machine while working with vectorworks. the day over i only worked in vectorworks. it didn´t crash once but therefore my machine got slower and slower. even when i was working on the finder, moving windows, they seemed to get sluggish a closer look to the activity monitor showed that vw uses more than 11gig of memory. at that time there were 5 drawings opened. 3 of them contained 3d models and the views were set to open-gl looking to the processes, while doing nothing in vw, showed a process called "windowserver" running at over 85% of cpu load. constantly. pushing vw to hidden by the system that process drops down. i closed vw and started again without any drawing opened. the process keeps calm. opening a new empty drawing brings it up shortly. when you move your mouse only in the drawing it comes up and gets down. opening 1 drawing, wireframe, brings the process straight to about 45-50%. opening a second drawing (small but open-gl) it jumps to over 80% as long as a part of the vw gui or drawing is visible to the screen. the second thing that i saw is that it seems that vw is allocating more and more memory while you work. whith each drawing that was opened the more memory was allocated. but after closing drawings this memory does not seem to be released. has anybody seen this on his computer too?
  16. I had the same issue. Switch back to version 1.1 That´s not really perfect at all, but the ball of death does not appear that often. To do so - open the Vectorworks Updater, while holding command and option and click on advanced options i think the last entry in the pop-up is called "change version"
  17. sorry. calm down. i am working for several years now with cad and modeling systems and other stuff. no matter if it is adobe cc, word, excel, numbers, form-z, electric image... did you forget the rule that after a new release is born, everybody is a tester? always keep a keen eye on new releases before switching your complete workflow. that´s what i do for over 24 years now! and if you don´t want to be a tester - wait half a year after each release 😉 no matter if it is adobe cc, word, excel, numbers, form-z, electric image, autocad, archicad...
  18. forgot to mention that this is the internal display and the system uses the Radeon chip
  19. yes. as some things are really slowed down i keep that little quartz debugger running to get a feeling if my macbook is going to retire ,-)
  20. i haven´t seen this before while working with multi view panes. zooming and panning is not possible in a controlled way. feels as if something is snapping in the background. this occured after setting a custom working plane and aligning this to my screenplane. check the screenrecording. Redraw-customview_workingplane aligned.mov
  21. Maybe there is another thing that goes along with this issue. I have a file that i wanted to use the purge command with. I forced vw19 to quit after 20 minutes. nothing happend there. exported the file down to vw17 and there the job was done after 2 minutes... inside there is a mess of coincident lines from a dwg import. brought the file size from 138mb down to 53mb 😉
×
×
  • Create New...