5.4.2 performance is so bad that I can’t get anything done at the moment. I’d like to be able to roll back to a version that wasn’t freezing every second or two, but can’t find where I would do that.
Afaik 5.4.2 and 5.4.1 should be compatible. Just change the engine version you are using.
If you wanted to switch to 5.3 or earlier, that would be problematic, unless you are using a versioning system.
I’m just unclear on how to get 5.4.1 at this point. The epic launcher updated me to 5.4.2 and has no option that I can find that would let me revert.
Hey there @gs_poopacabra! Welcome to the community! Minor version changes (for example from 5.4.1 to 5.4.2) are often primarily bugfixes and shouldn’t (while unlikely it still could) have introduced a major performance shift like this. So when installed via the Epic Games Launcher, Unreal Engine installations automatically update to the recent hotfixes (not full version changes however). That said I would usually advise checking other avenues such as environmental factors before deciding to make a source build if you’d never done it before.
If you were to still want to just go back one hotfix, you’d have to build the engine from source without this hotfix. Linked below are how you can get permissions for the Github repo and the releases page once you have.
https://www.unrealengine.com/en-US/ue-on-github
(This on will be hidden until you have permission to see it)
https://github.com/EpicGames/UnrealEngine/releases
I’m making cinematics, so no build required. This is editor performance, in all windows. It takes about 30 seconds to a minute to connect two nodes in the material editor. I guess I’ll wait for the next release.
The build I was referring to was the engine itself, not a project. Specifically you could return to version (and have it locked at) 5.4.1 as per your original request. However I was also noting that the performance issue is not likely from the hotfix itself, but likely 5.4 in general.
This thread has a number of workarounds/solutions to the possible causes of the issues stemming with 5.4 originally that may help:
1 Like
Turning off Studio Telemetry seems to have solved my issues.
1 Like
Thanks for the update and awesome work! It seems Studio Telemetry has been causing issues for a significant number of users. Was hoping to link something to the issues page, but it doesn’t seem like there is a corresponding issue. If you have a second and wouldn’t mind, could you submit a bug report with your specs? Having trouble correlating what environmental factors cause this issue and I can’t personally replicate it or I’d submit it personally:
You can use my plugin Asset Downgrader if you want to go back to 5.3 or lower versions.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.