[Plastic showing status Changed when files are identical]

6 hours ago, calbzam said:

Hi,

This is a local client configuration setting (not configurable on the server-side). By default, the "Pending changes" is not checking the file content (only the timestamp), because it would take a very long time in big workspaces with slow disks. Checking only the timestamp is very fast.

Anyway, if you try to check in an item that appears as changed in "Pending changes" but the file content is actually the same (not changed), Plastic won't create a new file revision in the repository.

Regards,

Carlos.

I understand that but for consistency issues having items which are not really edited in that list will certainly cause needless misunderstandings. Not only that,  but it litters the changes list so it's hard to gauge what you've truly changed. It is be something that now will have to be explained to every new team member.

[Plastic showing status Changed when files are identical]

1 minute ago, calbzam said:

Hi,

Is it possible that the file timestamp has changed? You can change this default behavior If you open the Plastic GUI --> Preferences --> Other options --> Check content to set a file as "Changed".

Regards,

Carlos.

Yes, that did the trick!

 

Is there any option to set this on the repository level itself? Or does every team member have to go and tick this in their client's preferences?

[Plastic showing status Changed when files are identical]

I got an issue with a bunch of files that Plastic marks as Changed even though they appear to be identical when diff'd.

 

It can happen with multiple files (.asset settings files or materials). What's going on?

 

 

[Item path not in workspace]

Yes, that's exactly that. I can share it with you privately, as it's a commercial project.

[Item path not in workspace]

Hey everyone!

 

I've recently created a new repository by using git fast-export and upon switching to of the recent branches [from /main which was obviously empty) I got the following message:

And then:

 

Is there anything I can do to find the culprit file and see what this is about?