Jump to content

bjoerka

Member
  • Posts

    258
  • Joined

  • Last visited

Everything posted by bjoerka

  1. hm - i have build 622317 - and there it doesn´t crash anymore. this is sp2 of vectorworks 2022 in vectorworks 2021 - sp5 - it still crashes immediately
  2. i think it was exactly what you mentioned. but i shut down vectorworks an saw the memory cleaned up again. but i haven´t tested this inn the last weeks with the sp1 and sp1.1 update. 2022 is still too slow in many operations than it´s worth to work with it seriously...
  3. i posted something similar to this issue i still wonder which renderengine is the more realistic one compared to the IES data...
  4. I´ll bring this up again... Bug still present in SP1 of Vectorworks 2022 Why doesn´t anybody from the VW team react to such an easy to replicate bug?
  5. but this seems to be related to windows, or more specific to special system versions i tested the file on my macbookpro, os 11.6, and there are no issues with that...
  6. maybe that´s something regarding vw not to release the vram of gpu´s actually. i have posted something similar i have come over when using redshift as renderstyle.
  7. hm. after asking is there something downloaded? did you check if your resource folder has got full rw access? otherwise - what happens if you place the original folderstructure again there without any content?
  8. did you move or copy the library to the external ssd? when you moved it, did you try to place an alias to the workgroup folder to point there? maybe vw isn´t able to recognize that the original place is moved somewhere else...
  9. guess it´s only you. i have 2020, 21 and 22 installed and the resources update frequently but not at every start of vw. did you try to move one of your folders inside users-library-application support and then restart vw? maybe it depends to that or some broken prefs... there are also deeper prefs kept in root-library-preferences-vectorworksxxxx.plist delete this and try again. that solved some issues we had with some other phenomenons.
  10. and sad to mention that this bug is still available in vw2022...
  11. It seems to me, that Redshift is not releasing the gpu memory after finishing a render. As a result textures are not rendered. An advantage, compared to other apps, it uses multiple gpu´s 😉 Both Radeon RX are external GPU´s. See the two screenshots.
  12. I have attached a custom database, that uses pop-up entries to define special needs for BIM workflow. When i attach the database to an IFCProxy as a custom pset, the pop-up fields do not appear anymore. They are normal textfields. Something i am doing wrong or a known issue? See the screenshots. The first one is the edit window in the database itself. The second when it´s selected in the OIP to edit the IFC entries.
  13. Hi Dave, i have attached the file to my post. thx for having a look. IES_in_VW_bjoerka_v2022.zip
  14. i got a code inside the serviceselect portal. but that is worth for 6 month... not perpetual
  15. It seems that the progress bar is not working correct. During the first denoising phase the progress bar works During the second denoising phase too. But at the end the progress bar turns black again and the rendering continues until the final result without showing a progress bar.
  16. I have experienced that some ies files show up completely different in Redshift in comparison to Custom Renderworks. Is that a known problem? See the attached renderings.
  17. this is correct. but the error appears when you open a document prior to vw2022. vw doesn´t recognize that in the older document unified view wasn´t enabled. it´s a workaround but no solution...
  18. the last years it was the second week in september 🙂
  19. this happens to me in vw2021 sp4 open a blank document insert a light deselect the light in the drawing right click the light in the visualization panel and choose edit pull the slider for brightness click the "ok" or "cancel" button vw crashes every time can someone confirm this?
  20. i have had the same rendering problems in vw21, no matter what servicepack. in vw20 this works fine. also the problems with autoconnections are a part of vw21. for me that too worked better in vw20... can you switch back to vw20?
  21. i experienced more crashes on my macbook pro with sp2 than sp1. so i went back to sp2. but yes, vw2021 is actually more unstable than vw2020 ever was.
  22. right, that works too. but i often had problems with the settings for the crease angle and sometimes geometry was double sided. that´s why i use 3ds 😉
  23. all models that we do in rhino are surface only, like pat mentioned. the only format that worked for me is to export as 3ds. then in vectorworks you´ll get a polygon model as mesh. when you do boolean operations the substracted faces appear as volume.
×
×
  • Create New...