As far as I know, I'm currently one of only a few tuners who actually own or have owned N54, N55 & S55 DCT cars. I have spent countless hours testing and tuning to find a good mix of torque table values and torque actual output to keep the DCT shifts smooth, firm, and as quick as possible while preventing clutch slip post shift with increase line pressure control. Just setting all the torque related tables to max value without knowing what they actually do can be a disaster to the shift quality and the fact that most of the so called tuners who have zero knowledge of DCT just make assumptions that it works for AT/MT it should work for DCT also. That is just not the case.
@Twisted Tuning &
@BQTuning can vouch for that.
Your assumption probably isn't too far off for most. You have overnight tuners who used my hacked MHD OTS maps to launch there business in scamming customers by posting up free maps like an Internet fishing game, hoping for a quick payday. Tuners who become overnight master tuners on Facebook because the post up a dyno video after making a few tweaks to an existing JB4 map and eventually learn how to flash tune while doing most of there R&D on a friends car, before you know they have fanboys telling the world this guy is the best tuner in the world. What you fail to understand is the fact that I have spent the past 10 years and thousands of hours of R&D learning the ins and outs of the tables we use, not to mention helping to define tables, port, and scale the XDF files everyone uses today. So after scaling, smoothing, testing, modifying table values, I have base maps with custom PID tables which allow for a very controlled and smooth wastegate duty making the car drive as if it rolled off the factory floor with a big set of turbos. Your overall lack of understanding leads you down the path of ease. You have made the assumption that the BMS maps are a really good starting point without understanding how the hardware they use would benefit from a better map to begin with, one that is smooth and has proper table scaling has a big impact overall. We all know piggybacks work, that has never been my argument. I moved away from piggybacks because they are nothing more than a crutch for something the ecu can already do for the vast majority of users, do it better, more consistent and smoother. The ongoing integration only strengthens the foothold it has on users to stay with their current piggyback solution even if there is something better. But I digress. At the end of the day, it doesn't really matter what you run as long as it works and you're happy with your solution. It's unfortunate this platform takes the simple way out and not the right way. There are multiple products that were integrated into this platform without the foresight of the issues they cause because the people promoting them took shortcuts to bring them to market. But that's an argument for another topic. I have already rambled enough.