One day I went to the editor version control and it showed a bunch of random changes I have no memory of. Dozens of changes that might have been from a long time ago.
No problem, I’ll just reset to the last checkpoint. Except after I reset, the random changes came back to the working directory. They keep coming back even if i switch branches or do a hard reset to a checkpoint on a branch. I am very familiar with git (which I assume PlayCanvas uses on the backend) and I’ve never encountered this behavior before.
I can’t do anything with this bug. It’s a complete showstopper. I can’t even commit the new unwanted changes as it just hangs when trying to create a checkpoint.
Now that I look at it, yes, a good portion of the changes related to changing material tints. there also appears to be a ton of new PNGs created. here’s some screenshots.
anecdotally: would be really great if we could somehow use vanilla git that doesn’t go through your middleware. as it’s extremely slow at diffing, committing, reverting, etc. whereas vanilla git is super fast at all those things.
That does explain the material changes. I will try to commit the changes by creating a checkpoint. The last few times i tried this, it hung forever. I’ll try again now but I suspect the same thing will happen. It just stays stuck on loading “creating checkpoint.” I think if you absolutely had to make this change, messing with people’s files wasn’t the best way to do it. It’s really disruptive.
Does it also explain the changes to images? Version control is telling my a ton of JPEGs and PNGs were created or changed. See attached screenshot.
p.s. it would really really really be helpful if you could go back to old versions of PC and stay there via project settings. Right now the editor just has settings for the last 3 updates I believe… and I think it might even auto-update to the latest. This creates an incredibly frustrating enviro to develop in. As the rug is constantly pulled out from under you with new automatic updates to PC engine that breaks stuff. It’s at a point now where I am considering rebuilding everything in a different editor and exporting to playcanvas, because I’m stuck with the proprietary editor that is extremely limited.
So that sRGB flag is for the upcoming switch from Engine v1 to v2 in the Editor as mentioned in this post Engine Release v2.0.0 so those changes are safe to merge. As the checkpoint creation hang are there any console logs?
Unfortunately due to updates in our Engine API we cannot support older settings versions however we will discuss solutions to mitigate breaking existing projects during updates.
Was able to delete some old files and free up space. TY for the help!
and please do consider allowing us to go back to old version of PC. It’s really difficult to develop in an enviro where the ground is constantly moving underneath you.
Your core audience is developers … Developers like options. Now if you must have the editor itself on the latest version, but an additional setting to change the version for when you launch the game, even that would be a lot better than the setup you have now. I just can’t wrap my head around why this wouldn’t be a barebones option.
