> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/holoplot-plan/working-with-beams/visualising-in-configure-mode.md). # Visualising in Configure mode View relative level, relative priority and line of sight directly in the viewport in Configure mode. In Configure mode, you can visualise relative level, relative priority and line of sight directly in the viewport. Relative level and relative priority show how the settings of the zones assigned to a Coverage Beam or LF Coverage Beam affect the beam, so you can adjust them before or after optimizing. Line of sight shows which areas are obstructed from the current selection. ![Viewing Relative Level and Priority in Configure mode](https://1870956965-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWZvA6Ecdn48SRkbJ1C8%2Fuploads%2FKxdayP639uQlucikZR4A%2FCleanShot%202026-09-23%20at%2016.05.17.gif?alt=media) {% hint style="warning" %} **GIF placeholder:** add a GIF showing the Relative Level and Relative Priority controls in the viewport. {% endhint %} {% hint style="info" %} These controls are only available in Configure mode. {% endhint %} ## Turning on a view The **Relative Level** and **Relative Priority** controls are floating icons at the top of the viewport. Neither view is turned on automatically. 1. Switch to configure mode. 2. Select the Coverage Beam or LF Coverage Beam you want to view. 3. Select **Relative Level** or **Relative Priority** at the top of the viewport. Only one of these views can be on at a time. Turning on one view turns off the other. ## Relative Level The **Relative Level** view shows the relative level pattern across the zones assigned to the beam. The relative level combines SPL and the zone's level into a single value. It isn't frequency specific, so the pattern applies to all frequencies. Relative level is shown as a colour gradient in dB. The scale is fixed and runs from 0 dB to -16 dB. This view is most useful before you optimize a beam so that you can check the level pattern across your zones and adjust each zone's **Relative Level** in the Assign Zones to Beam Panel. You can also turn on the view after a beam has been optimized. Zones set to **Avoid** aren't included in the gradient and are shown in the default zone colour. ## Relative Priority The **Relative Priority** view shows each zone's **Relative Priority** setting on the viewport, so you can see the priority of every zone at a glance instead of checking each slider. Priority is shown on the same logarithmic scale as the slider, from 0.01 to 100, with 1 as the default. For more information, see Assigning zones to a Coverage Beam. ### Changing the number of segments The priority legend is divided into segments, and each zone is coloured by the segment its priority falls into. To change the number of segments: 1. Select the settings button next to the legend. 2. Choose the number of segments. The default is 4, and you can choose from 2 to 20. Use fewer segments for a simple overview and more segments to see smaller differences in priority between zones. ## Line of sight preview The **Line of sight preview** shows which areas are obstructed from the current selection. It works for audience zones and boundary zones, and doesn't require Acoustic Shadowing to be on. 1. Switch to configure mode. 2. Select the entity you want to preview. 3. Select **Line of sight preview** (the eye icon) in the toolbar at the top of the viewport. Obstructed areas are shown in brown, and areas that are visible keep their normal default colour. A legend next to the colour bar explains the obstruction colour. {% hint style="warning" %} **Screenshot placeholder:** add a screenshot showing the line of sight preview with the obstruction legend. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.holoplot.com/holoplot-plan/working-with-beams/visualising-in-configure-mode.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.