Jump to content

elepp

Member
  • Posts

    253
  • Joined

  • Last visited

Everything posted by elepp

  1. Hi, what parameters define the success of generating a 3D model. So far I only managed to generate a model only once. Later we changed the model again and it didn't work. I tried saving the file in a perspective view, but didn't help. The vwx-file is 140 mb big. Maybe @inikolova you can help. Can send you a dm with a link to that file. Best regards, elepp
  2. @ida Glad it helped. AFAIK the tools in the benelux version are developed by the distributor there. As long as Vectorworks Inc. is not seeing a general benefit of that tool, it will not be implemented worldwide. @Christiaan Yes. That is annoying. Wondering if on purpose or just missed to be implemented when they changed the system.
  3. Hi, try =IFC.'Pset_DoorCommon'.'FireRating'. FireRating is a Property of the Pset_DoorCommon, like for Walls Pset_WallCommon.
  4. I wish there would be a short video from VW Inc. abou the different variations. Or a white paper.
  5. Hi! Theoretically it's possible. What exactly do you want to achieve? You can attach IFC data to the group itself or the objects inside.
  6. https://architosh.com/2022/05/the-gift-that-keeps-on-giving-vectorworks-talks-apple-silicon/ What I gather from this interview is to go with the highest amount of RAM possible, because Vectorworks will take all available space. Seeing the issues posted on this forum, it seems that even small files will cause problems though.
  7. Facing the same problem. Would be nice to have.
  8. Hi. You should use the data manager for this. Much easier and flexible. You canfind more info here: https://app-help.vectorworks.net/2022/eng/VW2022_Guide/DataManager/Using_the_Data_Manager.htm
  9. Hi, have you given the parasolid format a try? The geometry of VEctorworks is based on it and rhino can export it. We had some good results with some test files a while ago. The format should be called .xt, i think. Regards!
  10. Hi, Vectorworks does not convert IfcEntities into native objects (yet). It's meant as a reference, similar to a dwg-file. The question is your use case. Do you have to work on the imported architecture or are you only referencing it? If you have to work with the model, the best way would be remodeling it according to the ifc file.
  11. Hi, for a viewer I can recommend bimcollab zoom or the openifcviewer from oda. In general I would say that your clients request for a 3D model is very broad. You have to ask them what their use case is. Do they just want to have a nice rendering or do they want to have a walkthrough model like you could generate with vectorworks service select cloud. Regards!
  12. Thanks @Pat Stanford, @JBenghiat and @MullinRJ for your patient and your explenation. With one specific worksheet it's working now. I will start on the looping now. If I have questions, hope you don't mind me coming back here. 🙂
  13. @JBenghiat Thanks for your kind reply. You mean my code example above will not work? I just noticed that your reply before didn't have the parentheses around the string. I removed them and used single quotes for them. Still it's not updating my worksheet. Somehow I feel like I have a knot in my brain. What am I missing or is the whole script wrong?
  14. That sounds interesting. If I don't have the worksheet on the design layer, I can't see it in the criteria builder. But even if I do that my script is not running, even though I don't get an error message. But I am able to get the Index of the worksheet.
  15. I tried this: import vs def callback(h): vs.RecalculateWS(h) crit = ("N = TAB_WE_H*") vs.ForEachObject(callback, crit) import vs def callback(h): vs.RecalculateWS(h) crit = ("N = TAB_WE_H*") vs.ForEachObject(callback, crit) But it still does not work. I don't get an error message, but it's not updating the worksheets. Regarding the criteria, I was using the criteria builder, though I can't see the worksheet listed under Name. Somehow the worksheets don't have names that you can use.
  16. I tried this: import vs crit = vs.GetName("TAB_WE_H*") def callback(h): vs.RecalculateWS(h) vs.ForEachObject(callback, crit) I does not give me an error message but it's also not working. What am I doing wrong?
  17. I tried this: import vs crit = vs.GetName("TAB_WE_H*") def callback(h): vs.RecalculateWS(h) vs.ForEachObject(callback, crit)
  18. I have a pattern for the worksheets "TAB_WE_H3/0/1". If I can use a wildcard after TAB_WE_H, i could find all the worksheets I need. How would I add the search criteria to the foreachobject line? Thanks for the help!
  19. Thanks for the replys, I see if I can manage to film the jumping pins and send you pm with a download link. Regards!
  20. I am aware of this issue. With the flexible layout implementation, I am sure the way pins are implemented will have to be changed. Today this tool was beyond usable. The pins were jumping around, changing their colors randomly, changing their sizes. I spend most of my day playing wack-a-mole, instead of finishing it quickly. My experience today was more like using a tool in a very very early beta version. That's not cool, Vectorworks! 😠
  21. Another question. How does the 3D Panorama defines it's starting point. I realised that no matter how I am turned in a perspective, the resulting image always looks the same. I thought by rotating in the vectorworks model, I could change the seem at which the panorma is stitched together.
  22. Thanks for your reply. At the moment it's running very buggy for us. The pins are jumping around and resetting themselves. I have to reload the browser regularly 😔 It's costing us a lot of time to make changes. Here is another screenshot of an issue. The line break of our texts happen in weird places. I am not seeing this issue currently. It would be appreciated if you could provide more details around the circumstances under which this is happening. This seems to be a safari issue. It works in Firefox. Another suggestion is: We can change the names of the pins but the names of the files stay the same in the presentation. That's an annoying discrepancy and cause for confusion. Regards!
  23. Hi @inikolova, here is a first round of bugs/ criticism: - The starting camera position should always be adjusable, also in Panoramas that are not part of a tour. I dropped a panorama on a floorplan and can't adjust the view. Now people have to rotate the view first to see where they are. - The layout is very limited. We would like to have more freedom in layouting our presentations. - Occasionaly the pins I create are jumping around when I am trying to adjust them. I have to reload the website or close the browser to get the behaviour back to normal. I am using Safari on Big Sur. - Changing lots of pins is very tedious. We like to indicate different types of images with color codes, but if we change the colors it becomes a very tedious job changing 20 pins. Scaling issues like these happen. If I type this text in the editor I don't see it in the presentation. Somehow the <> lead to the software ignoring the text. Pins that are very low on the presentation become very painful because the settings are disappearing. We have to move them up, adjust them and than move them back. Thanks for reading this. Regards!
  24. Thanks for the first pointers. I will see how far I get and update my progress here. 🙂
×
×
  • Create New...