Snap and Static Mesh Functions Causes 5.3.2 to freeze


Every time I create/open a project and click on either of the Snap Functions (Grid or Size) or if I click on Static Mesh dropdown, UE 5.3.2 freezes totally. I can only close it by going into Task Manager to end task. Even then, I cannot re-open UE unless I completely reboot. I am using Win11 (latest release) and AMD Ryzen 9 7900X 12-Core Processor (drivers to latest update). Any ideas?

Hey there @StonePlank! Welcome to the community! Do your logs for last session this occurred show anything? Could we take a look?

They are located in your project folder:
UE5 Projects\ProjectName\Saved\Logs

I’d be happy to share the logs for three test projects, but I cannot upload them in the forum. I get a notification which says “New users cannot upload files”. How do I share these?

Ahh yes, new users are limited as it helps filter out spam bots and other malicious actors. I’d recommend posting it through a pastebin or similar site.

Posted on Pastebin under title: UE5.3.2 Snap Function Freeze
I posted the entire log for one of my projects, but no project I’ve created works. Unfortunately, the code lines did not carry over using CopyPaste and I could not figure out how to make that happen. If this is necessary, I need instructions on how to do that, please.

Oh did the formatting break? Might be a bit terse to read but I’ll be keyword searching regardless. PB usually does retain source formatting so that’s a bit odd. That said, PB’s search isn’t really viable, so usually when linking someone you just give the last slice of the URL, for example: the TAyNM4F here.

image

I was unaware of the search limitations. Here is the URL: https://pastebin.com/K5SMXVgv
I also noticed that PB added the code line numbers after my cut&paste. I never used this site before, so it was new to me. I hope this information helps?
What do I do if no one sees an issue in the log? I have check all software versions and drivers. The computer is brand new so I know it is not a hardware issue. I built this PC specifically to use UE5. If this cannot be fixed, why and what are my options? Use UE4?

No worries haha, you actually did have the paste itself set to private so no one aside from yourself could view it currently!

If the logs don’t point to anything specific, you’ll just have to run through some generic fixes, which I have hundreds of. More trying to determine what portion is failing before I run you through a gauntlet. Though I’ll list the standard ones first:

If the issue is install based (ie corrupted file during install/build):

Reinstall or verify the engine inside the Epic Games Launcher or if you built from source, rebuild it and check for errors in the process.

If the issue is GPU sided:
You may be able to reset your GPU settings to default (I know this is redundant because you just built it).

Do you have a high DPI monitor?

The PB post is set to Public, but I noticed that it is Pending Moderator approval. I would be happy to drop it somewhere else or email it if you have suggestions as to where.

I have already reinstalled Epic Launcher and UE5 as well as Visual Studio (just in case) multiple times with no change. I also tried Verify UE5 as well. Still does not work.

GPU setting have never been modified. I am not sure how to adjust anything back to Default. Happy to try that but need to be pointed in the right direct on how to do that.

My monitor is 2K and not 4K, so not sure if that constitutes as high enough DPI. Here is the data on this:

@SupportiveEntity - should I issue a bug report? I searched the forum and saw a couple of similar, but not exact, issues. I really need to get this working or I cannot use UE5 - and I cannot believe I am the only experiencing this problem. What would you do?

Definitely not high enough DPI to to cause the problems there. Let’s keep looking in the graphical vein. In your project settings, change the project RHI to DX11 and set anti-aliasing to “None” and relaunch the project, it sounds a bit funny but this check often helps guide towards the core of the issue. Does the affect the freeze in any way? Are other menus capable of causing the freezing?

Now I cannot even get to Project Setting without the screen freezing. It sticks as soon as I open the Setting menu:

UE5 actual freezes when I click on any menu item - does not matter which one. Furthermore, when I End Task, the Epic Launcher does not allow me to re-launch the application. The only way I can launch again is to restart my machine. I once again checked all driver versions and reinstalled Epic Games Launcher. This time I used a new account name just in case. Nothing has made a difference. Aaargh!!!

Launched UE 4.27.2 and it ran with no problems.

I launched all 5.x versions. The only one that works is 5.0.3. Every version above 5.1.1 crashes after opening a project. The only way I can shut down UE is to do a total reboot (even End Task does not close the app). When I click on any menu function, the GUI freezes.

I have the latest hardware and drivers. My main processor is an AMD Ryzen 9 7900X 12-Core Processor, the graphics card is an AMD Radeon RX 7800 XT, I have 64GB RAM and a 2TB SSD drive. Capacity is more than sufficient. I would be happy to help troubleshoot this further as I cannot be the only person experiencing this issue. I would love to use the most up-to-date UE5 version, but until this bug gets fixed I will have to stick with 5.0.3.

UPDATE - running 5.0.3 is very laggy. I am so frustrated. Isn’t there some way to contact Epic support for help without paying $1,200 for an Enterprise License?

@SupportiveEntity I do not see how to change anti-aliasing. Keep in mind that the only version I was able to launch is 5.0.3, so if this is in a later version it is not something I can change.

General support is limited to our team here on the forums, though bug reports can sometimes yield more insight if it’s an engine identified bug but in our case this is likely a mix of engine and environment and determining where the interaction is failing is going to be the biggest boon.

Here’s a quick tutorial that can help you change the RHI both inside and outside of editor.

And here’s a link to instructions on how to get to the AA area and change it (in engine):

Anti Aliasing and Upscaling in Unreal Engine | Unreal Engine 5.3 Documentation.

In UE 5.0.3, I set RHI to DX11. Just changing AA to LOW (there is no “None” option) did not help, but when I selected “Auto”, all scalability settings changed to “Medium” (see screenshot below). Making these changes seems to have fixed the issues in 5.0.3. No lag nor freeze. However…

…UE 5.3.2 still freeze/crashes. I went into the .ini and changed RHI to DX11, but I cannot change scalability settings within the application because every time I click on any menu option the GUI crashes. Is there a .ini file I can edit which will change scalability outside of the GUI app? If so, I can change to “Medium” and test again.

@SupportiveEntity I greatly appreciate your continued help and attention to this thread.
At this point, I am taking my PC back to the retailer to discuss the graphics card with them. It does not seem logical that with the processing power I supposedly have that I would need to set scalability to “Medium” and stay using DirectX11. I would think my machine should be able to manage higher settings. Since this thread is no long about just Snap and Static Mesh, I will open a new thread after I review with the retailer. Like I said earlier, with the thousands of machines and UE users, I cannot believe I am the only one having issues with 5.3.2. I will mention you in the new post so you can find it easily. Thanks again!

In the same menu pictured, open project settings than head over here to find the AA settings if you weren’t freezing:

However you can also edit them in the DefaultEngine.ini under the heading
[/Script/Engine.RendererSettings]
r.AntiAliasingMethod=0

The 0 here meaning none.

I don’t believe the hardware itself is the issue as it’s well above spec for the minimum requirements, but more an interaction with something in the software/firmware environment. Since there’s a ton of variables here, messing with the visual requirements were more to see if it was more of a graphical or processing issue.

Problem solved!!! Yeah!!!

Two fixes:

  1. Replaced AMD Radeon RX 7800 XT with NVidia GeForce RTX 4070.

  2. I thought I had a 2K monitor but I just had a 1080p.

After these changes, 5.3.1 seems to be running fine.