# Rendering issues with Niagara in UE 5.8+

**URL:** <https://forums.unrealengine.com/t/rendering-issues-with-niagara-in-ue-5-8/2858504>\
**Category:** Issues and Bug Reporting (Unreal Engine)\
**Tags:** unreal-engine\
**Created:** [November 18, 2026, 12:39pm UTC](https://forums.unrealengine.com/t/rendering-issues-with-niagara-in-ue-5-8/2858504 "2026-11-18T12:39:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![leopaul3](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@leopaul3](https://forums.unrealengine.com/u/leopaul3)\
**Post date:** [November 18, 2026, 12:39pm UTC](https://forums.unrealengine.com/t/rendering-issues-with-niagara-in-ue-5-8/2858504/1 "2026-11-18T12:39:31Z")

</div>

### Summary

We’ve encountered two issues with Niagara after upgrading a project from UE 5.6 to UE 5.8:

The first is a discrepancy in the way null bindings to texture parameters on materials are handled. Specifically: when a renderer uses a material instances that overrides a texture from its parent material, and that same texture parameter is configured as a binding on the renderer but set to null, UE 5.6 would fall back to the texture from the parent material instance, but UE 5.7+ will now fall back to the default texture of the root material. This is due to a change in CL 45127665 where a null value in the binding will now explicitly lookup the texture parameter’s value in the root material, and the previous behavior can be restored by performing the lookup on the parent material instance instead which seemed like a low-stake change:

```diff
-else if ( const UMaterial* ParentMaterial = MatDyn->GetMaterial() )
+else if ( const UMaterialInterface* ParentMaterial = MatDyn->Parent )

```

The second issue we encountered is a missing render state on a Niagara component when the system is reactivated without being reset after having already completed. This is a case where we want the effect to activate or reactivate only if its not already playing, which used to work in UE 5.6. In UE 5.8+ however, a new check was added in CL 50513903 that skips creating the render state if the execution state of the system is `ENiagaraExecutionState::Complete`. Unfortunately `UNiagaraComponent::ActivateInternal` calls `CreateRenderState_Concurrent` before `SystemInstanceController->Activate`, so the system is still in the completed state when the render state should get recreated on activation. This causes the render state creation to be skipped, and while the simulation can be verified to be running in the Niagara Debugger the particle system doesn’t get rendered. In this case I wasn’t entirely sure of what kind of side effects changing the ordering in these functions would have, so I’ve just added an extra `MarkRenderStateDirty` after the system is activated if its no longer in the complete state and doesn’t have a `SceneProxy` in the meantime.

Do these two fixes look sound, is there some other / better way of handling this, and should these changes be upstreamed in a future version of Unreal ?

### What Type of Bug are you experiencing?

Rendering (Graphics / Niagara)

### Steps to Reproduce

Bug 1:

- Create an unlit material using a texture sample parameter as its emissive color
- Create a constant instance of this material sampling a different texture
- Use this material instance on a Niagara renderer, with an attribute binding on the texture parameter with a null value

Bug 2:

- Create a Blueprint with a Niagara component
- Activate the component, then reactivate it again without resetting once the system completes (the simplest way to do this is activating on every tick)

### Expected Result

Bug 1: The particles should use the texture from the material instance  
Bug 2: The particles should render when the system start simulating again

### Observed Result

Bug 1: The particles use the texture from the root material  
Bug 2: The particles do not render when the system is reactivated

### Affects Versions

5.9  
5.8  
5.7

### Platform(s)

Windows
