Patrice Beauvais

Hi, It seems to be. We asked if they could add a merge option because it can happen frequently with External actors in Unreal 5, but I don't know if they are evaluating this or not. You can use the interactive resolve in cm merge and do that process automatically (copy the destination folder into the source folder and then commit the merge)

Any update on this bug? It's a real blocking one, you cannot merge a branch or check history of files. I told everyone to go back to Old Plastic client for now.

If you are using Unreal, the newer Unreal Plastic plugin should help (Check release note of 1.5.0 at https://github.com/PlasticSCM/UEPlasticPlugin/releases). It should notify that a newer version in another branch exists. It adds a bit of delay, but it seems to be helping.

Hi, I already sent a support ticket about Evil twin merge in PlasticSCM vs Unreal 5 one-file per actor (ticket #31359). This is a workaround to merge files from two branches when there's no file collisions. I really need to to automate that since there's no way I ask content creator to do manual merge with random folders and filenames (ex: 1\NT\PTHJ3ING96DMZW8M10UG4I.uasset). When there's no collision, there's no real reason to block from merging two folders, that should be built-in in my opinion, but it's not. Anyway, my the solution works and is live for couple of weeks. I just need all the fields description to support all the use cases. Thanks Pat

It's not exactly what I'm trying to achieve. Right now, I'm merging the two folders files by taking source and readding destination when the conflicts is not on files. This works well and make it possible to use One file per actor in Unreal 5 with PlasticSCM. But in any case, is it possible to know about the fields? Is there any documentation about it somewhere? My assumption is that True is Directory vs File, but I wanted to be sure. Thanks, Pat

Hi, Yes, exactly, I'm using it in our own tooling as a workaround for Evildirtwin. I'm not trying to automate everything, we more specifically the EvilDirTwin. But I want to better display to the user when he needs to do in Plastic UI. Thanks, Pat

Hi, Is it possible to know the list of possible fields that "cm merge" can return when using --machinereadable? It seems to by dynamic based on the conflict type. For example: DIR_CONFLICT||EVIL||Evil twin conflict||An item has been added on the source and on the destination with the same name, and they are different items.||Added /Wwise/Actor-Mixer Hierarchy/_TMP.wwu||Added /Wwise/Actor-Mixer Hierarchy/_TMP.wwu||2286698||False||ADD||/Wwise/Actor-Mixer Hierarchy/_TMP.wwu||ADD||/Wwise/Actor-Mixer Hierarchy/_TMP.wwu FILE_CONFLICT||/Plugins/UPG_OnlineCore/Source/OnlineCore/Private/OnlineManager.cpp||13774||13954||13829||330243 First line, what is the "True" meaning (pos 8)? Second line, all those numbers? It would be good to know the possible types and the returned fields. I did not find it with "cm help merge" neither in documentation. Thanks, Patrice

Hi, About the hosting of that script: if you don't have a NAS or something in common for all your users, you can put it in the [plastic-global-config] repository. This will be automatically downloaded to "%localappdata%\plastic4\globalconfig\[the server name]" folder and you can make your trigger refers to that folder. When you update it, people needs to restart their plasticscm client. It's not perfect, but it can do the job maybe. Thanks, Pat

cm status --header is not bad too since it returns the last synched changeset at same time too..

Hi, Is there a way to find if a file was added in another branch? I was using "cm find rev", to get the revisions of a file, but this only work if you integrated once the file in the branch. I tried with serverpath, but you need to pass the branchspec. I tried with cm find revisions where item ='', but with no success. Thanks, Patrice

I agree on what David said. On our side, we need something more like "Keep the last X revisions" and erase the old one. The feature is still interesting if we need to keep the old one. But, our use case is on large raw data that we don't really need a long history.

Hi, we would really need this feature too for our Raw data repository. Our binary assets can become very large and we don't care about old history (we would keep the last X changeset). Personally, I like the comment above on Perforce, I think it would work for us. Do you have an ETA? Thanks, Pat

It's strange since I have Blender preview by default without doing anything. But I'm not able to use the Preview tools... it's just not displaying anything and no debug logs. When using the same command lines in cmd.exe, it works, but inside Gluon it fails to load (Irfan or ImageMagick)

Hi, I do it here by having a "before-clientcheckout" to warn the user if the file version he has locally is not the latest across all other branches. The user can decide to work locally or not. And I have another trigger "before-clientcheckin" that blocks if it's not latest. I use "cm hist rev:thefile" to get the latest revision on a given file in all branches and "cm ls thefile --tree-br:/mybranch" to get the local file revision... then you compare the two. I skip if it's a new file or not in the lock file list.

Hi, Great point, I have the same problem here where I do a custom popup asking to the user to confirms that he really wants to update the file X... so if he says "no", I return 1 and it shows an error popup... It would be nice to be able to return another code or disable it.