Posts by Wotever

We are closing this forum. The support is still available.

In recent years, a large and active community has emerged on our Discord server. Many members are therefore no longer active in this forum and contributions from new users were not answered or only answered late. We are therefore closing this forum with immediate effect. Old posts will still be visible, but it will no longer be possible to write new posts. You can find our discord server here: https://discord.com/servers/tml-studios-224563159631921152

    Wotever where you buy a board with a meter and other accessories, show me the store :)

    There is no store, it's all based on "do it yourself" you can find all the documentation on my website.
    I won't give much more infos here, I don't want to hijack this thread from it's original purpose which is about telemetry implementation ;)

    Buying a steering wheel and manual gears that will be in the game, playing with a keyboard with such equipment is a bit strange Wotever :lol:

    Ah ah yes, I have everything under the scenes, but when developping, keyboard is still the best way to quicky switch from game to code and vice versa :D Coding when having the wheel in front of you with the keyboard on the laps is clearly hardcore and even physically painful :D (back pains ...).

    Timo

    It's a physical limitation of the arduino driving it indeed, I can go lower but the needle will be a bit jumpy in this range.

    Wotever Looks very nice! I really should try out your tool


    Our games are base on the same code base. So the telemetry interface will be included in Tourist Bus Simulator with the next update. Also it will be included in The Bus from the beginning.

    Perfect ! I was pretty convinced it would come, it was just to make sure :D
    Just digging into the new data, what is the unit of enginetemperature ? I get 0.181385 as a value, it does not looks like °C, °F or any units i'm used to.

    The Speed will be available in the next update. Also i've added a timestamp in the HTTP header and enabled keep alive support. I think suspension data would be possible to.

    Received the update !

    Thanks !

    - Got some very good results with suspensions informations for basshakers, giving straight "previous" and "current" information was a good idea, it makes easy velocity guessing :
    pasted-from-clipboard.png

    - Tested with french, vehicle data is not cut anymore !
    - Speed data works perfectly !

    I little demo driving a physical cluster ;) Dont hold a phone while driving :D rule #1 :D

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.


    PS : Such concept is planned to be expanded to other games soon ? (Tourist bus simulator for instance)


    how exactly is it placed and on what device Wotever Mathias no instructions on the exact settings and devices

    The telemetry won't give you any useable feature alone,
    Personnally I'm implementing it in my own software allowing to build external dash compatible with windows (using a secondary monitor), phones or tablets, it also supports external hardware (leds, 7segments displays ...)

    Definitely lacks a speed data ;)

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Mathias Amazing thanks !

    I've continued experimenting with the api, i had a few small issue :
    - Keep alive support, the server does not supports keep-alive, which leads pretty fast to free socket exhaustion. I had to force close all sockets before the time_wait delay as they can't be reused. I have a workaround for this but it forces me to go socket level to avoid issues.

    - Speed ;) , I could not find current speed in the vehicle data, I have location but the vehicle packet has no timestamp which prevents any client side computation.
    - Timestamp : A good way to handle the refresh rate and let consumer make accurate computations when required to to add a millisecond accurate timestamp to each api entry.
    - I've seen heavy discussions about suspensions, in order to create some bassshakers (buttkicker ...) feedback it would be interresting to add suspension velocity


    Hope that this feedbacks will help ;)

    Nicolas

    Hi !

    I gave a try to the new access however it seems that data is cut in the middle after targetGear, I tried to restart the game with no luck,
    but changing the game language to english solved it (probably because english is definitely more compact than french and makes json string shorter)

    Code
    ...... ,"TargetGear":0,"GearC



    A little additionnal question :D
    - What is the refresh rate of the data ? I usually poll games at 60fps, but not sure if it is usefull here