> For the complete documentation index, see [llms.txt](https://doc.realvirtual.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.realvirtual.io/components-and-scripts/scene-interaction/hmi-components-pro/hmi-value.md).

# HMI Value (Deprecated)

{% hint style="danger" %}
**Deprecated — no authored equivalent in realvirtual WEB.** This Unity uGUI value display is deprecated and is **not read by realvirtual WEB**. In the browser, live signal values are shown through hover tooltips, signal chips/badges and KPI cards rather than an authored per-object value overlay. See [**realvirtual WEB**](/extensions/realvirtual-web.md).
{% endhint %}

HMI Value is displaying values (PLCOutputFloats or PLCOutputInts) for example the number of produced parts, axis positions or temperatures.

<figure><img src="/files/ras0ljqhHE9Wj7gwV0ot" alt=""><figcaption><p>Example HMI-Value moving with the tracked object.</p></figcaption></figure>

## Properties

<div align="left"><figure><img src="/files/hDI6RtZIdgp74dtafh4K" alt=""><figcaption></figcaption></figure></div>

* `Title`: short describtion or name of the value
* `Title Font Size` : font size of the title
* `Display Unit` : true do display a unit right next to the value
* `Unit`: user defined unit string
* `Unit Font Size` : font size of the unit
* `Value Font Size`: font size of the value
* `Format` : number format
* `Follow Camera:` the orientation of the panel is always directed to the camera (only relevant if the canvas uses the render mode "Worldspace")
* `ObjectTracking`: boolean wether the value object is placed next to a game object within the scene or not
* `TrackedObject`: game object within the scene which position is used to place the HMI value information
* `Offset` : Offset position to the object in up direction.
* `SignalInt`: Connected PLCOutputInt Signal
* `SignalFloat` : Connected PLCOutputFloat Signal


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.realvirtual.io/components-and-scripts/scene-interaction/hmi-components-pro/hmi-value.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.