Vlado

This will be fixed in Vectorworks 2023 SP8 The technical description is that the Laubwerk library that we use was fixed and included in Vectorworks 2024 and thoroughly tested a while back. However due to the severity of the problem, we will include it in Vectorworks 2023 SP8. We're spending extra effort to make sure it will be stable in 2023 too.

@aage.langedrag this is actually a known wish and it is at the top of our list to add as a feature. I'n not sure which version just yet, but it's next. Stay tuned.

@Amanda McDermott @RonMan We've tracked down the slowness to the resource libraries load. It's not really plugin related, it's the loading of the resources DB. @Dubman can you delete your user folder, make sure you save you old one so you don't lose something important? Do you see the delay again? If so, please send me the user log files (the VW User Log.txt and VW User Log Sent.txt -- let me know if you cannot find them) @Hugues see the post above.

@Amanda McDermott I've been working with @RonMan to track it down, but it doesn't look that it's the Debug Module. Are you willing to help me test this too? Please send me an email to vstanev@vectorworks.net so we have a way for direct communication.

@ericjhberg this is pretty cool, thank you for the analysis of the problem. It is definitely a problem we need solved soon. It looks to me that, as suggested, we need a new feature or two. Let me consult internally, and I'll contact your.

@RonMan do you mind contacting me directly at vstanev@vectorworks.net? I would like to get to the bottom of this as soon as possible. Thank you.

@RonMan do you mind trying to delete the file /tmp/DebugModule_5.txt from your machine, and try running again with the Debut Module in? You can go there by opening a finder window, then from the menu Go -> Go to Folder..., then type /tmp, the folder will open and there should be a file DebugModule_5.txt. Is there? If yes, delete it and try again. Close Vectorworks and run it again. This file is used to cash flags and optimize the DebugModule, so it doesn't do extra work on startup. So you'll see it show up, and then it should be faster, if that's the reason. Note, please don't rely on the Splash screen, it's not necessarily synced to what's actually happening. The real test is to remove the DebugModule plugin from the Plugins folder, and see it becoming faster. Thank you for you testing!

@Letti R we have nowadays the Partner Install feature, that allows users to install/add on features developed by third-parties. Send me an email to vstanev@vectorworks.net and I'll forward it to the correct people for that.

Hi @Timothy Besada, this is an interesting question, but at the moment we do not provide anything for the Python Scripting that can work with the Web Palette. Only the SDK is capable to provide a web-palette. You can find an example how to make such palette here: https://github.com/VectorworksDeveloper/SDKExamples (this is self contained project, so you should be able to compile it directly) The base of the web-palette implementation is the two sides: - back-end -- which is essentially the C++ plugin. It is the browser, it can add JavaScript code, a.k.a. insert JS functions for the webpages to use, and also to implement JS functions. This way, the page [the front-end] can call into Vectorworks and get data. - front-end -- this can be an external site, or locally implemented [as the example shows, using VueJS]. This would use the JS functions provided by the back-end. Python cannot participate in this at the moment. I guess you can simulate by exposing Script functions [IExtensionVSFunctions] in your back-end, and thus delegate a JS implementation, but I think that would not be very efficient, plus you'll need to store state somewhere, between the calls in Python. I would not recommend going down this way. Unfortunately, the SDK is your only way to do your own web-palette. Regards, Vlado

@RonMan I'm trying to reproduce this this, but I don't even see the DebugModule show up when loading, let alone be slow to load. For me it's only Cineware that takes a couple of seconds. Do you still see this? Have you tried what Dave said, run it couple of times and quit it. Does the load speed change?

The DebugModule plugin is a set of tools for third-party development. It has no effect on the features of the application. Vectorworks would work ok without it, unless you want to enable the dev features, from the Partner Install menu. I would rather get to the bottom of why this is a problem, than to advise everyone to delete it. We'll look at what's going on with this.

@MarcusBIMBOT this looks like you are using the examples provided with the SDK. Unfortunately, those are not in good shape. Use the Github examples, there are in much better state. Go to https://github.com/VectorworksDeveloper/SDKExamples Download the entire repo, it is self contained, already setup to compile directly. Then try to compile the project: SDKExamples\Examples\ObjectExample\ObjectExample2023.sln We use Visual Studio 2017 for that version, but I guess the build tools are what you need. It should just compile. Let me know if you struggle, I'll be glad to help you. Sent me an email at: vstanev@vectorworks.net Regards, Vlado

Hi @MarcusBIMBOT, which project from the examples are you trying to build? The depot is setup so you take the entire thing, and open the appropriate solution file for the version you want to use.

Hey @Pat Stanford, @J P, and all, The root of the problem is that the available object variables are only for styles, and in this case you just have a wall. So, the way you get out data from the wall [nowadays] is via QTO functions, in this case it's =ObjectData('fire rating') Here is the modified script that executes the QTO function on the wall in the script: Note: you must do it via a string variable, for EvalStr to work property. It cannot work with direct string as parameter Procedure WallFireRatingForDoor; {August 8, 2023} {February 25,2022} {©2023, 2022 Patrick Stanford pat@coviana.com} {Licensed under the GNU Lesser General Public License} {No warranty expressed or implied. Use at your own risk} {Test before useing on real data} VAR H1, H2 :Handle; R1 :Real; B1 :Boolean; S1, EXP :String; BEGIN H1:=WSScript_GetObject; H2:=GetParent(H1); If GetType(H2)<>68 then WSScript_SetResStr('---') Else BEGIN EXP := 'ObjectData(''fire rating'')'; S1:=EvalStr(H2, EXP); {Execute the Worksheet formula expression on the given handle} WSScript_SetResStr(S1); End; End; Run(WallFireRatingForDoor);

Hi @loic.jourdan, yes 4 years later, we haven't fixed it, But this time we have an active task in R&D under development to address this.