It looks like you’re new here. To join in the discussion, click the register link below to get started.
Hey,Thanks for you answer!Maybe I don't get it but the float value I'm receiving is something like you said. It's like "1.5" but(!) I have to multiplize it with 5 to get the correct seconds in session. Like when I'm m_time=5.7486 secons in session my real session time is 5.7486*5 = 28.743 (example). I recognized this "failure" when i was stopping the time in session with my mobile ;D.Like you said world positions change when I leave the box. I think it's the same thing like the m_time. My values are "dancing" until i change them into the right order. But what does a "position" stand for and what can i do with it? First it's just a value for me..but is it something like meters or how do i have to interpret it?The receiving bytes is 1237 so i think this is correct. I think i'm able to calculate everything with a real physical unit (and %, too), but the rest is just a "value"?If you want pictures i can show you.Thanks a lot!Mark
Is there a way to provide Engine RPM in % for LED RPM light arrays?I use SimDash with both a DLC-247 and ProRace2 LED displays but, have to assign actual RPM values for each LED and make custom profiles for each car in Dirt4. With all other titles, RPM% automatically provides relevant RPM values for any car using a single SimDash profile.
theblacknight04 said:Also can someone please also explain how were now supposed to use more than 1 UDP device?,F1 2016 gave you options to add up to 4 UDP devices with seperate ports. Now if i try to run my MonstaDash LED which reads from port 20777 and then run a android app such as RS Dash it will try to read from the same port and all it creates is huge lag obviously as multiple devices cant share the same port numberWhos bright idea was to remove the multiple udp port option by adding broadcast mode instead? Ive tried using broadcast mode and all i get is my Monstdash light array working and the RS Dash android app is lagging like hell because its trying to use the same port!Their advise is to use broadcast mode so it can use multiple devices on the same subnet! WRONG!!!!!! maybe for multiple versions of the same app perhaps, but not seperate devices. Each device needs their own port number and you've removed that option!
well ive tried to just use the 20777 port with all my devices and its simply creates huge lag on everything.. Im not running any cheap android stuff either.. All other games work fine its just Codemasters games which is why we use the Proxy server. However for it to work you MUST change the port number in each application and set that port in the server.Sheild Tablet running RS Dash Port: CANT USE NO OPTION TO CHANGE PORT NUMBERSamsung S6 running Dash Meter Pro port 20780Monstadash DLC-247 running Simdash Port 12000Fanatec CSW running SLIMax Manager Pro Port 40555Asus RT-N66U Router
well ive tried to just use the 20777 port with all my devices and its simply creates huge lag on everything.. Im not running any cheap android stuff either.. All other games work fine its just Codemasters games which is why we use the Proxy server (CMPS). However for it to work you MUST change the port number in each application and set that port in the server(see example below)Unfortunately I cant use RS Dash which has annoyed me as its a great app but no option to change the default port number from 20777. leaving it on 20777 doesn't work as the CMPS is using the portSheild Tablet running RS Dash Port: CANT USE NO OPTION TO CHANGE PORT NUMBER Samsung S6 running Dash Meter Pro port 20780Monstadash DLC-247 running Simdash Port 20778Fanatec CSW running SLIMax Manager Pro Port 40555Asus RT-N66U Router
I am currently in correspondence with Craig from pocketplayground (maker of RS Dash) to see if an option can be added to change the listening port to make RS Dash compatible using the CMPS Server..
Thanks for all of the feedback. I'll pass this on to the dev team to look at. Regarding the temperatures and participant data, this isn't available in the Time Trial beta (wear and temperature is locked to optimal values). This will hopefully be available soon.
Are there any examples of what can be done with the world space location? I was hoping this could be used to somehow plot it on a track and be able to 'watch' the race. (Like they have in the official F1 app)
Hi,I'm on PS4 and trying to decode the data with a C# app but have some truble with gear selection.The data I get for the current gear is the following,R : 00-00-00-00N: 00-00-3F-3F1: 00-00-00-402: 00-00-40-403: 00-00-3F-404: 00-00-3F-405: 00-00-3F-406: 00-00-3F-407: 00-00-00-418: 00-00-10-41So for gear 3-6 it's the same value. Is this a known problem with PS4 or am I doing something wrong here?/Viktor
I have come across some bugs with the telemetry1. Time remaining for "one shot qualifying" (confirmed) and "Time trail" (so ive been told) is a very large number "3.402823E+38"2. Sector number appears to get frozen on real players in a MP session which are being simulated during network connection issues? In race i did (which i have the telemetry recorded for analysis) one of the players was stuck with "Sector = 2" for three whole laps (lap number was increasing, sector never changed). I suspect the player might have been having connection difficulties and their telemetry may be being simulated? if this is the case then it may be a bug that the simulated player is not updating the sector field in the telemetry. This causes major headaches trying to process the timing data if the sector number is not ticking over correctly.3. Player positions get messed up after the session has finished. In the same race mentioned above, the player (data screenshots below) crossed the line in 13th position, however after crossing the line they suddenly jumped up to p2, then p1. The other players all got shifted +1 in their positions in the data being received. So the real race winner was suddenly p2, p2 was p3, p3 was p4 etc. You can see from the screenshots below that Track Position goes from 13 at the end of the final lap (5 of 5), then drops to 2 and then 1 for the remainder of the telemetry packets being sent. The second screenshot below is the results from the game itself. The data is for the player shown in P13 in the second shot "Mortician" (Fernando Alonso), so clearly P1 is the wrong value in the telemetry as the race was won by dancslaslzo14 (Lewis Hamilton).