Quote from: davidboda46 on December 19, 2016, 12:39:15 AM
I just hope it does not end up being "a Skully".
Cheers,
/David "Gonzo" Boda #46
NO CHANCE OF THAT! Skully was a huge let down for us as well. We are not going down that path.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Quote from: davidboda46 on December 19, 2016, 12:39:15 AM
I just hope it does not end up being "a Skully".
Cheers,
/David "Gonzo" Boda #46
Quote from: HornetMaX on March 25, 2016, 08:08:13 AMQuote from: asic_designer on March 25, 2016, 01:03:47 AMThe trainer (as it is already in MXb and KRP) is just a saved "replay" that is shown on track while you ride.
I agree with the "trainer" request. This would be sufficient for everyone's needs. A complete AI may perhaps be too complex, however just a simple robot/trainer which can navigate a track fast efficiently would be great. This would suit our needs definitely, just so long as we can tap into and pull data from the trainer, and have it run independently, itself on the track.
It would not fill your need asic-designer: you will have to be riding to see it (and the data will be from the bike you're riding).
Quote from: h106frp on March 10, 2016, 04:24:11 PM
Hello,
Have you considered using SimTools as one possible easy solution?
http://www.xsimulator.net/community/threads/how-to-write-a-game-plugin-for-simtools-1-0-api-documentation.4612/
To do your own you basically compile a dll (dlo in GPB) that maps GPBs shared memory area to your own memory space (codeblocks can do this easily in c++). Then either from the dll or from a host application you send the data out to the device, if you use visual studio its easy to use the ports object.
What are you trying to communicate with?