Hey Guys,
i’ve been working in 4.18 for about 2 months solid.
I’ve got to upgrade to at least 4.19 for a few new reasons.
I went ahead and just went straight to 4.21 and I am wondering what is the best method for migrating “BluePrints” to a new Project?
My thoughts are doing screen prints but that’s tons of work, since I’ve got allot.
Please tell me their is a better way.
Regards,
.
Why don’t you just update your project from 4.18 to 4.21? Blueprints should not change in any way (I might be wrong though, don’t really remember the change logs that far).
But if you insist on migration, there is a really simple way of transferring assets between projects and actually you’ve hit the nail with the post title. When you right click any asset/folder inside UE4 editor there is section **asset actions **in which is a migrate option or if you are targeting folder the migrate option is in the main window after right clicking.
Based on redirectors it copies all assets that the specified asset(s) has listed as dependencies so if you want to copy let’s say an actor that has a reference to another actor and that has a reference to for example a blueprint interface, the editor will migrate the selected actor, actor that is referring to and also the blueprint interface to prevent any compiler error in your new project. This process is really quick and really simple to use, just select desired assets,right click -> migrate, hit OK button, locate content folder inside your new project and wait for competition.
But watch out for missing input or other project settings related reference, migration only copies assets with it’s dependencies. Also avoid selecting files and folders together it appears that there is no migrate option after right clicking.
Oh my Gawd, this is a dream come true. I was really for something like this.
Now I can realx and take it easy.
I cannot thank you enough, I thought i was going to have to use notepad ++ to copy the code and i had no idea what I was going to do to migrate the BluePrints.
Thank You !!!
Ok, Looking at the Migrate option on the right click, and it just seems like you can only migrate folders within the /Game that is loaded up.
I don’t see any way to migrate the folders to my other project that i created using 4.21?
, am I missing something here??
I tried to copy over content folder over to the new engine project (4.21) and for some reason that did not work.
I also tried to the “source” folder (public.private) since I have a few thousand lines of code from my (4.18) project, but I then see that i have to add each new item in the solutions explorer.
I am not sure if I can get this to work by copying things like this.
I really hope i don’t have copy the c ++ code to notepad ++ to the new project, but at least that’s an answer.
Not sure what i can do with the blueprints? Not to mention all my custom materials and stuff like UI.
There has to be a better way than this?
After copying BluePrints over and then trying to open them up, i get this error message…Daaayumn…
Blueprint could not be loaded because it derives from an invalid class. Check to make sure the parent class for this blueprint hasn’t been removed! Do you want to continue (it can crash the editor)?
C++ definitely complicates things and honestly I have no idea how to proceed with this, sorry. From my experience migrate function works great with pure blueprints setup but when custom C++ classes get mixed up I don’t believe that UE editor will handle it and my knowledge only extends to using plugins in my BPs.
I would really suggest you to just change the engine version on your 4.18 project (don’t forget creating backup just in case) it will probably introduce some new errors before you can successfully compile your solution but it beats copy-pasting all of the stuff. You can switch engine versions in windows explorer by right clicking on .uproject file. At the end, the compilation will probably fail so you will need to do it manually in your IDE and that should be all hopefully.
I’m sorry that I can’t help more, good luck.
That’s Ok ", you where kind enough to reply.
I am just going thru and migrating the c++ code along with other things.
The thing is this, if you create a project in a previous engine version, you cannot open it with a later version since the code was compiled with a previous version. I don’t think there is a way around this.
So, that being said and me being mindful that others are reading this too, I am just going to go thru and create the c classes again adding them to the new project and pasting the code in from my source. I have copied all the content into the new project.
It’s not that bad, but I am not sure how i feel about doing this again, seeing as there will be even more to sort thru.
How does everyone else do this?
Regards,
.
Ok, wait, it says I can “Convert in place” when I tired to open the previous project that have been working on. This might be the answer!
, I have magnificent news! Epic I must take a Bow…
After you install the newer engine, you open it and it will ask you if you want to “convert it place”, i picked that.
I open the solutions files and Epic is so on top of this that it makes new ones for the new engine.
Everything Compiled and there are no errors!
Wow, I am truly amazed and RELIEVED…
Regards,
.