K.Lalkovski
Vectorworks, Inc Employee-
Posts
116 -
Joined
-
Last visited
Reputation
42 GreatPersonal Information
-
Location
Bulgaria
Contact Info
-
Skype
k.lalkovski
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Marionette Plug-in Style parameters by instance
K.Lalkovski replied to Niels Timmer's topic in Marionette
Hi @heavy manners, We implemented Plug-in styles for Marionette Objects 2 years ago. And setting all the Marionette object parameters by instance was by design.This is how it works at the moment. My suggestion is just create a wish in our Jira so that we can consider supporting the parameters by style as well. As for your second question about the mystery - "However, the script itself is set by style and can be edited to affect all instances that use the style." Please, look at the attached video. As can be seen, regardless of the fact that the individual circles have different radiuses, manually changed through the OIP for each instance of the style, if we edit the network in the red symbol in RM and add additional functionality, in this case, extrude, after finishing the marionette network editing in the Resource Manager (the red symbol), all circles will become cylindrical extrudes, and their radius will be the same, equal to the parameter value seen in the dialog with the button E dit script. That is, all instances will change after editing the marionette network in the Marionette Object style and will be aligned to the parameter values of the Marionette network in the red symbol in the Resource Manager. The idea is, taking your door example into consideration - if you want, for instance, to add a handle to the doors, you add to the marionette network in the red symbol new nodes that create it, and all instances will have a handle after editing the network of the plug-in style. Regards, Konstantin 2024-06-14 16-00-35.mkv -
Module 'certifi' not found on VW2023 / Windows 10 Pro OS
K.Lalkovski replied to Paolo's topic in Python Scripting
Hi @Paolo, I saw you have already found a solution, but here is an example on Windows that finds package certifi. Just open vwx file and run find certifi node. The problem with the module not being found is that certifi for VW2023(Win) is not a direct descendant of the 'site-packages' folder and just the path to certifi needs to be added at runtime. testcertifipresence.vwx -
Marionette Plug-in Style parameters by instance
K.Lalkovski replied to Niels Timmer's topic in Marionette
Thank you! -
Marionette Plug-in Style parameters by instance
K.Lalkovski replied to Niels Timmer's topic in Marionette
Hi Niels Timmer, Could you please attach here the object you have created in order for us to look into it? Thanks, Konstantin -
NBS Chorus Plug-in for Vectorworks link to nowhere
K.Lalkovski replied to Christiaan's question in Troubleshooting
Hi @_James Yes, NBS Chorus plug-in works for 2023.Please, see attached video on how to install the plug-in with VW 2023. Regards Konstantin How to install NBS Chorus.mp4 -
2021 Import Errors for External Python Packages
K.Lalkovski replied to tbexon's topic in Python Scripting
Hi TBexon, I do not know if you have found the solution for your issue or still interested in running PyOpenSSL with Vectorworks, but on Friday I started looking at this problem while resolving a bug from Dominique about the serch path. The DLL that pyOpenSSL looks for is python3.dll.It is in python's folder where also python.exe resides. This path is included in the python search paths in VW. For some reason the code of pyOpenSSL when installed cannot find python3.dll.It's package's code search problem. If you copy python3.dll from python's folder to VW application folder(where VW exe resides) you will be able to use pyOpenSSl. -
Hi @Paolo, There are two approaches to resolve the problem: First approach: Replace VW2022 SP1(619242) with the new VW 2022 SP2(622317) . Second, if you prefer to deal with the existing VW2022 SP1(619242) Please, find the attached file scripts.zip. On the problematic PC: 1. Go to <VW App folder>\Python39\Scripts 2.Delete the contents of this folder. 3.Unzip the contents of the scripts.zip file 4.Run VW and try to install PIL. You should be able to install the Pillow package and any other package. Let me know if this works for you! Scripts.zip
-
Hi @Paolo, Please, take a look at the attached video. What is the number of the Autobuild 2022 you are testing on windows? Give me also details of your system configuration(windows version, processor). The warning on Mac will be removed in 2022 SP3. Could you prepare a video file for me to see what exactly happens on your machine? Pillow Install.mp4
-
EvalStr in VW2022 returning different results
K.Lalkovski replied to tbexon's topic in Python Scripting
Hi TBexon, if you run this on 2022 it is going to work(returns true): localized_True_Bool = vs.EvalStr(vs.Handle(0), "1=1") # Gets Localised True Bool vs.AlrtDialog(str(localized_True_Bool))/*I removed type() here*/ Regards, Konstantin -
EvalStr in VW2022 returning different results
K.Lalkovski replied to tbexon's topic in Python Scripting
-
@tbexon I asked my colleagues @Yasen Aleksiev to look into this and answer you.
-
2021 Import Errors for External Python Packages
K.Lalkovski replied to tbexon's topic in Python Scripting
@tbexon Where do you receive this behavior om Mac OS or Windows?