Jump to content
Sign in to follow this  
prog112

Plastic showing status Changed when files are identical

Recommended Posts

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

S7dpoPi.png

4ZiUAyG.png

 

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

 

 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...