- Sun Apr 26, 2020 7:54 pm
#42457
I'm getting the same behaviour as mentioned here: viewtopic.php?f=11&t=2361
I've kinda narrowed it down to firmware after 201903. If I open a log and open a tune with that firmware, the load/rpm bins all match up, and I'm able to chose different tables for display in the tuning view. If I open the most recent firmware (20202020etc), I get locked into a default load bin scale that goes from 0-240) and can only open VE1, no other tables are offered. The actual VE values are not quite correct as well, due to the y-axis scale not being 100% identical to what I'm using. The axis is off, but the actual table values are the same as my actual tune. For example's sake, I've attached the files I'm using (MLV is also the newest version).
Change the .txt file to an .mlg for it to work. It wouldn't accept the .mlg file so I just renamed it.
I've kinda narrowed it down to firmware after 201903. If I open a log and open a tune with that firmware, the load/rpm bins all match up, and I'm able to chose different tables for display in the tuning view. If I open the most recent firmware (20202020etc), I get locked into a default load bin scale that goes from 0-240) and can only open VE1, no other tables are offered. The actual VE values are not quite correct as well, due to the y-axis scale not being 100% identical to what I'm using. The axis is off, but the actual table values are the same as my actual tune. For example's sake, I've attached the files I'm using (MLV is also the newest version).
Change the .txt file to an .mlg for it to work. It wouldn't accept the .mlg file so I just renamed it.
Attachments
(57.88 KiB) Downloaded 233 times
(481.8 KiB) Downloaded 253 times