# \[UE5.6 Upgrade\] Build Error Including ScenePrivate.h — Missing 'TranslucentPassResource.h

**URL:** <https://forums.unrealengine.com/t/ue5-6-upgrade-build-error-including-sceneprivate-h-missing-translucentpassresource-h/2544308>\
**Category:** Programming & Scripting\
**Tags:** error, Render, rhi, compilation-error, unreal-engine, compile, issue, CPP, question\
**Created:** [June 6, 2025, 7:20pm UTC](https://forums.unrealengine.com/t/ue5-6-upgrade-build-error-including-sceneprivate-h-missing-translucentpassresource-h/2544308 "2025-06-06T19:20:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![X-perto](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@X-perto](https://forums.unrealengine.com/u/X-perto)\
**Post date:** [June 6, 2025, 7:20pm UTC](https://forums.unrealengine.com/t/ue5-6-upgrade-build-error-including-sceneprivate-h-missing-translucentpassresource-h/2544308/1 "2025-06-06T19:20:46Z")

</div>

I’m upgrading a project from Unreal Engine 5.5 to 5.6, and I’m running into a compiler error when including `ScenePrivate.h`:

> MeshDrawCommands.h(10,1): error C1083: Cannot open include file: ‘TranslucentPassResource.h’: No such file or directory

This was working fine in 5.5:

```cpp
#include "Runtime/Renderer/Private/ScenePrivate.h"

FSceneInterface* Scene = GWorld->GetWorld()->Scene;
Scene->GetRenderScene()->CustomRenderPassRendererInputs.Add(PassInput);

```

It seems like `TranslucentPassResource.h` might have been removed or relocated in 5.6, but I can’t find much on it.

Has anyone encountered this or knows the correct way to access `CustomRenderPassRendererInputs` or hook into custom render passes with the newer version?

Any help would be appreciated.

---

<div class="post-metadata">

**Author:** ![tyz\_kotono](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@tyz\_kotono](https://forums.unrealengine.com/u/tyz_kotono)\
**Post date:** [June 9, 2025, 1:10pm UTC](https://forums.unrealengine.com/t/ue5-6-upgrade-build-error-including-sceneprivate-h-missing-translucentpassresource-h/2544308/2 "2025-06-09T13:10:16Z")

</div>

I’m having the same problem, although I can add Path.combine to Build and access it through that, it doesn’t do much good, and custom render passes still have a lot of problems!

You can try adding this

PrivateIncludePaths.AddRange(  
new string {  
Path.Combine(GetModuleDirectory(“Renderer”), “Private”),  
Path.Combine(GetModuleDirectory(“Renderer”), “Internal”),  
}  
);

But Epic would advise us not to do so

---

<div class="post-metadata">

**Author:** ![X-perto](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@X-perto](https://forums.unrealengine.com/u/X-perto)\
**Post date:** [June 9, 2025, 2:35pm UTC](https://forums.unrealengine.com/t/ue5-6-upgrade-build-error-including-sceneprivate-h-missing-translucentpassresource-h/2544308/3 "2025-06-09T14:35:12Z")

</div>

I haven’t tried that myself, where you able to get it to work by adding the private and internal paths?  
If so then I guess that’s how you’re supposed to do it for the time being.

---

<div class="post-metadata">

**Author:** ![AYAYA2](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@AYAYA2](https://forums.unrealengine.com/u/AYAYA2)\
**Post date:** [June 24, 2025, 10:19am UTC](https://forums.unrealengine.com/t/ue5-6-upgrade-build-error-including-sceneprivate-h-missing-translucentpassresource-h/2544308/4 "2025-06-24T10:19:51Z")

</div>

It seems that the Unreal Engine official does not want developers to reference these private or internal header files in version 5.6. However, the issue is that they have only disabled the private files, but some variable(we need in plugin or proeject) pre declarations still have relevant definitions. For example:

class FPostOpaqueRenderParameters  
{  
public:  
…  
…  
const FViewInfo\* View = nullptr; // it still include “ScenePrivate.h”  
};

it make our code can not be compiled.  
so, wait next update~
