Targeting arrows don't show distance

[DevInstinct]

As shown in the attached screenshot, the distance of the targeting arrows don't show for one of my players.

His system specs:

Garuda Linux 6.19.14-zen11-1-zen
Arch
Amd Radeon RX 9070XT
Name : mesa
Version : 1:26.0.5-1
Description : Open-source OpenGL drivers

[pindercarl]

As shown in the attached screenshot, the distance of the targeting arrows don't show for one of my players.

His system specs:

Garuda Linux 6.19.14-zen11-1-zen
Arch
Amd Radeon RX 9070XT
Name : mesa
Version : 1:26.0.5-1
Description : Open-source OpenGL drivers

There is a potential conflict with Steam and the FGVTT type libraries under Linux. If you run Fantasy Grounds directly, rather than through Steam, text should render normally.

[Speculi]

There is a potential conflict with Steam and the FGVTT type libraries under Linux. If you run Fantasy Grounds directly, rather than through Steam, text should render normally.

Which steam runtime is being used to start FG through Steam? By default Steam will fall back to the rather old version 1 (Scout). It seems like version 4 (steamrt4) will display the distance on targeting arrows. I tested this by manually starting FG through both runtimes once.

https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/blob/main/docs/slr-for-game-developers.md#native-linux-games-targeting-steam-runtime-4-steamrt4

I didn't try v2 or v3 of the runtime.

[Moon Wizard]

For some reason, when FG is started through Steam; it is overriding the font library within the executable with a different version from Steam. It's something that Steam and/or Linux is doing for some reason we're not familiar with. We don't use the Steam runtime at all; just provide a command line for Steam to start FG.

Regards,
JPG

[Speculi]

For some reason, when FG is started through Steam; it is overriding the font library within the executable with a different version from Steam. It's something that Steam and/or Linux is doing for some reason we're not familiar with. We don't use the Steam runtime at all; just provide a command line for Steam to start FG.

Regards,
JPG

That's why I mention it and wanted to make you aware of the Steam runtime on Linux.

From the Steam documentation linked above:

All games distributed on Steam use a compatibility tool of some sort, for the widest possible cross-distribution compatibility.
There is no option for running directly on the host system with no compatibility tool.

Every game installed and started through steam will run in one of the Steam Linux runtime containers. By default this will be the oldest version. AFAIK this can be setup somewhere in the games management console/page by the developer of the game. Users can't change this. (They can only switch to the Windows version running through Proton.)
Even if you just distribute the installer/command line to start the launcher, Steam will treat FG as a Steam game when installed through Steam.

The idea behind the runtime is to bring a stable set of "system" libraries across different Linux distributions and versions.

I usually don't run FG through Steam, but with the given instructions from the documentation, I did run it once in v1 and got the missing text on arrows. That's the one FG is most likely using because it was never defined. With v4 it seems to be fixed (I guess a more modern version of whichever library is responsible).

Edit: in case the above link looks not official enough, this one has a link to the gitlab repo
https://partner.steamgames.com/doc/store/application/platforms/linux#5

[Moon Wizard]

Thanks for the info. I'll have to pass to Carl to review.

How were you able to run in different versions?

JPG

[Speculi]

After downloading the runtime (I had all 4 in my library anyway, because of different installed games, but you can also install them manually) you can use this to run an executable in v1.


$ export STEAM_COMPAT_MOUNTS=/path/to/steamlibrary
$ cd /builds/my-game
$ /path/to/steamlibrary/steamapps/common/SteamLinuxRuntime_soldier/run \
$pressure_vessel_options \
-- \
/path/to/steamlibrary/steamapps/common/SteamLinuxRuntime/scout-on-soldier-entry-point-v2 \
-- \
./my-game.sh



v4 is a little bit simpler


$ cd /builds/my-game
$ /path/to/steamlibrary/steamapps/common/SteamLinuxRuntime_4/run \
$pressure_vessel_options \
-- \
./my-game.sh


The my-game path is most likely something like ~/.SmiteWorks/fantasygrounds and steam library path ~/.steam/steam/ and the game.sh would be replaced with the FG executable
(Not at my PC at the moment.)

It's documented also at the first link I gave you. I'm happy to answer more questions or test something, if I can. Unfortunately I don't have a stem dev account any more to check on any internal documentation or a games dashboard.
If it would help, we might also find a timeslot to look at this over Discord.