After making small changes to my map like for example adding grass to stand on or if i just make settings changes on a device i cant save any of my changes and i cant launch a session. a popup says “Unable to play” “Dirty assets could not save” What are dirty assets and how do i prevent this from happening?
Solution:
The “dirty assets could not be saved” problem is caused by OneDrive. Make sure your OneDrive is either completely removed from your PC or that you save your files outside of the OneDrive folder. I just deleted it never checked my files, and for two very long years I kept encountering problems I thought were unrelated like the error “An error occurred. See inner exception.” It turns out my OneDrive file was still on my PC and my Documents, Downloads, and Desktop files were inside that folder. (Despite me uninstalling OneDrive)
To fix it and make sure OneDrive doesn’t cause problems, go to File Explorer > This PC > Local Disk > Users > Your Username (whatever your name is on your PC) > OneDrive. Open the OneDrive folder and move the Documents, Desktop, and Downloads folders out of it and into Your Username folder.
After that I deleted the OneDrive folder, but I don’t think you have to delete it. Since then, both the “dirty assets could not be saved” and the “inner exception” errors have disappeared
I have encountered this same error the moment i tried launching the session, i haven’t found a solution to this problem, if this is an issue on Epic’s end then i hope they fix it ASAP!
Hey all I just encountered this error a moment ago and after messing with things I noticed the revision control in the very bottom right corner was able to be interacted with so I clicked on it. Upon clicking on it I noticed it was inactive for some reason so I activated it and it saved all changes made then there was no longer any issue.
this problem can’t to be fix it ? beacause it’s really rage i can’t save any thing and when i leave i find every thing delete and i must build it again
Hey @SugaryMadness , yes indeed. Having 2 different source control system fighting for the same files can cause conflicts like dirty assets.
We make a small reference to it within the best practices documentation that can be found here:
stating:
Do not enable multiple revision control methods outside of Unreal Revision Control, enabling multiple revision control or backup systems on the same project/location in your filesystem can end up causing unexpected behavior since there won’t be a clear source of truth for either to reference.