inikolova

Hi @girwin, I am glad it worked! You can select all of them at once and then and click Options (click to select the first and then Shift+Click to select the last. This will select everything in between). If you save the set, this setting should be preserved within the set. I think there is also some logic that sets this option by default for newly added sheets once you have selected it previously. So, over time, it should become the default for you as you start using it.

Hi @girwin, From the Export PDF settings, check the "Export the whole printable area as one page" and see if you get the desired results. You can find this setting on the Publish dialog, when you select the items you want to publish to PDF, and click Options. Note that if you are publishing more than one sheet, you need to make sure this option is set for all of them.

I have entered this wish in our project planning tool for consideration.

@raumplaner, There was an issue that sounds similar to what you are explaining, which was fixed in Vectorworks 2023 SP4. If you haven't yet upgraded, please upgrade and let us know if you are still experiencing the issue. And yes, an example file would help a lot. Best regards, Iskra Nikolova

Just to follow up here for anyone reading this post... After further investigation, it was determined that referenced geometry is getting exported in the .vgx file and appears to be working fine.

I entered this into our task planning tool. It will be considered. Thanks!

@setdesigner, Redshift rendering is available on the cloud, please send me a personal message with your username, so I can investigate why it may not be working in your case. You can use the Publish command in Vectorworks to select individual sheets for export and submit to the cloud for processing. Yes, referenced geometry is not supported in the .vgx export currently.

@Jacob@tangably.comThe fix is included in Vectorworks 2023 SP4, planned for release next week. Users will not have to do the manual fix after they upgrade to SP4.

Hi @Jon wat, Are you submitting the .vwx for PDF generation from Nomad, i.e. for processing on the cloud? Only PDFs generated by the cloud contain measure data. Also, measuring works for top/plan viewports. Here is the Help article for this functionality: Ifhttps://cloud.vectorworks.net/portal/help/pages/measure-and-mark-up-pdf-files/. If you still can't get it to work, please let me know and I will try to help you further. Best regards, Iskra Nikolova

Thanks, @Christiaan! I will share your nice words with the whole team that was involved in this challenging effort. I am so glad to hear that you are loving it.

Ok, I am glad you found the culprit. Please let me know if I can help with anything else.

Hi @Tim Harland, I am sorry to hear that you are having issues with referenced geometry. There are a few prerequisites for referenced files to work on the Cloud: 1. The referenced files must be uploaded to the same storage location as the master .vwx file. For example, if your master .vwx file is saved on Vectorworks Cloud Services storage, the referenced files must already be uploaded at the time you submit the master file for processing. For example if your .vwx file is saved on your Desktop and you submit it for Publishing on the cloud, the referenced files won't be uploaded, so the cloud rendering would not contain the geometry, unless your master .vwx file contains the saved reference cache. 2. Both the master and the referenced files need to be converted to the latest Vectorworks file version (which is 2023 currently). For example, if your .vwx file is created in Vectorworks 2022, you can submit it for processing, but the Vectorworks 2023 running on the Cloud won't be able to use your referenced files even if they are uploaded to the same storage, because they are an older version. I hope that helps. Please let me know if I can assist you further in any way. Best regards, Iskra Nikolova

Hello @jnr, It is expected for the 3D model to contain all objects that are visible at the time of the export. I cannot think of anything that would cause this behavior by design. I looked at prior jobs on our servers and I think you are not using the clip cube export settings, so you should be able to see all visible geometry in your model. Your files appear to be coming from Dropbox storage though. I wonder if somehow Dropbox could be sending us an older version of your file to complete the job with? Would you mind uploading a copy of your file to cloud.vectorworks.net, and see if the 3D model gets generated successfully from there? That would at least give us an idea if it is a Dropbox specific issue, or an issue with the export in general. Thanks, Iskra Nikolova

Hi @jeff prince Thanks for trying this feature and for providing your feedback. Some of the items you are mentioning are specific to the technology being used, so we have no control over these limitations. Check this article for more details: https://cloud.vectorworks.net/portal/help/pages/create-a-room-plan-with-lidar/?app=IOS_NOMAD I think what this press release was aiming to convey as a message is that the framework automatically detects walls and doors and other object types to create the room plan. I did not realize that the way it is phrased, it might imply automatic conversion to native Vectorworks objects upon import. I think this would be really nice future project though. Vectorworks 2023 SP4 will support USDZ import, so you will see object names, like Chair, Wall, Table in the Data pane of object info palette. But the imported objects will be meshes. I hope this clarifies it a bit. Best regards, Iskra Nikolova

Thanks for reporting, Christiaan!

Hi Christiaan and Ben, Our engineers are looking into this. It sounds like an issue specific to .vwxw files. To work around this problem, you could save the current copy of your working file as a .vwx file and try publishing from there. I know this is kind of inconvenient, but I hope we will have a fix soon. Best regards, Iskra Nikolova

Hi Christiaan, When we implemented LAN sync, we also added a way to check peer info for testing purposes, but this was not exposed to the user. I think we should be able to display this info in a similar way, along with additional information. I opened a request for our engineers to look into that. Best regards, Iskra Nikolova

Hi Christiaan, Thanks for your feedback! I understand the need for such functionality and we will consider it as we make plans for future improvements. We have the same request from others already, so I went ahead and added your vote to it. Best regards, Iskra Nikolova

You're welcome! I am glad it worked. I will make sure we update the Help with that information.

I just got a tip from our Project sharing pro 🙂 . You change the visibilities in your Working File and Save & Commit. In the commit dialog, you have to make sure you choose to commit “view settings”. Note: only users with Project permissions or higher can commit view changes. I haven't tried this yet, but I thought I would share so you can try also. Maybe it will work for what you are trying to do.

Well, it is enabled and the job succeeds, but the question how you control the views remains.

Hi @Christiaan, Thanks for pointing that out! I will look into it. To be honest, I am not sure how the visibility of objects is set in the project file. I need to investigate and get back to you (and also update the Help article). Perhaps you can try refreshing your working file to be up to date with the project file and then generate the 3D model from there, to set the correct object visibilities? Best regards, Iskra

Hi @maxstk, Thanks for your feedback! We already have this wish in our project tracking system. I added your vote for it. We are considering to implement other Cloud job types that offload time-consuming tasks to the Cloud, so this is on our radar. Best regards, Iskra Nikolova

Hi @FKA, In the Photos to 3D model dialog, make sure you select the desired detail of output model. "Full" is the default, but maybe you used a lower value? (see the screenshot below) When we evaluated the "old" photogrammetry algorithm against the Apple's framework, we found that lower amount of geometry didn't necessarily mean lower quality reproduction. The new algorithm is just more optimized, so it doesn't create unnecessary geometry, which the old algorithm was doing. This results in a smaller file, which is easier to work with in Vectorworks. This also allowed us to be able to reproduce geometry from photo sets that were failing with the old algorithm. If you would like me to take a look at your specific case, please feel free to send me a direct message with more details, and I can investigate further. Best regards, Iskra Nikolova

Hi @Carla A, I am sorry to hear that you are having issues with the Cloud. Please let me know the username of the account that is experiencing this problem in a personal message (or email me at inikolova@vectorworks.net), and I will investigate. Best regards, Iskra Nikolova