inikolova

@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

@mjm, thanks! I see your point. It makes sense when you have more than one projects going on in parallel and you don't sit idle waiting for the cloud processing to complete. Can you elaborate on why having the .vwx file with the updated viewport is more valuable to you than having a PDF with the rendered viewport?

@Christiaan Thanks for reviving this thread! Saving the .vwx file with the rendered viewports back to your account is a quite simple task. However, think about what happens when you send a file for rendering on the cloud, and you continue to work on your local copy and make changes. By the time the cloud finishes rendering your viewports, you made some changes to the file, but the file you get from the Cloud with the updated viewports doesn't have your latest changes. Is that desirable? I think not. Saving a copy of of a .vwx file every time you do cloud rendering can be a dangerous setting, if not used properly, which is waiting for the cloud to do the rendering and then continuing work with the copy of the file you received when the rendering is finished. To me, waiting for your rendering to complete before you can continue working defeats the whole point of cloud rendering. I think the best way to implement your request would be with streaming, allowing the cloud to send updates directly to the .vwx file that you are working on, but we don't have this yet.

Hi @Florane, The purpose of the Google Drive integration with Vectorworks Cloud Services is to allow you to use the Vectorworks Cloud Services features without having to modify your existing Google Drive workflow or file structures. You can submit cloud processing jobs from files stored in Google Drive, and you can view 3D models (.vgx files), panoramic images, or 360° animation movies via the Vectorworks Cloud Services web portal or the Nomad mobile app, for example. Syncing and collaboration with the files should be done with Google Drive directly. The file needs to be downloaded by the Google Drive destop app. If you download it from the Cloud Services web portal, the updates you make won't sync back to your Google Drive. Copy to home creates a copy of the file on the Vectorworks Cloud storage, which is not connected to the original in Google Drive. The changes you make to the file copied to the Vectorworks Cloud storage will be synced only to the Vectorworks Cloud, if you use the Vectorworks Cloud Services desktop app, but the changes won't make it back to Google Drive automatically. Yes, Sync and Edit permission is only supported for files on Vectorworks Cloud storage. You should share the folder with Edit permissions through Google Drive directly. We will investigate. This should work, but it doesn't seem to work for me at the moment either. I have notified our developers. I think it becomes very simple when you understand when it is appropriate to use the integration, and when it is better to use the app that stores the data. You don't have to migrate everything to Vectorworks cloud, but if this is your desire, we will be happy to accommodate your needs. Purchasing additional storage is not available at the moment, but we are able to increase individual quotas as needed, free of charge. Please feel free to message me directly and I will be happy to help you further. Best regards, Iskra Nikolova

Hi @dnhopper, I am sorry to hear that you are having difficulties making custom fonts work with Vectorworks Cloud Services. One requirement is that the font files need to be placed on the same cloud storage where the .vwx file is stored. So if your file is stored on Dropbox, the fonts need to be on Dropbox, and you need to select "Store on Dropbox and Process on Vectorworks Cloud" in the Publish dialog: If this doesn't help you, please send me a direct message with a link to your file in Dropbox and the names of the fonts that are not being found. With this, I would be able to investigate the issue and try to help you with making it work. Trying to Publish from a simple file with custom fonts from my Dropbox worked for me, so I need to look into your specific scenario. Are the fonts you uploaded converted from a different format before uploding to Dropbox? Often, I find that the reason for custom fonts not working is due to conversion. I am able to fix the issue of this kind by editing the font metadata with a font editing tool. Best regards, Iskra Nikolova

@Max Jones, We found that your issue is caused by the + character in the file name. Please rename the .vwx file and regenerate the 3D model and it should work. We are working on fixing the issue. Best regards, Iskra Nikolova

@jbtroost Thank you for your help! Yes, my experience with Chrome is also the best when it comes to viewer performance. Other browsers are not as optimized as Chrome. I don't think there was ever an export setting that relates to shadows. It is in the viewer - in the Settings panel. I hope that helps. Please let me know if I could help with anything else. Best regards, Iskra Nikolova

@Matt Overton, The button has a tooltip on mouse hover, but I can see how it can be easily missed. All points taken, we will make corrections accordingly.

@Matt Overton, Thanks for your feedback. I am sorry to hear you found the job cancellation hard to find and thanks for pointing out the lack of a confirmation dialog. We will take care of these items. Regarding the differences in rendering that you see locally vs the cloud - it could be due to different Vectoroworks build numbers (older build may work properly while a newer build have a problem or vice versa). Please feel free to send me a direct message on the forum with more details about the differences you are noticing and I would be able to investigate further. Best regards, Iskra Nikolova

Hi @Johan de Groot • LYVR, Would you please clarify which aspects of the navigation you find difficult? We spent a lot of effort on the navigation and would like to hear how you think it can be made easier. We are actively working on numerous improvement of the viewer and will be happy to include navigation improvements in our upcoming iteratiiterations. Best regards, Iskra Nikolova

@Tom W., Are you using a custom workspace? The command is available in all standard workspaces, but you can also add it to your custom workspace using the workspace editor.

@line-weight, The Export VGX command is available in Vectorworks 2022 SP3 or later. I will make sure to include this in the Help. Thanks for pointing that out! I am glad you managed to export the model via the Vectorworks Cloud Services desktop app. Yes, transparent objects cast shadows currently. We are looking forward to fixing this it as we implement a "white model" functionality. It will require marking which objects are transparent so we don't make them white, so we can use that to also disable shadows. Reagrding your glass texture that appears opaque, please send me a message with a test file so we can evaluate this specific case further. We are aware of some issues with displaying transparency. Draw edges is coming soon, along with white model. 😉 Best regards, Iskra Nikolova

Hi @elepp, I am sorry to hear you are having troubles. Please send me a message with the link to the .vwx file and I will investigate. Best regards, Iskra Nikolova