By setting an Atlas Group to a newly created sprite, the editor freezes. This feature is most important, even if this issue can only be reproduced by a minority of users.

Repro rate: 5/5


  • No other Windows PC/Device could reproduce this issue.
  • Seems to only happen to me (Windows Only).
  • The user can no longer interact with the editor, even though the Task Manager seems to display that the engine keeps running.
  • After 5 to 6 minutes, the editor closes whit out a Crash Reporter Window but with an updated log after shutting down by itself.


Regression Status: The issue does not occur on //UE5/Release-5.2 CL-25121900 Binary so it's a regression.

Steps to Reproduce
  1. Open/Create a project with Unreal Editor (//UE5/Main-5.3 CL-25106002 Source Perforce on Windows 64 Bit).
  2. Make sure the plugin Paper 2D is enabled.
  3. Open Project Settings under Edit in the Toolbar.
  4. Search for Enable Sprite Atlas Groups under Plugins -> Paper 2D and click on the checkbox to set it as true.
  5. Close the Project Settings and open the Content Drawer.
  6. Click on Import located next to the green +Add (Plus) button and select an image/texture to import.
  7. Right Click the newly imported texture and go to Sprite Actions and click on Create Sprite.
  8. Double Click to open the sprite and go to the View Tab where you can see settings as Sprite, Source UV, Sockets, Collisions, etc. (This tab appears by default, but you can see your sprite as Source Texture).
  9. Go to Advance Settings -> Atlas Group and by the None dropdown, selected the NewPaperSpriteAtlas made beforehand.


Expected Result: The Atlas Group can be set to Sprite properly, whit out Freezing the Editor.

Actual Result: The editor gets Frozen after setting an Atlas Group into a newly created sprite by an imported texture.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-183748 in the post.

Login to Vote

ComponentUE - Editor - Content Pipeline
Affects Versions5.3
Target Fix5.5
CreatedApr 19, 2023
UpdatedJan 26, 2024
View Jira Issue