I wonder if is it possible to downgrade the project version because I’ve done some days of improvement after upgrading, but I’m not able to find a solution nor have it been fixed.
But I’d rather have it fixed because the nanite weren’t working for me in the earlier version.
The ones I found some far that weren’t present in the earlier version:
-foliage appearing and disappearing constantly (leaves)
-groom unbinding every time I restart
Hey @Lucavall!
Unfortunately no, you can’t downgrade a project’s version. Hopefully you backed up your project, before upgrading? 
2 Likes
If you are using a versioning system, yes. If not you may be out of luck.
Code is forwards and backwards compatible but the engine marks content like materials and especially blueprints with a version number which makes it so they cannot export to a previous version.
There could be a workaround but I’m not aware of it.
1 Like
I still have the last version backup, maybe a week ago, I’m not familiar with versioning system. I just didn’t want to lose the increments I’ve made recently. At 5.3.1 I don’t know if they would fix these in 5.3.2 or something, so maybe I should use the backup, I’m not sure.
In my experience, if binary files are not modified by the engine with a new version, a downgrade is possible. I did it sometimes. But, if my memory is correct, if binary files are modified, for example, you open some file with the engine with a new version and save it, when you try to downgrade, you would see some warning or error message.
You can now downgrade assets using my plugin ( Asset Downgrader | Fab ) all the way back to 4.27. There may be some issues like missing blueprints nodes that exist only in newer versions, but for anything else, just report them to me and I’ll fix them.