So, it migrated, but there is a lot of broken stuff still and I can’t test it. I figured out what breaks the migration though
if I click Yes on this, it breaks. Clicking No allowed me to migrate, but my character is all broken.
Blah.
Ahhh… an old chestnut.
Close up all those boxes on the migrate dialogue, and uncheck everything except your stuff
Yeah, it imported, but still a broken character. Mostly the animBP. Gonna try to fix
I don’t know why this would break, or where my body/head stuff went. lol
That, I’m not sure about…
Yeah this is a very odd thing to break… meh. I might just have to wait until they update or the template i’m using updates and try to create a fresh 5.1 from the template and migrate to that instead.
It has something to do with my defaultengine.ini settings or something. Either way, too much is broken for me to try to fix everything. 
Hopefully this performance migration bug gets fixed.
I fixed the physical material bug, but now i need inputs. grrrr
I got it mostly working, can test fps now, 1 sec
It maybe runs 10-20% faster but at the same time now my lighting looks super weird and my textures are doing some odd warping… trippin balls man lol. Either way, thanks for the help, gonna keep trying at it.
1 Like
Ah some progress, jolly good 
1 Like
Yeah, some other small stuff got broken but I think you cracked the code with the migrate stuff. Sucks we gotta go that route though. Thanks dude. Glad I can at least experiment with 5.1 now lol.
1 Like
Experiencing the same issues. What ran 40fps in 5.0 now runs 20fps after removing foliage…it’s pretty awful. I thought their target was 60fps for 5.1 with Lumen…
Like, 60fps on what, a scene with nothing in it?
Has this been bug reported?
Same here, after testing 5.1 for a few days decided to stay on 5.0.3 until this issue is adressed. Here we found other issues after the update to 5.1, such as blueprints reseting and actors with wrong variable values. It is so strange that we decided not to update to 5.1 for now. Hoping it is fixed by 5.1.1
1 Like
Ok well, I submitted a bug report for this. It would be helpful if you all who are experiencing the issue could do the same as thing as well (bug report form: Unreal Engine Community )so that the issue gets addressed ASAP
I never reported the bug, but hopefully they are aware of it.
lol how will they be aware of it if it is not reported
Hi, we have a similar issue.
We used to run DX11 on 5.0
After migrating to 5.1, we tried DX12 like they recommended - our FPS dropped by 50% so we reverted back to DX11, while that was significantly better, it still seems somewhat less FPS than what we had on 5.0.
I think that Lumen specifically takes more performance now…
And yes, we have also had an issue with some BP variables resetting after the upgrade from 5.0 to 5.1, but we’ve managed to find workarounds to fix this.
We’re also experiencing the issue of worse performance in our project after migrating from Unreal Engine 5.0 to 5.1.
I’ve looked into it a bit and it’s quite fascinating. At least in our case, the GPU thread has exactly the same performance as before.
However, the Game thread now runs twice as fast, while the draw thread takes + 3.5ms, becoming the bottleneck and causing the lower framerate.
It looks to me like occlusion culling could be part of the problem? The frame time for that seems too high at ~4ms.
All things considered, I wonder if it could make sense to run a “difference” test between a default UE 5.0 project settings file and a default UE5.1 project settings file.
IF the project settings are really the problem, then technically the two files should show differences in a text comparison.
Migrating a 200+GB project manually and setting up source control again whouldn’t be an option, at least in our case.
2 Likes
Same here as XilenceX, I’m the only person on my team with the problem though, and doing that with our 130 gb project with source control just for one person would be impractical.