sirnoname wrote:Yes, this are the basics. Play button in extractor leads to changing values in the input setup. If this does not work you have a problem.
Check the joystick values in the converter input setup. Are they working (independend from plugins, select a joystick in the extractor main dialog).
Normally you do not use the start button. Have a look here (3):
http://www.x-sim.de/manual/settings.htmlEnable autostart trigger and use developer plugin as trigger.
I made the test and added a joystick and enabled the autotrigger fuctions. For ETS2 everything worked like it should, all signals were received by the Converter and the autotrigger function kicked in during driving, but I had no success with GRID 2. It stays the same, if I observe the Input values (Input Setup) in the converter, I can see that the values are once updated at the time I press Play Game inside the Extractor. However afterwards there seems to be no more communication going on, the values are not transfered and the autotrigger function does not kick in, also a manual push of the "Start" button in the converter cause the "Can not start" message. There must be a difference in the way how the outsimDirt2.exe works and the plugin for ETS2, as the ETS2 plugin works. As I previously wrote, I can see that the outsimDirt2.exe receives the data from GRID 2, but the application seems to be unable to forward the data to the converter/extractor, in comparison the ETS2 plugin is able to forward the received data. I assume there is a difference between the way of communication between outsimDirt2.exe and the ETS2 Plugin, but where and how do they communicate? If they communicate through sockets, so it might be there a difference in the way how they choose the right network adapter or something similar, I have really no idea as the detailed internals are unknown to me.