Well, my logs:
Code:
>>> INFO : Assetto Corsa Telemetry Interface v1.1.2 written by Latch Dimitrov - Dec 2017
>>> INFO : Starting ACTI with loglevel = 3.
>>> INFO : Initializing...
>>> INFO : Initialization complete.
>>> INFO : Accepting incoming trig connection...
>>> INFO : ACTI Running as Subproc.
>>> INFO : Accepting incoming trig connection...
>>> INFO : Connect trigger accepted.
>>> INFO : Attempting to connect...
>>> INFO : Accepting incoming trig connection...
>>> INFO : Connect trigger accepted.
>>> INFO : PHASE2 response length = 328 bytes.
>>> INFO : Connection established.
>>> INFO : Stint recording started...
>>> INFO : Stint recording finished.
>>> INFO : Processing stint data...
>>> INFO : Finished processing stint data. Started external MoTeC converter.
asii_to_motec (starting was with content manager):
Code:
>>> INFO : ascii_to_motec converter v1.0.0 written by Latch Dimitrov - Oct 2014
>>> INFO : Starting converter with loglevel = 3
>>> ERROR : Aborting program! Line #: 185 , Filename: ascii_to_motec.cpp
But I found that if I start AC normally, then it works fine. But if I start it with Content Manager, then it does not save the file and motec converter fails.
So I googled a bit and found that it can cause problems if the driver name in content manager differs from the one in AC, but it did not solve the problem.
I can live with this, CM just helps to join online server more comfortable for me.