I am having the same issue, but with "table ID: 1"

email incoming.

I've only been tweaking my WGDC tables to smooth out the boost curve. Load was stuck around the 2.02-2.10 range when it should have been much higher. It didn't matter if I was running 19psi or 22. Load stayed in that range. I did a pull the other morning to check my changes and low and behold loads ...

I don't know what's up. I did a little tweaking of my WGDC tables and now load is reading upwards of 2.3.
I'm confused.

Been working on my tune lately and it seems my absolute load is not going over 2.1 In the logs, once load reaches about 2.00-2.05, it's almost a perfect flatline. Did a pull this morning and the boost had a strange oscillation, but load was steady flat through that oscillation and all the way to the...

I don't like when in the dashboard, if I am trying to rearrange the PIDs, clicking and dragging a PID over an existing PID and releasing will delete the underlying PID. Sometimes my wireless mouse, or a lazy finger, loses the click while dragging and I lose a PID...then I have to look around to figu...

Interesting turn of events. I just got the above error after hitting Ctrl-A on an ignition table. VT crashed. When I opened it back up, the OTS tunes were back.

While resetting a few tables back to a previous version I've got this message. If I hit the OK button it would open a new message box. I had to terminate the VT from the task manager... https://s15.postimg.org/h151etanb/VT_fail_after_resetting_values.gif I too have experienced that error. Working w...

Is there anything wrong with setting the WGDC to 80-100% across the board during tuning and then setting appropriate values after? The ECU can correct -100 / +20, so I don't see the problem with it. I haven't done it, but I'm thinking it would save some time. Scenario: You increase the load tables. ...