I am using Perforce for version control. In the process of making some changes to some assets/blueprints/etc., I noticed I now somehow have unsaved changes to my map. Saving of course asks to check it out from version control.
There is an option to diff it with the depot version, but nothing helpful is presented (P4 Merge just brings up a few lines of text that are identical between the two map files). Is there a workflow to determine what I changed in the map?
This specific scenario was unimportant, but I’m thinking ahead to future workflows. How can I determine if I accidentally moved an object, deleted something, etc?
Interesting, thanks for the response. I’ll have to do some more experimenting to figure out what scenarios can end up with edits without prompting for checkout, or what non-viewport type changes can result in needing to resave/submit.
My worst fear is an accidental hotkey press (e.g., wrong window in focus) and doing something I didn’t realize to the map, then being unsure of why there are changes – I might discard updates I need if I ignore the changes, or might update something unintended if I do.
It makes me wonder if the undo log has some way to filter it down to actions taken to a relevant asset, like the umap. That could help identify what was done as well.
Why do you have such a fear? Don’t you already upload your progress on milestones? That’s the whole point of version control.
Though I should add that just connecting your project to version control isn’t enough to be safe. I’d recommend also having backups of your project and storing them somewhere safe.