[WIP] TruckSim Navigator: a route advisor for your tablet / phone

[hoseclamp72]

No errors that I've seen. It just closes. Normally I don't even notice it close (I run the client displayed on a secondary monitor which is kinda out of the way), I only tell because the GPS stops updating my route lol. I'll watch for the updates though and see if anything shows up then.

[truckermudgeon]

It just closes.

Just uploaded a new client! It's available for download at the original link in my first post, and my github releases page:

• http://downloads.truckermudgeon.com/tru ... indows.zip
• https://github.com/truckermudgeon/maps/ ... tor/v0.2.0

Let me know if this improves/fixes the whole client-closing-itself issue

[hoseclamp72]

I just installed it. Now I'll give it a try and see how things go. Thanks!

EDIT: Is it possible to add a little more tolerance to the time checking the client does when connecting? I just had a heck of a time getting it to connect because of that.

[truckermudgeon]

Is it possible to add a little more tolerance to the time checking the client does when connecting? I just had a heck of a time getting it to connect because of that.

Oof, sorry about that... tolerance is now a 10-minute window (instead of a 35-second window ). If it happens again, I'll either increase it to a 1 day window, or I'll remove the time check altogether.

Other than the time check thing, have you been experiencing any other weird client errors?

[TwinShadow]

So I still appear to have the occasional problem that the client silently crashes while I'm doing a load or something. I didn't catch anything in the console because I forgot to run the EXE itself through command line and not just double clicking the EXE file. The last time I ran it, it didn't crash, so it's random on when it crashes or something. With Illinois set to release pretty soon now, I'll probably be doing some more driving in it, but I'll see if I can't get something before then too.

[truckermudgeon]

Just pushed an update to the server, and to the webapp (the client hasn't changed, though I expect it will have to in the next update or two, in order for me to fix a convoy issue).

If you're connected to the webapp: you'll need to reload your browser

The update is kinda big: it adds support for ETS2. But that support is even more experimental than this already-experimental project... it's so experimental, I won't even post about it in the Euro Truck Simulator 2 version of this board . But if anyone here does try it: expect some weirdness (and please report issues if you run into any!)

@TwinShadow let me know if you get any more information on your client crashes... I haven't seen anything in the logs (but maybe I'm not logging the right things ).

[TwinShadow]

I've just now been able to kinda get back to this. I have not done extensive testing because I've had some other games come up, and I've been using Linux a bit more as my primary OS now. So, I did a little stuff to get ATS installed on Linux (using the forced compatibility for Proton so I can download the Windows files, rather than the native Linux binary build), and I figured out how to get the telemetry DLL to load while using Proton. I still have some weirdness occasionally, but that has nothing to do with the navigator itself.

So what I did after was I looked up on how to launch a Windows program in the same prefix, and it was stupid simple. I did that, loaded the game, loaded the navigator app (the Windows build, not the Linux one because I don't think it'll hook correctly if I did), got into the game world in the truck seat, paired my tablet and........ IT WORKED. I was actually kinda surprised by that.

I'm still waiting for SCS to eventually give us a Vulkan renderer update, but this will suffice for now. I've lost TrackIR for the time being, so I'm going back to a very old setup I used to use before I got the TrackIR itself, so that'll work.

If anyone else is on Linux and wants to play through Proton and use this navigator app, make sure the following is in your launch parameter for ATS:

Code: Select all

WINEDLLOVERRIDES="scs_telemetry=n,b" %command%

If you already have existing parameters, make absolutely sure you put this DLL override BEFORE your game parameters, like so:

Code: Select all

WINEDLLOVERRIDES="scs_telemetry=n,b" %command% -nointro

Another thing to note, make sure the scs_telemetry matches whatever DLL you're using, be it truckermudgeon's build, or some other on GitHub. That's an important part.

Now for the navigator itself, I did not test this without it being in the prefix, but I ran it just in case within the same one that ATS is in to ensure that things get hooked like they're suppose to. YMMV of course, but if you want to launch it in the same prefix:

Code: Select all

protontricks-launch --appid 270880 /path/to/navigator.exe

