Jump to content

inikolova

Vectorworks, Inc Employee
  • Posts

    696
  • Joined

  • Last visited

Posts posted by inikolova

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

    • Like 1
  2. 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

     

     

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

    • Like 1
  4. 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 

    • Like 1
  5. 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 

     

  6. On 1/3/2023 at 2:49 PM, kwik said:

    Any ideas?

    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

    • Like 3
  7. @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

    • Like 1
  8. @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

    • Like 1
  9. @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

  10. @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.Screenshot 2022-11-17 at 8.27.55 PM.png

     

    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.

     

    Screenshot 2022-11-17 at 8.23.24 PM.png

    Go to https://cloud.vectorworks.net/portal/account/ and make sure these font mappings have disappeared.

    Screenshot 2022-11-17 at 8.25.50 PM.png

    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

     

    • Like 2
  11. 3 hours ago, Peter W Flint said:

    Philosophically, I think a product that asks for a significant investment from its users should work as it is advertised.

    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.

    • Like 1
  12. @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

    • Like 3
×
×
  • Create New...