How to stop the "Reopen Asset Editor" notification from disappearing in UE5.1?

Development Programming & Scripting UI
, ,
1

One thing I absolutely loved about UE4 (I love the the entirety of UE4, screw UE5) was this little notification window that would let me reopen the 10, 12 assets I had open at the same time and would allow me to pick off right where I left off.

image

That little notification stayed there till the end of time in UE4 and that is something I really liked because often times I would launch a project and then get up to get a drink or browse the web.

In this abhorrent monstrosity of UE5.1, the notification disappears within a couple seconds of launching a project, causing me to painstakingly find and open each blueprint (Thank God for CTRL+P) and find out where I left.

Is there a way to ensure it doesn’t disappear so quick? It’s a minor detail but it’s gotten to the point of genuinely frustrating me.

2

bump?

3

bounce?

4

Hop?

5

I hate this version

6

problem in 5.5 as well, asks after every restart and doesn’t respect when i click ‘dont ask me again’

1 Like
7

I hope developers come back to UE4. 5 is just a mess

8

Functionality has always been there.
Go to Editor Preferences and search for Asset. CHange the setting to whatever you want. Keep in mind, if you set it to always reopen and one of your assets gets corrupted, it’s really hard to get the engine running again. I recommend you set it to Always Prompt for safety. It should stay open for a while if you don’t click somewhere else first (Ie click on the content browser before you tell it to open). I just make sure I always click on open as soon as I restart.

AssetReopen
AssetReopen1920×1080 122 KB

1 Like
9

They patched in in 5.3 as far as I can tell. Setting it to “Always Restore” is dangerous in case you mess up something in a BP and get stuck in a crashing loop. I used this before and the primary BP struct for my entire inventory system got corrupted (I didn’t know BP structs were finicky back then) and I got stuck in a constant crash loop. Had to remove the inventory component so that the editor can’t find it, then fix the issue

10

When you say they patched it, what do you mean? If you create a loop yourself within blueprint, and the engine crashes and then automatically brings it back up, you’ll never get out of it unless you know which asset caused the issue and delete it as you said you did. Not sure how they can patch out your ability to write shoddy code :stuck_out_tongue: