How is the G-Map / G-force dot in Screamer built? Is there a public way to make a 2-axis G ball?

Hi,

I’m building a custom dashboard and I have a working G-meter using bar gauges fed by Acceleration X (6) and Acceleration Y (7). What I want is the 2-axis dot-in-a-circle display — the G-Map in the premium Screamer dashboard (slide the tach sideways to the G-force view: circle + crosshair + a white dot that moves with the values).

I tried to build it with value-morph animations (RealDash 2.7.5 on PC, 2.7.4 on iOS). One morph alone tracks fine, but two morphs running at the same time corrupt each other:

  • two morphs on one gauge: they fight, last-listed wins;
  • container morphed on one axis + the ball inside morphed on the other: applies once on activation, then freezes;
  • two separate gauges, one morph each (crosshair): the vertical line renders squashed into the lower half, as if the engine cross-applies rect components between the two running morphs.

I also checked the full ADD GAUGE list in the editor — there is no G-Map / G-Force gauge type available to builders. The 2023 thread “Accelerometer via serial” only explains feeding X/Y/Z to inputs 6/7/8, not how the dot display itself is constructed.

My questions:

  1. Is Screamer’s G-Map built with an internal / hidden gauge type that is not in the public editor?
  2. If so, is there any plan to expose it to dashboard builders?
  3. Or is there a public construction (animation XML, gauge combination) that achieves a 2-axis dot that I have missed?

Attached are my two minimal repro animation files: TRY 1 (two morphs on one gauge) and TRY 4 (one morph per gauge, crosshair). Happy to provide the test dashboard as well.

Thanks!

The two repro files, pasted as code

TRY 1 (two morphs on one gauge):

TRY 4 (one morph per gauge, crosshair):

GRYaris_GBallTest_anim.xml (1.5 KB)

GRYaris_GBallTest4_anim.xml (1.6 KB)

There’s no hidden gauge type for that. The G-force view in Screamer is a regular Axis gauge, the same one that’s in the editor. It’s a bit hidden in the menu: ADD GAUGE → INDICATORS → AXIS GAUGE. In Screamer it’s just that gauge with a circle/crosshair image as the face and a white dot as the indicator image.

An Axis gauge has two inputs and moves one dot in both directions:

  1. Add the gauge and size it to cover your circle.
  2. In INPUT & VALUES, select the data sources (X and Y axis): Acceleration X for X and Acceleration Y for Y. Set the min/max for both axes, for example -1.5 to 1.5.
  3. In LOOK’N FEEL, set the face image to your circle and crosshair, and the indicator image to your dot. The indicator scale setting controls the dot’s size.

The X value moves the dot from left (min) to right (max), and the Y value moves it from bottom (min) to top (max). There are also two optional extras: SHOW HISTORY TAIL (a fading trail behind the dot) and SHOW ABS-MAX AS TEXT (shows the peak G value).

If you want a ready-made example to take apart, download the free Arc and Axis gauge example dashboard from the gallery.

About the value-morph tests: one value-morph sets the whole rectangle of the gauge (left, top, right and bottom), not just one axis. So two of them running on the same gauge keep overwriting each other, and that’s why the last one wins. Value-morph isn’t built to combine two values. The Axis gauge is the right tool for this.

Thank you — that was it. “Axis” was sitting in our ADD GAUGE → INDICATORS list the whole time; we photographed that menu and still read past it.
The value-morph explanation also matches exactly what we saw in the tests (whole-rect overwrite, last one wins).
I’ll rebuild the G page with an Axis gauge — our existing circle/crosshair art as the face and a dot as the indicator. The history tail is a nice bonus; that’s the trail we admired in other apps.
Thanks again for the clear answer.

It works! Reporting back as promised.

I built the G-Map with the Axis gauge, exactly as you described:

  • X axis: Acceleration X, Y axis: Acceleration Y, both ranged -1.5 to 1.5
  • Indicator image: a small orange ball PNG I made (the default white dot worked fine too)
  • SHOW HISTORY TAIL turned on - the fading trail behind the dot looks great
  • VALUE SMOOTHING 90, same as on my G bar page, to calm the sensor noise

The dot tracks tilts in both axes and diagonally, and returns to the centre. I also added LAT / LONG / TOTAL text readouts next to it, and the dot position matches the numbers.

So the G ball was sitting in the ADD GAUGE menu the whole time. Thank you again for pointing me to the right tool - and for explaining why the value-morphs could never have worked.