inikolova

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

LiDAR equipped device running iOS 16 is required for Room Plan. The Object Capture (photogrammetry) uses LiDAR and depth data to aid in object reconstruction, but it is not required. Photos from any camera/drone are supported, they just won't produce an object in the real scale and orientation and will need to be adjusted after being imported into Vectorworks.

@kwik This post is relevant to an algorithm which we no longer use (replaced recently with a better one). Please refer to this article for the most up-to-date information: https://cloud.vectorworks.net/portal/help/pages/capture-photos-for-3d-models/ I don't think the way you captured your photos relate to the issue you are reporting though. I posted a reply in another forum post that you submitted with the same issue. Best regards, Iskra Nikolova

The Cloud just had a new version deployed. Can you please retry to see if it works now? I tried to reproduce your issue by naming other files the way you have named yours and I was not able to reproduce the problem. I'll continue investigating if it is still not working for you. Best regards, Iskra Nikolova

@Oaktown, I am sorry you are having difficulties making it work. I suspect it's returning "No such xattr: com.apple.quarantine" because the quarantine has already been removed. Please make sure you are correctly replacing the current files in the Vectorworks installation folder with the ones provided in the zip. Vectorworks Remote.vwlibrary should go to: Plug-ins The contents of the VWRemoteServer.framework folder should replace the contents of the Plug-ins/VWRemoteServer.framework folder Make sure the old ones are completely removed from the Vectorworks installation folder. We tried this .zip on a few machines and it worked on all of them, so I really hope it will work for yours too. By the way, these are for Vectorworks 2023. Are you trying with a prior version by any chance? Best regards, Iskra Nikolova

@Oaktown Please unzip the attached file and drag its contents into the Vectorworks Plug-Ins folder, replacing the existing ones. This should be able to fix the Remote crash. Note, you need to run the Quarantine command as follows: -In Terminal type: xattr -d com.apple.quarantine make sure there is a space, after ‘quarantine’, then drag the attached .zip file into the Terminal window and press <return> -Unzip the file using the Mac operating system's decompression option, do not use another decompression utility. Please let me know if this doesn't work for you. Best regards, Iskra Nikolova Remote plugin M1 fix.zip

Could be a printer calibration issue?

@Peter W Flint, I am glad you are now getting the proper result! Yay!!! I think the reason why you had these mappings on the Cloud was that you had them in your local Vectorworks mappings. You probably opened a file that contained these fonts before you had them installed on your machine. And when you submit a job to the cloud, your local mappings are automatically synced to the Cloud. Best regards, Iskra Nikolova

@Peter W Flint, I investigated this in more detail and here is what I think is the cause of your problem. During file generation, the cloud server searches for fonts using the following priority: 1. Cloud server system fonts 2. Current font mappings in your cloud preferences 3. Custom fonts that you have uploaded to cloud storage It looks like the Yantramanav font you are using is currently mapped to Arial in your cloud font mappings. To fix this, you need to delete these font mappings from your Vectorworks. In the Vectorworks preferences; on the Display tab, click the Edit Font Mappings button, and delete these mappings. Quit Vectorworks to save the font mapping preferences. After this, open the Vectorworks Cloud Services settings and click the SYNC button to sync your local mappings to the cloud. Go to https://cloud.vectorworks.net/portal/account/ and make sure these font mappings have disappeared. After this, the Cloud Publish should be able to give you the expected result. Please let me know if this doesn't help. Best regards, Iskra Nikolova

I agree with you. The issue you are seeing is likely due to some specific properties of the font you are using. I will do more research and try to help with your specific situation.

@Rick Berge Thanks for chiming in. I was not sure if Peter's issue was due to font platform differences or because his custom font is getting mapped to Arial. I will try to research some more and find out if font mapping is the culprit in his case.

The filed issue currently has a Vectorworks 2024 as a fix version, so I hope it will be fixed by then.

@Peter W Flint, If you are on Mac, there is a known issue observed when a file created by a Mac version of Vectorworks is opened and Published by a Windows version of Vectorworks. Since the Vectorworks running on the Cloud is Windows-based, the issue is seen. I would recoomend you use an image, to ensure the Cloud will produce the correct results in the title block. However, I would also recommend you keep an eye on other scaling issues like that in other elements of your pages. The isssue is not specific to title blocks. You can also try using another font with a similar appearance to see if that helps in any way. Also, check your email to see if you get an email that custom fonts were mapped to Arial. It does look to me like your original font is getting mapped to Arial. If you have used a font converter to convert a Mac font family into idividual fonts (.otf and .ttf) it is possible that the Vectorworks on the cloud can't recognize your custom font. In the past, I have been able to fix custom fonts like this by using a free font editing tool called FontForge. If you need further help, plese don't hesitate to send me a personal message and let me know about specific fonts that are not working and I will try to help you. Best regards, Iskra Nikolova

Oh, I realize this is for the Educational version where the situation may be more specific. What option are you setting on the Store and Processing dropdown on the Publish dialog?

@Claudia P., Are you trying to Publish to the Cloud? Can you check if the Vectorworks Cloud Services app is up and running? A few days ago, we noticed a pronblem with the app not launching after an auto-update. I assume you may have this issue because of that. If the desktop app is not launching, try: 1. Restarting your computer. It the issue persists, continue to step 2. 2. Downloading the latest app from https://cloud.vectorworks.net/download/latest/Mac or https://cloud.vectorworks.net/download/latest/Windows and install it, replacing the current version that is on your computer. Please let me know if these steps do not fix your issue. Best regards, Iskra Nikolova

Thanks everyone! I appreciate all the feedback. To me, the most important thing is how you use our product, not how we thought you would use it. If we had wrong assumptions, we can do things to correct them. 🙂

Hi @Andy Broomell, thanks for the clarification! You are saying it doesn't work for you because you don't get the rendered viewports back to your file. I misunderstood that rendering viewports never worked in the way they are designed to do so. Thanks for explaining your workflow in detail. I will discuss this with the team to see what we can do in the short term, until we are able to offer "the ideal" solution.

@mjm, the Cloud is able to produce final renderings in a form of panoramas, images and PDFs. It sounds like you think it can't. My question was more about whether having a copy of the .vwx file with "Saved viewport cache" is more valuable to you in some way compared to getting the final rendered viewports in an image or PDF file