Page 1 of 1

Table dot not moving

Posted: Thu Jan 19, 2017 8:39 pm
by xgrapher
While retuning this car after a couple of months now I see that the dot on both the VE and Ignition tables that show the current position don't move. It stays where it started first. This didn't happen earlier. Tune file is attached.

Re: Table dot not moving

Posted: Sun Jan 22, 2017 8:35 am
by xgrapher
anybody?

Re: Table dot not moving

Posted: Sun Jan 22, 2017 10:00 am
by LT401Vette
can you send/post a copy of your TunerStudioAppDebug.txt with a link back to this thread?
support <at> efianalytics. com

Re: Table dot not moving

Posted: Sun Jan 22, 2017 12:55 pm
by xgrapher
Here it is

Re: Table dot not moving

Posted: Sun Jan 22, 2017 4:00 pm
by LT401Vette
You were not online during that log, so it doesn't say much in the way of a table trace.

However, it does show me that you are running on OSX with 3.0.16, there were a number of OS X fixes in 3.0.17. Please take the update and see.

Re: Table dot not moving

Posted: Mon Jan 23, 2017 9:58 am
by xgrapher
So it is not some TS option that I may have turned off by accident

Re: Table dot not moving

Posted: Mon Jan 23, 2017 12:12 pm
by LT401Vette
Nope, there is no way to turn it off.

Re: Table dot not moving

Posted: Mon Jan 23, 2017 7:11 pm
by xgrapher
Today on the dyno i was confident the 3.0.17 update must have fixed the problem but was let down. Good thing I have Windows running in parallel so I quickly downloaded TS there and everything was good. Since the past couple of updates TS on OSX sucks. It crashes, fails to startup with the startup page, quit fails so force quit is the only way out - all this happens randomly. All these bs didn't use happen ever before the last couple of updates

Re: Table dot not moving

Posted: Mon Jan 23, 2017 9:04 pm
by LT401Vette
Yes, there was a bug impacting OS X in TS 3.0.15. It caused a number of issues such as gauge images not working, ini files not being found, etc.
I stumbled on it myself and was pretty surprised none of the bugs had been reported.

This was fixed in the 3.0.17 release.

Table dot shouldn't have been effected by this. Perhaps the table dot issue is OS X specific?