# Display Cluster API in c++

**URL:** <https://forums.unrealengine.com/t/display-cluster-api-in-c/496491>\
**Category:** C++\
**Tags:** ndisplay, unreal-engine, UE4-26, question\
**Created:** [February 10, 2022, 10:13am UTC](https://forums.unrealengine.com/t/display-cluster-api-in-c/496491 "2022-02-10T10:13:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MikeAngeloK](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@MikeAngeloK](https://forums.unrealengine.com/u/MikeAngeloK)\
**Post date:** [February 10, 2022, 10:13am UTC](https://forums.unrealengine.com/t/display-cluster-api-in-c/496491/1 "2022-02-10T10:13:48Z")

</div>

Hello,

i want to get the Display Cluster API in c++. There is already the Blueprint [UDisplayClusterBlueprintLib::GetAPI | Unreal Engine Documentation](https://docs.unrealengine.com/4.26/en-US/API/Plugins/DisplayCluster/Blueprints/UDisplayClusterBlueprintLib/GetAPI/)  
The class isnt tagged as a dll Export so i cant build any “Editor” configuration.

Is there a workaround or fix for this?

Thanks!

---

<div class="post-metadata">

**Author:** ![Barbelot](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Barbelot](https://forums.unrealengine.com/u/Barbelot)\
**Post date:** [March 14, 2023, 5:55pm UTC](https://forums.unrealengine.com/t/display-cluster-api-in-c/496491/2 "2023-03-14T17:55:55Z")

</div>

Hello,

I am also interested in this.  
I am trying to get the Display Cluster API in C++, I currently have the following code :

```auto
//Get DisplayClusterAPI
TScriptInterface<IDisplayClusterBlueprintAPI> DisplayClusterBlueprintAPI;
UDisplayClusterBlueprintLib::GetAPI(DisplayClusterBlueprintAPI);

```

But I get an error when compiling :

> unresolved external symbol “public: static void \_\_cdecl UDisplayClusterBlueprintLib::GetAPI(class TScriptInterface &)”

I have included “DisplayCluster” in my build.cs file as follows :

`PublicDependencyModuleNames.AddRange(new string[] { "Core", "CoreUObject", "Engine", "InputCore", "DisplayCluster" });`

And included the header

`#include "DisplayCluster/Public/Blueprints/DisplayClusterBlueprintLib.h"`

but I still get the error and I don’t know why.

---

<div class="post-metadata">

**Author:** ![SeraPhiXR](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SeraPhiXR](https://forums.unrealengine.com/u/SeraPhiXR)\
**Post date:** [September 21, 2025, 7:43pm UTC](https://forums.unrealengine.com/t/display-cluster-api-in-c/496491/3 "2025-09-21T19:43:17Z")

</div>

Hey! Has anyone figured this out?

---

<div class="post-metadata">

**Author:** ![David\_Gilbert](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@David\_Gilbert](https://forums.unrealengine.com/u/David_Gilbert)\
**Post date:** [September 23, 2025, 9:03am UTC](https://forums.unrealengine.com/t/display-cluster-api-in-c/496491/4 "2025-09-23T09:03:01Z")

</div>

Why do you want to get the Blueprint API instead of accessing the functionality directly:

```cpp
IDisplayCluster::Get()

```

From there on, you can access the respective managers:

```cpp
/**
	* Access to the device manager.
	*
	* @return Current device manager or nullptr
	*/
	virtual IDisplayClusterRenderManager* GetRenderMgr() const = 0;

	/**
	* Access to the cluster manager.
	*
	* @return Current cluster manager or nullptr
	*/
	virtual IDisplayClusterClusterManager* GetClusterMgr() const = 0;

	/**
	* Access to the config manager.
	*
	* @return Current config manager or nullptr
	*/
	virtual IDisplayClusterConfigManager* GetConfigMgr() const = 0;

	/**
	* Access to the game manager.
	*
	* @return Current game manager or nullptr
	*/
	virtual IDisplayClusterGameManager* GetGameMgr() const = 0;

	/**
	* Access to the DisplayCluster callbacks API
	*
	* @return Callbacks API
	*/
	virtual IDisplayClusterCallbacks& GetCallbacks() = 0;

```

These work fine on my end, just have to be a bit careful sometimes on which node you call them.
