@avenger82 I'll have to do some testing with starting and stopping logs at different times, to see if I've missed something there. Regarding the crashing/freezing and particular tracks, a track really shouldn't cause an issue itself so it's more likely just uncovering a fault in my plugin - unfortunately intermittent ones like that can be hard to track down (haha... 'track' down... oh dear). I probably didn't test all that much after putting in the parameter to control log capture in different scenarios (car moving etc), the actual logging shouldn't be affected but something in the building might end up corrupted. Your i2Pro graphs is a strange one. Most of my graphs I tend to have on auto scaling, so they should adjust themselves to the values automatically, while others (like ride height) I define manual ranges for and they don't change regardless of what logs I load. Your Engine RPM graph looks like it has an incorrect manual range set (if you right-click on the graph and click properties, you will see the range setting for each channel group in the table) but it's a very strange range to have defined. Actually all your graphs there just look strange, like there's some sort of vertical zoom being applied. Off the top of my head I'm not sure what options there are for that, maybe you've accidentally activated something (or pressed some keys that did it, ...). Just to check as well, are you using a current/recent version of i2Pro? Some game telemetry plugins require old versions, so I've seen people using those old versions and they can have more bugs in them - this plugin should work with the current i2Pro version from the motec website.