Jump to content

ollieblanks

Administrators
  • Posts

    268
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by ollieblanks

  1. Hi Gabzzel,

    Thanks for reaching out.

    • The Repo URL field should be in the format "CloudOrgName@cloud". Once you get past this step and you set up Build Targets in Cloud Build you will select which repository and branch that you will build from.
    • The Username field should be the email address associated with your Plastic SCM account.
    • The Password field should be your password associated with your Plastic SCM account.
    • The Authentication Type should be set to LDAP.
    • The Encryption Method should be set to AES128.

    I hope this helps!

  2. The underlying cause of this issue has been fixed in release 9.0.16.4995.

    All platforms: fixed duplicated deletes after incoming changes operation.

    The incoming changes could leave a duplicated deleted directory. It happened if there were 2 moved files plus a delete of their source parent directory as pending changes.

  3. Hi,

    Thank you for raising this. I believe this should be made easier with a "Use another account" button (or similar) directly in the General Preferences pane. I will make this suggestion to the team.


    To change your logged in user when you have used Unity ID login, you will need to close the Plastic SCM client and run macplastic --configure in a terminal window. This should present you with the following window...image.png
    (Note: The command on Windows is plastic --configure and Linux is gtkplastic --configure)

    Hope this helps!

  4. Hi Stéphane,

    Thanks for reaching out.

    I suspect that you are using TeamCity version 202.1 or newer and you are experiencing an issue that has been recently reported. The fix for this is due to be released very soon. Please bear with us and I will update you here once the release has been published. 

  5. Hey @Luke Hedditch,

    Thanks for reaching out to us. This is unfortunately a known issue that we are currently investigating as a high priority.

    There isn't a currently known workaround at this time, but the plugin can be disabled in Rider by doing the following:

    1. Navigate to  File > Settings > Plugins in Rider.
    2. Find the Plastic SCM Integration plugin within the list of plugins and uncheck the checkbox.
    3. Click Save to save changes, a restart of Rider will be required.

    I will make sure to keep you updated of progress of a fix.

  6. Hey Scott,

    Regarding the EULA, I can assure you that Codice or Unity would never use anything for publicity purposes without given consent. I understand this is nice to know but does not directly address your legality concerns. Please refer to my colleague Francisco's comment above regarding this matter.

    Regarding your other queries. Please see direct responses to your questions below...

    Quote

    Will that work even if I have only one Unity ID?

    Yes, you can create another Plastic SCM account with another email address without linking it to a Unity ID.

    Quote

    I assume it would, and I would simply need to login manually to PlasticSCM depending on which Unity project I'm building? Does the PlasticSCM client remember my credentials globally, or within the project?

    The Plastic SCM client does remember your credentials, but multiple connection profiles can be set up for different Cloud Organizations/Projects. Additionally, the client can be completely reconfigured to use another set of credentials at any time by running plastic --configure command from command line. This is what I do with my work and personal accounts! ;)

    Quote

    If PlasticSCM remembers the credentials by project, then it sounds as if we might be better off keeping the PlasticSCM cloud account standalone rather than using the SSO feature. Do you have an opinion on this?

    Whether or not you link your Plastic SCM and Unity accounts is completely up to you. There are no real advantages or disadvantages either way. As time goes on there is likely to be further Unity ID integration efforts made, but we would never leave our non-Unity users out in the cold!

    Hope that helps.

    • Thanks 1
  7. Hi Scott,

    Thanks for your detailed questions. I hope I can do it justice with a detailed response!

    RE: Accounts and setting up...

    From the sounds of it, keeping the account you have already set up as your myself@personal account would be most efficient. This way you can keep it separate from your work account.

    I would suggest setting up another Plastic SCM account with your accounting@company, this way you could set up a Cloud Organization for your company and this account can be responsible for handling the billing and adding/removing other accounts. As long as this account never actively uses a Plastic client, you will never be billed for it. For more information on our pricing, please see here.

    If you do the above you would then have the following:

    • yourself@personal account that is linked to your personal@cloud organization
    • accounting@company account that is linked to a newly created company@cloud organization (which you could configure to use encryption)

    You would then be able to add artist@company, designer@company and yourself@company accounts to the company@cloud organization.

    RE: Unity ID account email change...

    Unfortunately, changing email address associated with your Unity ID currently stops any Plastic SCM linked account from authenticating in the Plastic client and website. This is an issue we are currently investigating. If you contact our support team, we can manually make this change for you.

    RE: Plastic SCM EULA...

    As you quite rightly stated, Codice was acquired by Unity very recently. Please see here the current EULA for Plastic SCM and let me know if there is anything that concerns you.

    Hope that helps!

    • Thanks 1
  8. Hi,

    Thanks for reporting this issue to us.

    Problem:
    Error message "Multiple precompiled assemblies..."

    Workaround:

    This error message is complaining about duplicate assemblies within the solution. Deleting one of the DLLs should be enough to workaround this.

    In my test...

    • Plastic SCM Plugin (Version 1.2) had Assembly version 3.5.0.2 of Antlr3.Runtime.dll
    • Bolt Plugin (Version 1.4.13) had Assembly version 3.1.3.22795 of Antlr3.Runtime.dll.

    After removing the older DLL both plugins continued to work as expected.

    Solution:

    We are currently working on moving the Plastic SCM plugin to be its very own self contained package managed in the Package Manager, which should alleviate incompatibility errors such as this.

    Hope this information proves helpful!

  9. Thanks for getting back to me.

    After taking a closer look at your screenshot, I can see that the script and meta files are both checked out (orange symbol). They appear in the pending changes list, even if they are not modified, because you have "Show Checkouts" checked.

    The only way I could produce this behaviour was by checking out a script file using the legacy Plastic SCM Unity Plugin (Project Settings > Editor > Version Control > Plastic SCM), this checked out the meta file along with the script file.

    image.png

    If you are interested in an Editor integrated solution, please take a look at the new plugin available on the Asset Store.

    Hope this helps!

  10. Thank you for reporting this. I've attempted to reproduce this behaviour to no avail. I did notice that the time for the Editor to load was slightly longer if I had the Plastic SCM plugin window open.

    image.thumb.png.f675e1af56f85235d7e707dd1b8d04ad.png

    Can you confirm if closing the window reduces the occurrences of this?

    Please can you also send us the below log files, which can be found on Windows here: %localappdata%/plastic4/logs/, and on Mac here: $home/.plastic4/logs/

    • unityplastic.debug.log.txt
    • unityplastic.relevant.log.txt
×
×
  • Create New...