inikolova

Hello everyone, The fix for this issue has been deployed to our production servers. Please check it and let us know if you continue to have any issues.

Hello, Is anyone here still experiencing the desktop app's error on startup with the latest released version 8.4.933? If yes, can you please send me the log files right after you have experienced the issue to inikolova@vectorworks.net? On Mac, zip up the entire folder: /Users/<username>/Library/Logs/Nemetschek/Vectorworks Cloud Services. On Win, zip up this one: C:\Users\<username>\AppData\Local\Temp\Nemetschek\Vectorworks Cloud Services Thanks, Iskra Nikolova

Hi @SebasVidales, I tested the light issue again today and it seems to be working for me when I have the file stored on Vectorworks Cloud Services. My guess is that your job may have been processed by a server that hasn't received the updates yet. I am verifying with our engineer to make sure all servers have been updated with the fix. Regarding the status update... For Cloud Publish jobs, the progress is based on the number of items being published, not the time that remains for the publishing to be completed. For example, if your publish job contains ten sheets, when the cloud renders the fifth sheet, the status bar will display about halfway done. Since this does not account for the number and complexity of the viewports on each sheet layer, you may see the status slow down as it starts to render a more complex viewport or a sheet layer with many viewports. The name of the item currently being rendered also displays. Since you only have one sheet layer, the progress can be either not yet started, half done while rendering the sheet layer and fully done when the rendering is finished. You would not be able to see detailed progress of the actual rendering, this is expected. I agree with you that it is strange that the progress reported as 100% done while it is still doing the rendering. While rendering a publish, consisting of a single sheet, it would be better to display half way done. I filed a bug report to our engineers. This is an issue only with the progress reporting, not with the actual server processing. Regarding your job that has run for 7 hours, it sounds possible, depending on your render and DPI settings. If you don't mind sharing your file with me at inikolova@vectorworks.net, I can investigate this in more depth. Best regards, Iskra Nikolova

Hi @toby4571, Do you have this setting turned on? If this setting is not turned on, the Cloud will just export the out of date viewports without updating them. Please let me know if I can help with anything else. Best regards, Iskra Nikolova

@Matthew Byrne, We are currently in a process of updating our production cloud servers to contain the fix about the Export PDFs as separate files setting and other rendering fixes, including the one with the lights not being rendered. If you try tomorrow, I would expect things to work much better for you, The issue with the camera object not being included in the rendered panorama will be released in September, along with the Vectorworks 2021 release. Please let me know if there is anything else that I can help you with. And thank you for using Vectorworks Cloud Services. Best regards, Iskra Nikolova

I narrowed it down to being an issue with Vectorworks, so I submitted an issue to our rendering team and they are currently looking into it. We have a fix for the lights in the upcoming version. I will let you know when it gets released. I am not familiar in depth as to which lights the issue was related to, but my guess is that not all types of light objects were affected. There is no workaround for this at the moment, but we are doing our best to release the fixes as soon as possible. I apologize for the inconvenience. Best regards, Iskra Nikolova

@Matthew Byrne, I found out that there is an issue with the Publish job when the option to Export PDF as separate files is turned on. This issue will also be fixed with our next planned deployment. In the meantime, you can try turning off this option in order to get the results in your Dropbox folder. If you necessarily need a separate file for each sheet, you can submit an individual job for each of your sheets. I know this can be a bit tedious, but I hope you won't have to use this for a long time. I am continuing to investigate the remaining issues that you reported and will let you know my findings as they become available. Best regards, Iskra Nikolova

Hi @Matthew Byrne, I may need to get your file in order to investigate the Panorama issue. It sounds like something I may not be able to easily replicate with my test files. If you are willing to share your file with me at inikolova@vectorworks.net, that would help me a lot with the investigation of the issue. Regarding the Publish issue, I will test with my test files to see if I can reproduce. I will do this tomorrow Regarding the rendering without lights, we have a fix that we will release with the next planned deployment, in about 2 weeks or so. Best regards, Iskra Nikolova

Hi @Matthew Byrne, Upon opening the file in Vectorworks, does a full lit scene render as expected? We have a currently unresolved bug about Vectorworks that the lights will not render unless all of them are turned off, then on again, in the Visualization palette on a Design Layer (doing so on the Viewport itself has no effect). When processing on the cloud, since no manual turning on/off of lights is performed, this results in no lights being rendered. Please let me know if you believe this is not what is happening in your case and we can work together to investigate the issue further. Best regards, Iskra Nikolova

Hello @str, No need to report this as a bug, we are aware of the issue. With iOS 13, Apple have removed the ability of the user to allow safari Motion & Orientation access to all websites in favor of relying on the webpage creator prompting the user to allow access on a page by page basis. This puts the fix entirely back on Vectorworks. We are looking into addressing this problem. I apologize for the inconvenience this is causing you. Best regards, Iskra Nikolova

Thank you, @khumenny for the additional clarification! The performance improvements that we are working on currently will open up the door to many possibilities for AR. I will consult with you once we are ready to tackle further AR improvements.

Hi @khumenny, Thank you for your post! We are currently working on addressing the file size limitation and it is our top priority. Once we have overcome this struggle, we can consider different improvements like location awareness or positioning of models by using image markers. We have talked a lot about using image markers, and we even had a working prototype, but we realized that the technology that allowed us to do this was very restrictive in a way that these image markers had to be built into the app. So, it didn't quite work for our needs. Also, we thought that image markers have a downside that you have to have a printer and print them. What do you think would be the benefit of using an image-based marker vs touch with your finger on any surface to pinpoint where the AR must start? Do you think scanning a QR code could be used to serve the same purpose? Proper scaling and the orientation of the model at the launch of the AR sessions are problems that could probably be approached differently as well. We do show a model scale currently. 100% gives you the model on a real-world scale. We scale the model down so that you can see the whole model on your screen and better orient yourself. What could be a different behavior that would serve you better than scaling/positioning "by eye", if we take the image markers out of the picture? Best regards, Iskra Nikolova

Hi @mattleaf, We recommend that the Vectorworks Cloud Services folder is on the local computer - any physically connected hard drive, not necessarily the C drive where the OS is installed. While it may seem to sync and work properly, there may be cases that the app is not handling, such as the Publish issue you are seeing and many more. The reason why you get a file that cannot be opened is because you are submitting a job that has the items in red, which means that they cannot be found. It is a known bug that we allow the job to proceed in this case, while in fact it should not allow you to proceed, because there is no way the job can produce results when the items can't be found. I hope this helps! Best regards, Iskra Nikolova

Hi @mattleaf, If you see the issue after re-opening the document, that is most likely the reason why the rendering on the cloud produces incorrect result, not the cloud rendering itself. There is a Vectorworks on the Cloud that opens the file you submitted and does the Publish the same way that you would do manually on your local computer. If you could email me (inikolova@vectorworks.net) a simple test file that can demonstrate the problem, I can submit it to our rendering team to investigate further. Best regards, Iskra Nikolova

Hi @mattleaf, That's correct - in order to Publish using the Cloud, the file must be saved to your Vectorworks Cloud Services folder on your desktop. The only requirement is that the file needs to be in the folder at the time the cloud server actually starts working on the job. After that it is up to you whether you want to keep working in the same folder or not. Best regards, Iskra Nikolova