That will launch the navigator application in the same prefix as the game. In my case, if I ran Navigator before ATS, for some reason, ATS will fail to boot, not sure why. So I launch the game first, and then the navigator app, and everything is peachy. I think it's a quirk with my system though, as I was having problems launching before anyway a couple times.

I will do more testing, especially that weird silent crashing behavior when I can. I've been wanting to drive around in Illinois anyway since it released and did a few drives last night, but couldn't get the navigator running at the time. But now that I figured it out, I'll do some testing with it next time I'm in ATS, provided I'm not playing Enshrouded or Subnautica 2, or messing around with a local LM trying to debug a script for 3 days. lol

[TwinShadow]

Driving through the panhandle of Idaho with the navigator and I noticed a notification from my terminal window that it failed. So, I got whatever was output in the window, but I still don't know what causes this:

Code: Select all

socket closed: CloseEvent {
  isTrusted: true,
  wasClean: false,
  code: 1000,
  reason: "CloudFlare WebSocket proxy restarting",
  type: "close",
  target: WebSocket {
    URL: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    url: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    readyState: 3,
    bufferedAmount: 0,
    onopen: null,
    onmessage: null,
    onerror: null,
    onclose: null,
    protocol: "",
    extensions: "",
    binaryType: "arraybuffer",
    send: [Function: send],
    close: [Function: close],
    ping: [Function: ping],
    pong: [Function: pong],
    terminate: [Function: terminate],
    CONNECTING: 0,
    OPEN: 1,
    CLOSING: 2,
    CLOSED: 3,
    addEventListener: [Function: addEventListener],
    removeEventListener: [Function: removeEventListener],
    dispatchEvent: [Function: dispatchEvent],
  },
  currentTarget: WebSocket {
    URL: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    url: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    readyState: 3,
    bufferedAmount: 0,
    onopen: null,
    onmessage: null,
    onerror: null,
    onclose: null,
    protocol: "",
    extensions: "",
    binaryType: "arraybuffer",
    send: [Function: send],
    close: [Function: close],
    ping: [Function: ping],
    pong: [Function: pong],
    terminate: [Function: terminate],
    CONNECTING: 0,
    OPEN: 1,
    CLOSING: 2,
    CLOSED: 3,
    addEventListener: [Function: addEventListener],
    removeEventListener: [Function: removeEventListener],
    dispatchEvent: [Function: dispatchEvent],
  },
  eventPhase: 2,
  cancelBubble: false,
  bubbles: false,
  cancelable: false,
  defaultPrevented: false,
  composed: false,
  timeStamp: 0,
  srcElement: WebSocket {
    URL: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    url: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    readyState: 3,
    bufferedAmount: 0,
    onopen: null,
    onmessage: null,
    onerror: null,
    onclose: null,
    protocol: "",
    extensions: "",
    binaryType: "arraybuffer",
    send: [Function: send],
    close: [Function: close],
    ping: [Function: ping],
    pong: [Function: pong],
    terminate: [Function: terminate],
    CONNECTING: 0,
    OPEN: 1,
    CLOSING: 2,
    CLOSED: 3,
    addEventListener: [Function: addEventListener],
    removeEventListener: [Function: removeEventListener],
    dispatchEvent: [Function: dispatchEvent],
  },
  returnValue: true,
  composedPath: [Function: composedPath],
  stopPropagation: [Function: stopPropagation],
  stopImmediatePropagation: [Function: stopImmediatePropagation],
  preventDefault: [Function: preventDefault],
  initEvent: [Function: initEvent],
  NONE: 0,
  CAPTURING_PHASE: 1,
  AT_TARGET: 2,
  BUBBLING_PHASE: 3,
}
error: Unknown error
process exit 6

Got another while I was playing from the same session.

Code: Select all

socket closed: CloseEvent {
  isTrusted: true,
  wasClean: false,
  code: 1006,
  reason: "Connection ended",
  type: "close",
  target: WebSocket {
    URL: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    url: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    readyState: 3,
    bufferedAmount: 0,
    onopen: null,
    onmessage: null,
    onerror: null,
    onclose: null,
    protocol: "",
    extensions: "",
    binaryType: "arraybuffer",
    send: [Function: send],
    close: [Function: close],
    ping: [Function: ping],
    pong: [Function: pong],
    terminate: [Function: terminate],
    CONNECTING: 0,
    OPEN: 1,
    CLOSING: 2,
    CLOSED: 3,
    addEventListener: [Function: addEventListener],
    removeEventListener: [Function: removeEventListener],
    dispatchEvent: [Function: dispatchEvent],
  },
  currentTarget: WebSocket {
    URL: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    url: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    readyState: 3,
    bufferedAmount: 0,
    onopen: null,
    onmessage: null,
    onerror: null,
    onclose: null,
    protocol: "",
    extensions: "",
    binaryType: "arraybuffer",
    send: [Function: send],
    close: [Function: close],
    ping: [Function: ping],
    pong: [Function: pong],
    terminate: [Function: terminate],
    CONNECTING: 0,
    OPEN: 1,
    CLOSING: 2,
    CLOSED: 3,
    addEventListener: [Function: addEventListener],
    removeEventListener: [Function: removeEventListener],
    dispatchEvent: [Function: dispatchEvent],
  },
  eventPhase: 2,
  cancelBubble: false,
  bubbles: false,
  cancelable: false,
  defaultPrevented: false,
  composed: false,
  timeStamp: 0,
  srcElement: WebSocket {
    URL: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    url: "wss://api.truckermudgeon.com/telemetry?connectionParams=1",
    readyState: 3,
    bufferedAmount: 0,
    onopen: null,
    onmessage: null,
    onerror: null,
    onclose: null,
    protocol: "",
    extensions: "",
    binaryType: "arraybuffer",
    send: [Function: send],
    close: [Function: close],
    ping: [Function: ping],
    pong: [Function: pong],
    terminate: [Function: terminate],
    CONNECTING: 0,
    OPEN: 1,
    CLOSING: 2,
    CLOSED: 3,
    addEventListener: [Function: addEventListener],
    removeEventListener: [Function: removeEventListener],
    dispatchEvent: [Function: dispatchEvent],
  },
  returnValue: true,
  composedPath: [Function: composedPath],
  stopPropagation: [Function: stopPropagation],
  stopImmediatePropagation: [Function: stopImmediatePropagation],
  preventDefault: [Function: preventDefault],
  initEvent: [Function: initEvent],
  NONE: 0,
  CAPTURING_PHASE: 1,
  AT_TARGET: 2,
  BUBBLING_PHASE: 3,
}
error: Unknown error
process exit 6

[edit] June 13, 2026
I'm thinking that the errors I'm seeing here are Cloudflare oddities and might be why things keep getting terminated for some reason. I'm getting them consistently now at around 45 minutes to a bit over an hour at times before I get the connection terminated or something. I opened a GitHub issue about me re-writing the Wiki instructions for hosting ones own instance after I spent a literal entire day at it. I plan to run my own instance as a test to see (I do not intend to open this to the public) whether or not I'm still going to get those disconnects, or I'll get different errors, or... it Just Works™. I've already tested the edits and all that to verify it connects to my own instance at least, so that'll be fun to do.

The only hurdle is that compiling a Windows binary is a bit of a hassle since I'm on Linux. The repo uses a GitHub Actions runner to build all of the binaries, which is fine, but doesn't work too well for cross-platform stuff unless there is some additional instructions on that, or perhaps it is meant to be done on a single platform or something. I dunno... Maybe it'll all get figured out.

So far, that's where I'm at in this project. On the bright side, I can easily help provide new tilesets if necessary if there are any map changes or new DLC's and you haven't gotten them yet, or haven't gotten around to it due to being busy or something.

[truckermudgeon]

@TwinShadow thank you so much for that bug report! And apologies for the late reply: I've had to deal with some life + work things this past month, and am only now able to get back to my trucksim hobby

The "CloudFlare WebSocket proxy restarting" error message is extremely useful: the Navigator app should be able to recover from that (currently, I'm extremely conservative about what errors can be auto-retried). Expect some updates soon