Several install script issues on Nobara

[NLRevZ]

I run Nobara, so in order for the install script to work I had to download it manually and add 'nobara' to the list of distributions under the fedora case.
First issue I ran into: Neither Fedora 43 nor Nobara's repos seem to have yder-devel available, so I had to first add the @meshtastic/build-tools) repo for it to be able to install yder-devel.
After doing this, the install script seemed to work fine (simshmbridge's build process threw dozens of warnings about unused variables though), installed all dependencies but during the last few steps it turns out the script has some hardcoded search paths and can't cope with the fact that the script is running from outside its intended path which turned out to be ~/.local/share/monocoque/monocoque. This lead to some funny assumptions being made in the script:

[INFO] Checking: /home/myusername/Downloads/monocoque/monocoque-manager
[INFO] Checking: /home/myusername/Downloads/monocoque/tools/monocoque-manager
[ERROR] monocoque-manager not found!
[WARN] Searched in: /home/myusername/Downloads/monocoque/monocoque-manager /home/myusername/Downloads/monocoque/tools/monocoque-manager
[WARN] SCRIPT_DIR was: /home/myusername/Downloads/monocoque
[INFO] Please copy it manually: cp /home/myusername/Downloads/monocoque/monocoque-manager ~/.local/bin/

After manually putting the modified script into ~/.local/share/monocoque/monocoque I executed it again and this time it detected monocoque-manager and installed it. The last thing to fail was creating the service files:

[SUCCESS] ✓ Installed monocoque-manager TUI to /home/myusername/.local/bin/monocoque-manager
[SUCCESS] Launcher scripts created
[INFO] Creating systemd service files...
./install.sh: line 456: /home/myusername/.config/systemd/user/simd.service: Permission denied

I have not yet attempted to manually perform this step, but it appears this step will only run as superuser..

[Spacefreak18]

i'm thinking about getting rid of that install script because it causes too many issues for people and I have these builds now.

Looks like Nobara is based on Fedora 43, can you try the prebuilt rpm for fedora 43 here.

And that was built yesterday so it is quite up to date.

[NLRevZ]

Actually, I did try installing the RPM package first and it doesn't install monocoque-manager (despite returning a success status on the overall RPM install), which is why I even bothered to try out the install script
Only problem is that while that script successfully installs monocoque-manager when it's in the right location, it cannot install the service.
It did seem like the RPM package also did not do this, though it got less far in general.

[Spacefreak18]

you don't really need the manager. ( you'll just have to install all the part separately )

you likely have /usr/bin/monocoque already there now and ready to use.

which will be sufficient for sims that just use udp, if you want to use Assetto Corsa, or Automobilista or other sims that require shared memory files, you will also need to install simd and download the appropriate compatibility bridge exes described here

you can download fedora 43 binaries for simd ( and simapi which it depends on ) just like for monocoque here

[Spacefreak18]

oh, i've been meaning to add a link to these on the simd page, but I have packages built for yder and other simd dependencies.

https://repo.spacefreak18.xyz/Packages/Fedora/43/

[Spacefreak18]

the unused variable errors you get on simshmbridge are normal, they're just warnings, i'll fix those eventually.

[NLRevZ]

In the end it all seems to function, except the part where data is supposed to come from AC/ACC..

/tmp/simd.log shows the probable cause:

026-03-20T16:56:05 - simd INFO: Starting Bridge Polling Thread.
2026-03-20T16:56:22 - simd INFO: found a specified launch process for gameid 805550 running at pid 8697.
2026-03-20T16:56:22 - simd INFO: Detected simulator id 805550, starting appropriate bridge if necessary.
2026-03-20T16:56:22 - simd DEBUG: Retrieved env vars /home/myusername/.local/share/Steam/compatibilitytools.d/GE-Proton10-32:/home/myusername/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper and /mnt/2TBGAMES/SteamLibrary/steamapps/compa>
2026-03-20T16:56:22 - simd DEBUG: Determined wine executable path /home/myusername/.local/share/Steam/compatibilitytools.d/GE-Proton10-32/files/bin/wine
2026-03-20T16:56:22 - simd DEBUG: No errors found, will attempt to fork a process like this WINEFSYNC=1 WINEPREFIX=/mnt/2TBGAMES/SteamLibrary/steamapps/compatdata/805550/pfx /home/myusername/.local/share/Steam/compatibilitytools.d/GE-Proton10->
2026-03-20T16:56:22 - simd DEBUG: Fork was successful looking for data next
2026-03-20T16:56:22 - simd DEBUG: datacheckcallback triggered
2026-03-20T16:56:22 - simd DEBUG: Found running process for Assetto Corsa
2026-03-20T16:56:22 - simd DEBUG: static and physics files found
2026-03-20T16:56:22 - simd DEBUG: simapi_init error 0
2026-03-20T16:56:23 - simd DEBUG: datacheckcallback triggered
2026-03-20T16:56:23 - simd DEBUG: Found running process for Assetto Corsa
2026-03-20T16:56:23 - simd DEBUG: static and physics files found
2026-03-20T16:56:23 - simd DEBUG: simapi_init error 0
2026-03-20T16:56:24 - simd DEBUG: datacheckcallback triggered
2026-03-20T16:56:24 - simd DEBUG: Found running process for Assetto Corsa
2026-03-20T16:56:24 - simd DEBUG: static and physics files found
2026-03-20T16:56:24 - simd DEBUG: simapi_init error 0
2026-03-20T16:56:25 - simd DEBUG: datacheckcallback triggered
2026-03-20T16:56:25 - simd DEBUG: Found running process for Assetto Corsa
2026-03-20T16:56:25 - simd DEBUG: static and physics files found
2026-03-20T16:56:25 - simd DEBUG: simapi_init error 0

