Description

Hello!

We have encountered a bug with the Interchange pipeline. When an interchange texture import is cancelled due to non-power of 2, and then the same texture is imported again without any changes, the texture is imported with legacy pipeline. This fallback seems to occur even though the asset was never fully imported via Interchange and never appears as a .uasset.

First import log:

LogInterchangeEngine: [Pending] Importing

LogInterchangeEngine: Display: Interchange start importing source [C:/.../T_Cat_D.jpg]

LogInterchangeImport: JPEG file [C:/.../T_Cat_D.jpg]: Pipeline setting 'bPreferCompressedSourceData' has been overridden by Editor setting 'RetainJpegFormat'.

LogInterchangeEngine: Display: Interchange import completed [C:/.../T_Cat_D.jpg]

Interchange: Error: [Link Removed] Cannot import texture with non-power of two dimensions

Interchange: Error: [Link Removed] Unable to retrieve the payload from the source file.

LogInterchangeEngine: [Pending] Importing - Operation completed.

LogInterchangeEngine: Error: [Failure] Import Failed

Second attempt:

LogEditorFactories: Performing atomic reimport of [C:/.../T_Cat_D.jpg]

LogFactory: FactoryCreateFile: Texture2D with ReimportTextureFactory (0 0 C:/.../T_Cat_D.jpg)

LogEditorFactories: Display: JPEG imported and retained as JPEG in uasset.

LogEditorFactories: Display: Image imported as : TSF BGRA8

LogEditorFactories: – imported successfully

What is the best way to prevent this behavior?

Steps to Reproduce

Steps to Reproduce

Repro steps:

1. Make sure interchange pipeline is enabled for textures
2. In DefaultTexturePipeline set Allow Non Power Of 2 to false 
3. Import a texture with an invalid size (eg: 1025x1023)
4. Note that the import is cancelled
5. Immediately try importing the same texture

Have Comments or More Details?

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

0
Login to Vote

Fixed
Fix Commit44080139
CreatedJul 14, 2025
ResolvedJul 15, 2025
UpdatedAug 11, 2025
View Jira Issue