Interesting, I've only tested this with standard AI offline and it seemed to work fine (with different names of course). Your config seems correct as far as I can tell. Maybe something is different with the driver names on an online server. I'll check if I can find the problem and solve it. Otherwise I might contact you again.Hey AW939,
Wanted to do a little sanity check on myself. I've been using your v2.4 for the past couple days, and just installed v2.5 earlier today (both clean installs).
In both the new Free-Roam Color and Free-Roam Class modes: seems to be an issue with auto-filtering the traffic drivers by name prefix on all the servers I've tested.
View attachment 582498 View attachment 582499
View attachment 582500
Attached are two examples of servers running AssettoServer with generated AI traffic. Both (all) cases the traffic driver names are "Traffic XX" and the servers are setup to use the same cars for traffic as the drivers. Tag settings for the app are set to defaults. As an experiment I tried changing the Traffic Name Prefix setting to both "Traffic " (with a space after) and "Traffic," both with no change in result.
As a counterpoint, when connecting to a server that uses traffic-specific cars that I have manually tagged in Content Manager with the #traffic tag, these cars do get filtered and rendered correctly in the new Free Roam Color and Free Roam Class modes (with the new default settings of a smaller grey circle). Screenshot of this behavior also included below, for reference.
View attachment 582501
Wanted to check in and see if any others are seeing different/correct behavior? Or if I have overlooked something.
Thanks again.
Edit: send you a message with a test build, maybe you could test that, to see if it helps.
Last edited: