[Docs Missing for Dialog creation for Plug-In Development]

Note, there are several repos depending on the development you do:

• https://github.com/Vectorworks/developer-scripting
• https://github.com/Vectorworks/developer-sdk
• https://github.com/Vectorworks/developer-worksheets
• https://github.com/Vectorworks/developer-content

Additionally, good examples can be found here (note, those are contained examples, the SDK is also included):

https://github.com/VectorworksDeveloper/SDKExamples

[iPadOS support… please 🙇🏽‍♂️]

@Jeff Prince yes, this is exactly to the point. Combined with @PenChiselCamera point on being able to start a project it would provide a great tool.
This is high on our list for the cloud/Nomad improvements.

[iPadOS support… please 🙇🏽‍♂️]

@PenChiselCamera Thank you for your reply, I appreciate the details.
In fact, this matches to what we're trying to do, and the direction we're working at the moment.

Have you seen the "Share Document" feature in Vectorworks 2025? This is our first step to allow users to share the drawing with other people with the purposes of measuring and review, with comments you can see back in Vectorworks. It's a first step, but we are moving in this direction.
https://app-help.vectorworks.net/2025/eng/VW2025_Guide/Export/Sharing_documents_in_the_cloud_document_reviewer.htm

 

 

[iPadOS support… please 🙇🏽‍♂️]

10 hours ago, PenChiselCamera said:

The Nomad app is less than worthless. We need native file support and interoperability with VW on MacOS.

 Hello @PenChiselCamera, we're focused on visualizing the drawing on the mobile at the moment.

I'm interested to know why you thing Nomad is "less then worthless"? Can you please elaborate?

 

Thank you

[Cloud Document Reviewer - Swipe / arrow through pages]

Hi @bcd,

 

The goal of this viewer is to allow you to navigate the sheet around, zoom, pan, etc. Swiping to change sheet is more PDF viewer-like, and it is in conflict with navigating around a sheet. There is a Navigation-like palette on the side, which you can make taller and have a convenient Layer list to navigate easier.

 

Regards,

Vlado

[Cloud Document Reviewer - Option to hide most of the OIP Shape information]

Hi @bcd, thank you for your input.

The goal is to replicate Vectorworks so we've chosen similar user interface and naming. Then we display information from Vectorworks about this object, and depending on the case you might need something or not. There are currently options to control what data gets exported at record format granularity.

 

Regards,

Vlado

[Missing Features in the Irrigation Settings]

Oh wow, it looks like a general UI bug in Vectorworks. When a tab control is inside a tab control, it doesn't show the tabs. And it's windows only issue it looks. And this is also affecting other dialogs, when there is such tab inside tab condition. Even though I cannot thing of one right now.

 

But the tabs are still there, only collapsed to a line. and you can change them by clicking. Just click around in the space where they are supposed to be (see attached image) and you'll see the controls change. We haven't removed anything.

 

Note, there are 3 tabs, the first two have similar controls, and the third one is different. Which makes it hard to notice when the first and second change. So look for the values, "Default Trench Depth" is different by default. I'll include an image where they are visible for reference

I'm sorry for all the inconvenience. We'll fix it in the next update.

 

 

 

[Help with georeferenced point file importing where it should be]

... scaling problems are typically due to incorrect coordinate system, but the WKT looks the same.

Maybe you can getting more points and plotting them in Vectorworks to see how they relate to the imported image. This will give you more confidence that it's not the WKT.

 

Another way might be if you export a shapefile with prj file, and then import it in Vectorworks in a new file [so that it sets the Georeferencing]

[Help with georeferenced point file importing where it should be]

@PNWPaul I was able to import it somewhat where it is supposed to go, but unfortunately it is not perfectly fitting. And I'm not sure what's wrong. Anyway, here is what I did:

ok, so these are called cartesian coordinates (i.e. easing and northing).
1110896.65E
1313006.9N
Note they are measured in linear coordinates, where lat/long are measured in degrees.

 

After I setup the Vectorworks drawing geo-referencing with the WKT above, these cartesian coordinates gave me:
-48.91273585 lat
-122.070105424 lon

These checks are very easily done in Vectorworks using the Stake tool, and the .Set Geolocation" button.
Then with the Geoimage, it all seems to line up to your image from the original post:

 

