Bug in VE/Spark Table Export (MAF)

[JustinHoMi]

When exporting the VE or Spark tables, Megatune rounds the MAP or MAF digits to the closet whole number. This is a problem for MAF, obviously. Can this be fixed? I've seen it mentioned on the forums a few times over the last year, but no solution has been posted. Are the megatune developers active? Is it open source?

Justin

[LT401Vette]

That isn't really a bug as much as a limitation to the VEX format. VEX only caries 2 digits for the x & y array's. I am implementing a new XML based format for table import and export in TunerStudio and MegaLogViewer that takes care of this. Expect it in releases within the next 2 months.