ollieblanks

Hi, I believe the command you want is cm showselector. To find out more about this command please type in cm showselector --help. Hope that helps!

Hey @RichardNightschool, The easiest way to "Undelete" a file, is to create a Gluon workspace for your repository. In the Gluon GUI, there is a specific Undelete function where you can select a file and restore it. Regarding History in Diff window, that is some great feedback! Unfortunately, the History of a file is only accessible via the Workspace Explorer and Pending Changes views. I will share this Feature Request with the Product Management team, as it would be a great improvement.

Hi @RichardNightschool, I have attempted to reproduce this behaviour to no avail, which means that there is something environmental to your repository/workspace that is causing this behaviour. Perhaps a file that is changed that is not picked up by the "What To Show" options? After you do the first switch, what does the CLI command cm status --all return?

Hey @joevin, Apologies, but I am a little confused about what it is you are trying to achieve here. Can you please elaborate on what it is you are doing and maybe provide an example? Look forward to hearing from you.

Just FYI. This change has been made and will be in the next release! Thanks again for requesting it.

Thanks for logging a support ticket as requested @Ahmet YILDIZ! I believe the reason for this behaviour is because Cloud Build requires some extra setup with Plastic SCM, which was not required with Collaborate. To resolve this, you need to navigate to the Config page and reconfigure your Source Control settings to point at your Plastic Cloud organization. Once this is done you also need to edit your Build Target's Basic Settings and select your Repository and Branch that you would like Cloud Build to build from. Hope this helps!

I suspect this was due to a transient outage in one of the Plastic Cloud regions, which is now resolved. If this issue is still ongoing, please reach out to us at support@plasticscm.com with your project ID and we will take a closer look.

Hi @Gardenfiend Games, Sorry to hear this has caused you headache. I agree the wording could definitely be improved. Just FYI, if you would like to share cloaked.conf rules with your colleagues, you can do so by adding a cloaked.conf file to your plastic-global-conf repository. Regarding your suggestion to rephrase the button text, my suggestion would be to rename this operation to "Apply rules to all MY workspaces". I'm interested to hear what you think. Do you think this would be descriptive enough or could this still be interpreted incorrectly? Thanks for raising this feedback!!

Hi @stijn, Please can you try the following? Navigate to the Services Window and disable the Collaborate service. Restart the Editor. You should now have access to the Plastic SCM window via the Window > Plastic SCM menu option. Hope this helps!

Hi, Sorry to hear that you are experiencing this issue. What is the behaviour that is blocking you from configuring your credentials? Can you please share screenshots? Are you able to run the below command in a Command Prompt window and use your Unity ID for authentication? On Windows: plastic --configure On Mac: macplastic --configure Hope this helps.

Hey Stephen, Sorry to hear of this behaviour. I can't be sure of the steps you have taken to get to this state, but it sounds like the workspaces may have been corrupted somehow. A quick and dirty workaround may be to create a new workspace. If this is not helpful or you would like us to do some deeper investigation, please log a support ticket via support@plasticscm.com.

Hi @Mub_Dev, Please do not upgrade to version 2.0.1 of the package. This is an experimental version of the Collaborate package that does not include Plastic SCM. The version you want to use that has Plastic SCM integrated is 1.15.x. Hope this helps!

Hi @disola, With the current migration wizard, you cannot select which Projects you wish to migrate, but you can with the legacy migration wizard: https://www.plasticscm.com/plasticscm-cloud-edition/migrate-unity-projects/unity-login?allowLegacy=true Hope this helps!

Hi, Thanks for reaching out. Newly added files are given the status private until they are checked into your repository, at which point, they become controlled. Added and Private files should be selected by default. So it should just be a case of checking in your new files. Hope that helps!

Thanks for logging a support ticket for this issue. Together we identified that the issue was due to a mixture of Polish and English Windows Language/Region settings.

Triggers are designed to be synchronous to return an outcome to the client with the possibility of action, but since 10.0.16.6280, you can now spawn a child process and the GUI does not wait for it to complete. For example, this could be done with the following line in a batch file... start /b run_trigger.exe Hope this helps!

Hi @AlanMattano, Is it because there are no changesets since 15 November 2021? What happens if you change the date filter at the top to an earlier date? Hope this helps.

Hi @ManjitB, Thank you for raising this. I have reproduced this on the current Mac client. We are actually working on a new cross platform GUI, where this issue is not present. This new version is already released in the latest Plastic SCM installer, if you would like to give it a try. The default locations for this new GUI are: On Mac: /Applications/PlasticSCM.app/Contents/Applications/PlasticXSCM.app On Windows: C:\Program Files\PlasticSCM5\client\winplasticx.exe On Linux: /opt/plasticscm5/client/linplasticx Hope this helps!

Hi @stryfe86, Thanks for reaching out. It sounds like Plastic SCM Cloud Edition would be a good solution for you. With Cloud Edition you can host your repository in the Cloud and both your workstations can have separate Workspaces configured to work with this repository. For more information on getting started with Cloud Edition, please check out the video tutorials at the bottom of this page. Hope this helps!

Hey Steve, I see these error messages in the log you sent me... Error message: These items are exclusively checked out by ... Does the user have multiple workspaces? Perhaps, these files are checked out in another workspace for the same user? If you are still having issues with this, please open a ticket with support so we can troubleshoot further.

Hi @SteveEverCurious, Thanks for reaching out. RE: Item cannot be moved because it cannot be found. As the error suggests, it seems that Plastic is not able to find the folder to merge anymore. I suspect this may be because it was deleted and/or recreated and therefore given a new GUID identifier. If you are able to reproduce this issue, please can you let me know the exact steps so that I can investigate here in our labs? RE: User with files checked out that they can no longer check in. Do you receive any error messages in the client? Is there anything in the log related to this?

Hey @Joevin, This is because you are only reading the first line. If you want to get the entire standard input as one long string then please use... Console.In.ReadToEnd(); Hope this helps!

Thanks everyone for the feedback! Its great to hear about people's plights with the tool so that we can review and improve. @Mikael Kalms Thanks for clarifying this request. I believe this would not be a trivial task, but a very good addition nevertheless. I will raise this with the team! @Oyvind, reverting a hunk of code can actually be done in the in the diff view that is nested in the Pending Changes view. Hopefully this is helpful to you. @Energy0124 As I mentioned above, a merge operation is an atomic transaction at the Changeset level (meaning it is "all or nothing" operation) for traceability and performance reasons. Are you able to give a bit more context about how Git does this better?

Hi, If you are using C#, you can use Console.In to access stdin. Or Console.ReadLine() which is just a shortcut for Console.In.ReadLine(). Hope this helps!

Hi Alan, Thanks for raising this feedback. I have already addressed this in this thread, but this term is something that is used for Cloud Edition (where "Organization" makes more sense) and in Enterprise Edition (where "Server" makes more sense). I agree that this could be made a lot more clear for Cloud Edition users and will be sure to pass this along to the Product Management team.