STOP Animation Blueprint from SPAM-OPENING ITS MULTIPLE STATE/TRANSITION TABS EVERY TIME ON EDITOR RELAUNCH.

Summary

PLEASE STOP Animation Blueprint from SPAM-OPENING ITS MULTIPLE STATE/TRANSITION TABS EVERY TIME ON EDITOR RELAUNCH.

Things I’ve tried (has no effect on editor relaunch):

  • right-click one of them, “close other tabs”, close the last tab, close ABP, reopen ABP, ABP correctly has no tabs displayed, but when I relaunch the editor, all the tabs come right back
  • close all tabs, save the ABP, then restart editor
  • going into Editor preferences > turn off “restore open asset tabs on restart”.
  • deleting the Saved folder.
  • deleting the Intermediate folder.

The only “workaround” that barely works is closing all the tabs inside the ABP, spammmmm the save button on the asset, close and reopen ABP, spammmmmm the save button on the asset again. This is NOT a fix. This is insanity. After closing all ABP’s tabs we shouldn’t have to close ABP → reopen ABP → save ABP every time we want to edit ABP in a clean session. Having to save the ABP asset is also bad for version control since .uasset files are marked as modified upon saving.

What Type of Bug are you experiencing?

Editor

Steps to Reproduce

In an ABP asset edit multiple states and their transition conditions and press save. Maybe edit some more and save again. Now the ABP asset will spam open all of your state and transition tabs EVERY SINGLE TIME ON EDITOR RELAUNCH EVEN AFTER YOU’VE CLOSED THEM ALL BEFORE CLOSING UE.

Expected Result

Not having all the tabs in ABP asset SPAM-OPEN IN MY FACE.

Observed Result

all the tabs in ABP asset SPAM-OPENS even after CLOSING THEM ALL and double-checking by reopening the asset

Affects Versions

5.7, 5.5

Platform(s)

Windows

Upload an image

Additional Notes

PLEASE FIX IN UE 5.7 OR PREV VERSIONS AS WELL AND NOT ALWAYS JUST YOUR “LATEST” VERSION

I use UE 5.7.4 but I DO NOT KNOW if this problem is in previous versions as well

EDIT: This is a problem in 5.5.4 as well, I just checked. Probably safe to assume this is a problem in 5.6 as well.