Created new work space but one file is missing!

[Stephen Taylor]

Hi,

 

One of our artists has created a new work space and in one folder a particular .mb file isn't present, all the other .mb file are present.

t's there if they browse the repository at the latest changeset submitted to main.

There is no mention of this file in any ignore, cloaked of hidden_files file.

If we look at the history of the file from the browse repository then non of the file changeslist numbers are in bold.

There is nothing in their pending chnages. I.e no deletes.

Updating the workspace doesn't fix it.

Adding a new file to this folder and merging from main and it appears fine.

What could be causing this?

Thanks,

Stephen.

[calbzam]

Hi,

If the artist, is using Gluon, they can customize the files to download via the "configure" button. If a file/folder is not configured, it won't be downloaded when you run an update.

Please review in the "configure" panel if the file appears to be configured and if after selecting the file, the artists is able to download it.

I guess other artists/developers are not affected, right? I mean they all can download this file.

Regards,

Carlos. 

 

[Stephen Taylor]

Hi,

They are using Plastic SCM not Gluon. Is there a plastic SCM equivalent? 

What else could cause this in Plastic SCM?

[calbzam]

Ok, sorry. If the artist is using Plastic GUI, if he/she opens the branch explorer --> browse repository in this changeset --> select the file --> Save revisions as.  Are you able to save the file revision in your disk?

If a different artist from a different workspace runs the same update, are you reproducing the issue?

Regards,

Carlos.

 

 

[Stephen Taylor]

If she does as suggested above the file appears locally as a private file. It still doesn't register it already being under plaster source control.

Different Artists aren't getting this issue.

Thanks,

Stephen.

[calbzam]

If you are able to "Save file as...", it means the revision content is correct in the database, so something should be preventing the file to be downloaded during the update operation. Could you check if there is a cloaked file in one of the following paths?

1) Workspace path.

2) C:\Program Files\PlasticSCM5\client

3) C:\Users\xxx\AppData\Local\plastic4

4) Do you have a "plastic-global-config" repo where you distribute a "cloaked.conf?

Regards,

Carlos.