Then I was able to import the .las file, making sure the center checkbox is off, and select Feet for units as this coordinate system uses feet (note, it doesn't really matter what units the Vectorworks document is in)

 

Then the image didn't fit at all, it was way to far, and comparing the location of where it should be to where it is (in cartesian coordinates) it seems like it's off by scale of 1000.

 

So then I just scaled the Point Cloud object by factor of 0.001:

 

And that put it at the stake point, but it is still slightly off from the geo-image background:

 

 

I have no idea why this is happening. I'll keep poking it, and see if something comes out.

[Question about Text Format in Worksheet - why is it trimming decimal digits when reading from other cell]

Thank you Hugues ☝️

[Help with georeferenced point file importing where it should be]

@PNWPaul It looks like EPSG:4152 is not the correct coordinate system, as it looks like this is only spherical coordinate system. The images you provide shows a projection added to it, but it is not clear what is the EPSG if that projection.

 

I managed to pull the data out from the image and setup this WKT that is based on EPSG:4152 spheroid plus the projection parameters from your images. See below for the text of it.

 

However, I'm still not able to align your file with it, as it's not clear what units the LIDAR file is using. Yes, it should be automatic, but it should be possible to be done manually. I've tried several settings but shouldn't guess it.

 

Do you know the latitude and longitude of the location where the file is supposed to be? That can give us a clue what are the correct unit configuration.

 

Regards,

Vlado

 

PROJCS["custom",
    GEOGCS["NAD83(HARN)",
        DATUM["NAD83_High_Accuracy_Reference_Network",
            SPHEROID["GRS 1980",6378137,298.257222101,
                AUTHORITY["EPSG","7019"]],
            AUTHORITY["EPSG","6152"]],
        PRIMEM["Greenwich",0,
            AUTHORITY["EPSG","8901"]],
        UNIT["degree",0.0174532925199433,
            AUTHORITY["EPSG","9122"]],
        AUTHORITY["EPSG","4152"]],
    PROJECTION["Lambert Conformal Conic"],
    PARAMETER["latitude_of_origin",45.33333333333334],
    PARAMETER["central_meridian",-120.5],
    PARAMETER["standard_parallel_1",45.83333333333334],
    PARAMETER["standard_parallel_2",47.83333333333334],
    PARAMETER["false_easting",1640416.667],
    PARAMETER["false_northing",0],
    UNIT["foot",0.3048,
        AUTHORITY["EPSG","9002"]],
    AXIS["Easting",EAST],
    AXIS["Northing",NORTH]]

 

[Question about Text Format in Worksheet - why is it trimming decimal digits when reading from other cell]

@ashot you can use the TXT function to convert to string: https://developer.vectorworks.net/index.php?title=Worksheet_Functions#Text

Example: =TXT(B2, 'General', 'Dec', '0.0000000000000')

 

I'm looking at the other part of the question.

 

 

[Known Issues with SQLite linking]

@Don Seidel as far as I'm aware, SQLite is working ok. I know you are having an issue which you already are working with an engineer to figure out, and we're having trouble reproducing it on our side. I'm not sure you can blankly state that it's completely not working judging by the conversation on the filed issue.

 

Is this a new issue? Please file it as a new issue and let us know.

[Regenerating Laubwerk plants in VW2023 SP7 causes mayhem]

On 11/14/2023 at 9:44 PM, Your Name Here said:

If it's mission critical, I don't use Laubwerk plants.

 

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.

[Site Modifiers - Batter slope with constant slope 1:2 towards existing site and automatically created a Grade Limit in this line?]

@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.

[Vectoworks 2024 very slow to open]

@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.

[Vectoworks 2024 very slow to open]

@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.

[Accurate Sheet Legends Using Data Tags]

@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.

[Vectoworks 2024 very slow to open]

@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.

[Vectoworks 2024 very slow to open]

@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!

[Change tool behaviour with mode bar.]

15 hours ago, Letti R said:

so i finished my Plug-in. Now i want to put it in the Forums to share it (for free). Is there something i have to consider to not run into legal problems because i used the VW SDK, or can i just put it out there for others to use?

@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.

[Live connection between web app and marionette]

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

 

[Vectoworks 2024 very slow to open]

@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?

[Vectoworks 2024 very slow to open]

12 hours ago, Amanda McDermott said:

Tempted to try this - can anyone from Vwx advise on whether this is a good idea?!

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.

[Getting started with VWorks SDK 2022]

@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