Did you install the in-game app? See the set-up guide PDF. Is the in-game app able to connect?
The .exe and the in-game app work together (in fact, the in-game app launches and triggers the .exe). Essentially the in-game app provides the data and the .exe does all the processing. Obviously AC needs to be running though
If it's not, the .exe will give the error you described.Haha ok, fair enough. Cheers
Of course. The way development works for these sort of things is that you make it in large part because you want to use it yourself lol. And sure, actually I think telemetry sharing can be just as useful (if not more so) as set-up sharing. At the end of the day though, decent racing against decent opponents wheel-to-wheel is what it's ultimately all about
No, at the moment ACTI deals only with a single car (i.e. the remote player's car). I was thinking at one point to bring in timing / positional data for the other cars on track as well but at the time I decided that there are other apps out there that already do something like that so I didn't implement this feature. Maybe at some point in the future I'll come back to it...
Does it say that it started the external Motec converter? If not, then you probably are not driving a full lap around the track. You have to cross the start/finish line at least once in order for the current stint to be recognized. Otherwise you have to use the "Force Splice" function. Also, make sure that the ascii_to_motec.exe program (located under /bin/) is not being blocked by AntiVirus etc.
See the set-up guide that's part of the acti package. Basically all you have to do is specify the other PC's IP address in the trigger control settings and start acti.exe on that PC. Connection should happen automatically after that.@KLGreene At first thanks a lot for this great tool, it works great!
But is there any guide for setting up the live telemetry, so that it is possible to send the data immediately to an other pc system?