With that last block repeating several times per second, as you can see..
The output test in monocoque-manager works just fine so the issue seems to be that something wasn't installed right?

[Spacefreak18]

that looks good, if you start /usr/bin/monocoque play and start driving you should see the speed and rpms come through.

if not double check if you have data in
hexdump /dev/shm/SIMAPI.DAT
hexdump /dev/shm/acpmf_physics

[NLRevZ]

Hmm.. It seems the only way to reliably get it to process data is if I start simd, then the game, then monocoque. If I start both before or after starting the game it won't log any data.

I do wish this whole process could be more automated; at the moment it's just a whole bunch of fragmented things to set up and then trigger by hand through console commands. This is definitely hampering greater adoption for the average user who wouldn't be comfortable digging through command lines to get something like this accomplished.

Sidenote, I think I'm going crazy or something; I swear I saw some settings regarding RPM range mapping somewhere back when I was setting up the device settings but now I can't find it anywhere anymore.
I would prefer if the RPM gauge would follow Moza's default behaviour ("Normal" mapping being 6300-7800RPM for RPM1 to RPM10 rather than 1000-8000RPM as it seems to be right now), is there any way I can set this range manually or perhaps per game?
Boxflat already supports setting this curve but it seems this way of driving the LEDs bypasses Boxflat's control entirely.

[Spacefreak18]

you definitely need to start simd before anything else. after that... it shouldn't matter (that's why there is a service for it).

I know, what you're saying but simd needs to be it's separate things so in the future if we decide to spin off apps ( like in the Windows world where every wheel manufacturer has their own software, even my tachometer came with it's own software ), we can atleast keep the telemetry mapping part separate and shared. I know one dude who is trying to make a motion sim app in python, he doesn't have to worry about getting data from sims, just open /dev/shm/SIMAPI.DAT and his app has any data he needs from any sim.

The simshmbridge stuff, because of the reasons I talk about in the github readme for that project, that has to be that way for the sims that need it. ( I have precompiled binaries for simshmbridge too, but having to mess with launch commands is a mess )

What I am starting to concede on, after hearing Linus say the same thing in regards to packaging on Linux, it's a headache. And maybe you keep the core OS packaged by the package manager, with dynamic linked libraries, but for niche apps ( like this simracing, and Linus maintains some diving software ) you just distribute a big binary that's statically linked. Because packaging on Linux is just such a headache.

[Spacefreak18]

I only assisted with writing the code for the Moza LEDs, but I thought that it would let you set the settings in boxflat, and then monocoque just lights them.

Looking at the code, it looks like we take into account the percentage to maxrpm as we set LEDs. And the maxrpm, most sims send that data on a per car basis. So that should be desireable?

[NLRevZ]

Boxflat allows you to set the wheel RPM display between Mode 1, which should have it follow whatever the game sets as a curve display (usually following the indicator lights in the actual car) or Mode 2, which has you choose from three predefined curves (just like with Moza's own Pithouse software) or set a curve of your own, using either RPM or percentage RPM as a basis:

However, I do suspect this is completely bypassed by the way the device is directly driven from monocoque, is this not true? No matter what I set there, it's wholly ignored.

[Spacefreak18]

i think you're right, we're just setting leds based on current_rpm/max_rpm.

i guess the only thing it WILL obey is the colors.

[Spacefreak18]

i fixed the issue with the install.sh simd.service installation

[NLRevZ]

Despite everything working right now, the service doesn't seem to exist on my system yet (systemctl status simd.service yields nothing) so the RPM package install also didn't install it on my end. How do I go about properly setting up that service without having to redo the rest?

[Spacefreak18]

The same way as manually installing any system wide systemd service.

Copy to simd.service to /etc/systemd/system/. ( You may need to edit that servivce unit file based upon where you have installed the simd binary you wish to use )

Then:
systemctl enable simd.service
systemctl start simd.service

https://wiki.archlinux.org/title/Systemd

( if you want it to be a user service copy it to ~/.config/systemd/user/ and just add the --user flag to your systemctl commands, which is what the install.sh does ).