You're welcome!

This is beautiful

Hi, you succeed with it?

Glad it was helpful!

When you say scene are you meaning a level blueprint? For example you created a small world with chairs boxes and other misc items and want to export the level with the object locations intact? Just to ensure I am understanding correctly

Taking a lighting setup or volume area and keep it's world position I am not sure. I have migrated a level with the placed actors and have found sometimes it stays and sometimes it doesn't. Haven't quite figured out how UE determines saving of world positions of different assets in levels. My best advice is to place your level and the lighting into a single folder and export them all together. Same with volume. But if you're trying to do without the level, that can't be done from what I understand as the world info gets built into the level info.

Check to make sure the lights are still set to static/movable or whatever you need them to be set. Sometimes the light settings get restored to a default state on migrating.

@@ArtofficialEntertainment Changing them to static fixed it. thank you

You need to make sure to migrate the materials and the models. And changing the file path means it can't find materials sometimes so once you migrate it just reapply it

If you are trying to export a single model you could try exporting it to an FBX file (by right clicking the object in the content browser, asset actions, export) then reimport the FBX into the new project.

When migrating you want to make sure that you just check the file path you want to migrate. So if you uncheck all other file directories except the ones you wish to migrate it will only migrate those files. If you uncheck the root then your disabling all content under it. You just need to uncheck the other files within the root or content folder and should be fine. As far as the screen size goes sounds like a possible canvas panel setting issue within the widget as you can set different aspect ratios from the canvas panel scaling.

Yes and no. Sequencer settings and added components may not carry over. Usually migration is used for direct assets. While it will allow you to migrate it I have found sometimes there is a data loss on things like sequences or PCG content.

When Migrating you can select folders and all the assets in the folders as well - Were just the folders checked or the folders as well as the content within the folders? Ive done this several times by accident and completely uncheck the root folder and just checked the folders i wanted not remembering that doesnt by default also check everything under the folder (For example: Folder named Props is highlighted but the Bps for Sword, Shield, Barrel are not checked and as a result will export the file but not the contents) If this does not solve your issue please feel free to hit me up on the channels discord so I can help further!

@@ArtofficialEntertainment thank you for the reply! I did solve the issue: i was trying to migrate files from a project using the current version of unreal into a project using an older version. To fix it, I made sure the versions matched before migrating the files. And problem solved! Hope this helps someone else who might be getting the same issue.

@@ArtofficialEntertainmentfor exAMPLE for me i arrastred the carpet of animations and solutions

Been saving for a beast machine. Gonna be upgrading to a 4090, 13900k, DDR 5 at 64. Laptop has a 2060 so I can dev just cant go beyond low settings while in the editor. I do not know for certain if DDR5 makes a massive difference inside of UE but for playing games it does so I'm assuming there has to be some performance boost even if it's minimal before things like Raytracing and all that. I think DDR5 is mostly future proofing at the moment

Technically yes but I always recommend caution when migrating assets to engine versions they aren't made for.

You are just migrating files from one project to another. Doesn't change the origin files or the overall project.

When migrating it's always going to double the memory usage as now you have 2 copies. I have almost 150 gigs just in assets let alone project files. 30gigs doesn't go very far in game design sadly

@@ArtofficialEntertainment might be but it worked fine now. It also doesn't seem to be an issue usually when packaging. It only takes longer but it doesn't crash the engine. ( also might have to clarify that i meant with memory the RAM. not my hard drive, i have meany of those and all hold TB not GB) The problem in the end was that it gave me a message that some root files where missing for some assets and asked if i wanted to migrate everything into a folder. So that it wouldn't loose those references. I picked Yes and that crashed it. I tried it another time without it and it migrated without any issues. Still have to see though if all the assets are working properly.

@@sam-psonsmith9951 sounds like the asset for sure then. I've had a similar issue and found some of the raw files were corrupted slightly, and another time the asset was labeled for UE5 but wasn't compatible at all and gave me tons of crashes. I plan on doing an asset trouble shooting video soon after I do some more research

@@ArtofficialEntertainment sounds great i am definitely gonna watch it.

When it says unable to determine what are you migrating? I have a new Discord server that if you want you can join and post some images or videos of what you are having an issue with and i can see what i can do to help :) Heres the link: discord.gg/rDH494Nu6R