# Example Pipeline {% hint style="info" %} Please keep that in mind, the example you are going to proceed with is based on our R\&D studio. Various aspects might differ from your setup. If you have any further questions, do not hesitate to contact our Support Department. {% endhint %} ### Preliminary Preparation

* Prepare your scene, launch it via Reality Hub [Launcher](/docs/reality-5.3-sp3/reality-5.3-sp3/user-guide/launcher.md) module. * Drag & drop the **`UE5`** processing node into Nodegraph canvas. * Create two Reality Cameras. See [Actor Spawning](/docs/reality-5.3-sp3/reality-5.3-sp3/tutorials/reality-actor-spawning.md). * Add **`AJAIn`** and **`AJAOut`** nodes, select your devices and outputs based on your setup. * Create your Track node. (In our example it will be the **`Xync`** Node) ### Modifying Curve XR Node

* Add **`Curve XR`** node to the canvas. * Change the following properties based on your measurements: Pitch Angle, Cell Width, Cell Height, Columns Count, Rows Count, Left Tilt/Roll and Right Tilt/Roll, Height Offset, Left Point and Right Point, Cell Resolution, Canvas Resolution. * Duplicate the modified **`Curve XR`** node. * Connect the **`RealityCamera0.Scene`** output of the **`UE5`** node to **`Inner Frustum View`** of the **`Curve XR`** node. * Connect the **`RealityCamera1.Scene`** output of the **`UE5`** node to **`Outer Frustum View`** of the **`Curve XR`** node. ### Preparing Inner Frustum Track * Create **`Add Track`** node. * Connect the **`Track`** output of **`Xync`** node to the **`X`** input of the **`Add Track`** node. {% hint style="info" %} To address a delay in the Inner Frustum at certain zoom levels, which causes a collision with the outer frustum, we must provide additional FOV input for tracking. Our example requires an additional 10-degree field of view (FOV). {% endhint %} {% hint style="info" %} This delay is inherent to the tracking process and rendering of the inner frustum. {% endhint %}

* Expand the **`Y`** property and change the **`FOV`** property to 10. * Connect the **`Z`** output of the **`Add Track`** node into **`Inner Frustum Track`** input pin of the **`Curve XR`** node. Pan, tilt, and roll can now be performed independent of zoom level without causing collisions. ### Preparing Outer Frustum Track

* Create a **`Break`** node. * Connect the **`Track`** output of **`Xync`** node into **`Break`** node’s **`Input`** pin. Now we have access to Track data. For more details, see [Dynamic Nodes](/docs/reality-5.3-sp3/reality-5.3-sp3/user-guide/nodegraph-actions/nodegraph/operating-nodegraph/dynamic-nodes.md). * Create a **`Make Track`** node. * Connect every **`Break Track`** node’s output to the matching inputs of the **`Make Track`** node, except for **`Rotation`** and **`fov`** pins. {% hint style="info" %} Inner Frustum rendered based on where the camera is looking and what is its resolution. On the other hand, the Outer Frustum render continues even if the camera is looking towards a different direction than the LED Screen, because the main purpose of it is to illuminate the scene and talent. No matter what zoom level you are in, Outer Frustum must always encompass the LED screen, therefore Outer Frustum’s FOV must be fixed. In the following steps, you need to get the Rotation and FOV data from your Track while framing the LED screen with your studio camera and keeping the zoom level zero, but the driver still will be the Inner Frustum, the first Track Node we added. {% endhint %} Now:

* Frame the LED screen with your studio camera and keep the zoom level at zero, as illustrated above.

* Create an **`Add f32`** node. * Connect the **`fov`** output of the **`Break`** node into the **`X`** input of the **`Add f32`** node. * Connect the **`Z`** output of the **`Add f32`** node to the **`fov`** input of the **`Make Track`** node. {% hint style="info" %} Now we have the FOV value in the full zoom out while our camera is framing the LED screen. On the other hand, the driver still will be the Inner Frustum. Therefore, we need to disconnect the **`X`** output of the **`Add f32`** node from the **`fov`**. {% endhint %} * Disconnect the **`fov`** output of the **`Break`** node from the **`X`** input of the **`Add f32`** node.

{% hint style="info" %} As the above image suggests, Outer Frustum is rendering with 97 FOV. We need to increase the FOV **`X`** and **`Y`** by 30 degrees to compensate. With this change, Outer Frustum will project the image onto LED screen with 127 degrees to encompass the LED screen. {% endhint %}

* Create an **`Add vec3`** node and connect its **`Z`** output to **`Rotation`** input of the **`Make Track`** node. * Connect the **`rotation`** output pin of the **`Break Track`** to **`X`** input of the **`Break`** node. * Disconnect the **`Z`** output of the **`Add vec3`** node to the **`fov`** input of the **`Make Track`** node. * Connect the **`Canvas`** output of the **`Curve XR`** node to **`AJAOut`**, as illustrated above.

Our scene is successfully projected on the Curved LED. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://zerodensitydocumentation.gitbook.io/docs/reality-5.3-sp3/reality-5.3-sp3/tutorials/curved-led-pipeline-with-curve-xr-node/example-pipeline.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.