Hi All,
I’m use to work with medium size project. Always make a copy in case all goes wrong…
But, with UE4.27, it doesn’t work ??? When I’m satisfied with a part of program I made, I close everything, laucher included, and just make a copy of the whole project directory. Change .uproject extension to .up, cos laucher search everywhere and mix up projects (???)…
When I want to recover this version, I have plenty of compiler errors and editor won’t load the project.
I know I can delete all pch files, but what do I miss ???
What is the correct way to make safe copy ?
TIA,
Robert
1 Like
Hi,
I’d suggest you to use some version control. I use Git.
https://docs.unrealengine.com/4.27/en-US/Basics/SourceControl/
.gitignore:
https://www.toptal.com/developers/gitignore/api/unrealengine
2 Likes
If you don’t feel like setting up source control (that’s the best option), you could create an archive instead of renaming the uproject file.
I sometimes use WinRAR to backup my test projects that are not worth setting up a git repository, remember that you don’t need to backup the Intermediate and Binaries folder since they get automatically generated when you open the project file and they could be kinda heavy
2 Likes
Ares9323, Thanks for suggestion.
Maybe a way to bypass launcher behavior of searching everywhere instead of just working dir…
2 Likes
Hi Solid Sk,
I looked at source control, but there is no detail as to where they keep a save version for fallback…or I don’t read well 8|
I found two reasons for error message, one, when copying files, windoze automatically make them “read only”, need to take that out. (and to all subfolders)
Second clue, before copying or retrieving, need to insure that unreal and launcher are completly shut, cos they sometime keep files lock, even if not working on them.
The reason I’m using copy is that it is (supposingly…) full proof against corrupt windoze or engine, drive fail, etc…My copies are on different medium.
Source control is literally updated everytime you commit new files, so, every commit is indeed a fallback (you can go back in time through the commits and find out which one broke your code)
3 Likes
I’ve never noticed that option despite I’ve packaged hundreds of times 
Does it exclude the Intermediate folder automatically?
1 Like
Thanks All for the options, I’ll dig into it and test their robustess…(Sorry for language mistakes, I’m french 
)
