CathyN wroteWhy did you update the .atlas.txt file?
Sorry, I just noticed that this was ambiguous. What I meant is: "why are updating the .atlas.txt
file (copying them over the existing ones in the project) but not the .png
files?".
CathyN wroteSo when I look in my Perforce, both the .skel.bytes and the .atlas.txt are marked 'dirty' but not the .png's (even though they are updated at the same time as .atlas.txt ?).
Here it would be very interesting to know whether the png files are really unchanged (binary equal) or whether your Perforce UI did not list them or update their state.
CathyN wroteI guess the lesson here is to uncheck that atlas box on export OR then the .atlas.txt updates, the png's are required to update with it.
If the png files changed and were not listed as modified in Perforce, I would highly recommend to check with a programmer of your team why Perforce is not listing them as modified. Otherwise you will eventually miss to submit important files with your changelists.
Regarding uncheck that atlas box on export: You could disable it when you are sure you did not add or remove any attachment images. This would also help to reduce size of your submissions in Perforce and create less "background noise". Just don't forget to enable it again when necessary.
Regarding updating: yes, please always update .atlas.txt
and png
files together.