SAPIEN Technologies

Please try service build 5.8.217 and let me know if you are still having issues.

If you are getting a different error, please post the new error message here. If it's the same error, make sure your versions of assemblies loading match the version in the error message. Your previous error was unable to find this assembly: https://www.nuget.org/packages/System.IdentityModel.Tokens...

Can you please open your snippets in our Snippet Editor, verify the information is correct along with making sure a Shortcut is specified, then save. There has been changes since 2017 that may have affected loading older snippets in PrimalSense. You may need to restart PowerShell Studio in order for...

Thank you for reporting. I've been able to reproduce this behavior and have informed the development team. When I have more information, I'll post here.

Please refer to the following article:
https://www.sapien.com/blog/2021/11/22/ ... -what-now/

The script that is generated when you run in PowerShell Studio vs when you are packaging is the same other than the name. For packaging, the script generated is name ProjectName.package.ps1. When running, it is named ProjectName.Run.ps1. I'm not sure what your buttons that are not working are suppos...

The original post was for service build 5.8.203. Has this been a consistent issue for you in builds since service build 5.8.203? Do you remember if you experienced the behavior before that?

Also, does this ever occur with files not saved on your network?

Can you please run your script in the console (Ctrl + F8) then copy and paste the error output here?

Please try service build 4.5.82 and let me know if you are still experiencing this issue.

A fix for the second issue reported was released in service build 5.8.214.