Jump to content

ollieblanks

Administrators
  • Posts

    268
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by ollieblanks

  1. This is because you are trying to invite members to a local repository on your client machine (default@local). this is not possible with a standard Cloud Edition installation which is why you are presented with this error. Thanks for reporting this, I will try and get a more useful flow to be presented in this scenario.

    If you want your project to point at a Cloud Repository instead, you need to Turn Off Plastic SCM for Unity (as shown in your screenshot), which will delete the current configuration and allow you to reopen the Plastic SCM window and configure it to work with a repository on your Cloud Organization.

    Hope this helps!

     

     

  2. Unfortunately, you do need a license for a self-hosted Enterprise server. You will probably find that you are currently on a 30 day trial. I suspect Cloud Edition would be the most cost effective solution for your use case.

    Hope this helps!

  3. It seems that you have an application changing the permissions and/or the timestamp of the file which is causing them to show as changed with the content being identical.

    • Are you able to run Plastic SCM with elevated privileges? This should resolve the inability to change the permissions on the files.
    • What application are you using to modify these files? Is it possible that this 3rd party software is modifying the OS level permissions on them?

    Hope this helps!

  4. Hey Ben,

    Gluon is designed for artists who do not need the entire project to work. Whereas the full client is designed with developers in mind, who do require the full project. I understand that this does pose a different problem where you are forced to download everything even if you dont want to.

    Cloaked.conf is what you would want for this. Please see the below snippet from here.

    Quote

    Cloaked items are items that the update operation won't download by default from the repository to the workspace. This is convenient in some scenarios, for instance when there are big files in the repository that are updated often, but you don't really work with them, so you prefer to skip downloading those cloaked files every time you switch the workspace to a different branch or do an update of the workspace.

    Hope this helps!

  5. I would suggest trying to connect with the Plastic SCM Cloud Edition Client to rule out whether the issue is specific to the Version Control package or not. If you are still seeing issues with the client then you can review the logs which can be found...

    • Here on Windows: %localappdata%\plastic4\logs\
    • Here on Mac: ~/.plastic4/logs/

    I hope this helps you track down the problem. If not, please reach out to us at support@plasticscm.com.

×
×
  • Create New...