ollieblanks

Sorry for the delay. For us to make an informed analysis of this we will need to see the latest debug.log file (whilst reproducing the issue). Can you share that here or create a support ticket so we can investigate further?

All features that are currently in the legacy Windows client is planned to be included in the new GUI. Hope this helps!

Sorry for the delay. Can you please confirm what version of the Version Control package you have installed in Package Manager? Additionally, does the issue persist when restarting the Editor and were there any particular steps you took to get this behaviour to occur?

Sorry for the delay! Adding the user to the Organization will grant them access to the everything by default. If you want to configure more granular permissions then you will need to set these within the client. Please see our Security Guide for more information and scenarios for setting up permissions. Hope this helps!

Hi, If Substance Painter has its own command line diff tools then these can be used with Plastic SCM. Alternatively if ImageMagick supports these file types then this is configured in Plastic SCM by default and should work out of the box. Hope this helps!

Hey Mo, Sorry I'm only seeing this now. As we have been working together on a support ticket, I suggest we continue doing that.

Hi, Please can you log a support ticket providing some screenshots or examples for this. I would like to fully understand the problem here.

All features that are present in the Legacy GUI will be put into the new GUI. Unfortunately, it is just a case of prioritisation. Hope this helps!

Sorry for the delay in response. In the Plastic SCM window (or in the Plastic SCM client) you can review the Changesets in your repository... This can be cross-referenced against the Last Commit value in Cloud Build... Hope this helps!

The command cm status --machinereadable --header will always return the changeset number as the second output parameter. With this information you can run cm log cs:## --csformat={branch} to return the branch name. (Only caveat is this solution will not work on Gluon workspaces, as they don't technically point to a single changeset!) Hope this helps!

Hi @hwang, You can change your account to use password authentication. To create a password for your account, please log out and use the Forgot Your Password function at plasticscm.com. Hope this helps!

I suspect we may need to look at client logs (found here: %LOCALAPPDATA%\plastic4\logs) to diagnose this. If you haven't already, please can you log a support ticket?

Hey @Arlorean, I truly empathise with the situation you faced, there is definitely room for improvement when it comes to safeguarding changes from the user! I think its important to note that this feature would only be effective for reversing a Delete operation and not an Undo operation, as the Undo operation only reverts changes to controlled files and does not delete Added and Private files.

For high priority issues, please log a support ticket.

I suspect this workspace has gotten into a bad state from the experimentation. Does the issue persist if you create a new workspace?

Ah yes the order by and limit clauses. Great solution!

You could use something similar to this to get the highest number changeset number. cm find changeset "where date > '3 months ago'" --format={changesetid} --nototal | tail -1 Hope this helps!

Hi @Oleg, Sorry to not get back to you sooner. Scene are just YAML files (.unity) and meta files (.unity.meta) that store certain values and references to other objects and such. It sounds like some of these references are not resolving, perhaps due to files being ignored or not checked in, which is why they are empty. Please can you create a new workspace and try making the changes there?

Sorry we didn't get to your forum post quicker! From the looks of your support ticket, it appears that there was some confusion around ignore.conf and the fact that the rules are only applied to files that are not under source control (private files).

Glad to hear that you already resolved the issue!

Hi all, Please accept my apologies for the disruption of service and the lack of communication. Unfortunately, our automated monitoring did not pick up this outage and so it was not communicated on the Unity Cloud Services Status page. This is something that we plan to remedy and further measures will be put in place to make sure communication is improved. Here is a summary for this latest outage in Asia. Cause: Server was not responding to any requests for organizations that are hosted in the Asia-East region. Date: 29/03/2022 Downtime: 5h Actions taken: From now on we automatically restore the service when it fails so the server will continue accepting requests again. Also if for any reason the service cannot be restored, the server instance is stopped and a new one will be launched automatically.

Hi both, Please accept my apologies for the disruption of service and the lack of communication. Unfortunately, our automated monitoring did not pick up this degraded service and so it was not communicated on the Cloud Services Status page. This is something that we plan to remedy and further measures will be put in place to make sure communication is improved. Here is my summary for the latest outage. Cause: Server load issues caused degraded performance for organizations that are hosted in the US region. Date: 29/03/2022 Downtime: 3h 10min Actions taken: Added ThreadPool pressure to our automatic monitors so the situation can be detected and mitigated automatically. Reduced the usage/pressure on the ThreadPool. Tuned the ThreadPool configuration to have a higher threshold. Actions still in progress: Extra reduction on the ThreadPool usage/pressure Improvements on the REST API to reduce its impact and improve general performance.

For anyone else visiting this thread. I suspect that the Enterprise Edition of Plastic SCM was installed by mistake (The version used for self-hosted servers). Installing the Cloud Edition will resolve this.

I suspect the issue may be that the automatic migration of your local copy of the project has failed and it is still trying to use your archived Collaborate repository. Please can you do the following in an attempt to resolve this: Make sure you have the latest version of the Version Control package in Package Manager and that you are on a supported version of Unity. Navigate to the Services window and disable the Collaborate service. Restart the Editor, if you are alerted to migrate your local project, please do so. Either way, you should now have access to the Plastic SCM window via the Window > Plastic SCM menu option. Hope this helps!

@Mikael Kalms, thanks for all these reports. Keep 'em coming! I hope you have found the WebUI beneficial to your workflow. @QuellWobling, very much so!!