VE has multiple definitions.
VE table depends on who programmed the ECU, and some have more options for enrichment interactions than others and some have more complex airflow characteric models than others.
I have written software applications to automatically tune VE tables in 2001 stand-alone ECU
https://www.thirdgen.org/forums/dfi-...der-950-a.html
My understanding of ECU to engine behavioral tuning and what a VE table is doing from over 20 years ago was better then than most people on this forum will ever achieve in a lifetime. You really need a programming background to understand microcontroller capabilities otherwise you can not grasp possibility boundaries. Many cannot fathom how a computer is 'thinking' and this is a hurdle between the reality of what a computer is capable of doing and what they perceive as 'correct' and 'typical' or 'original'. It is the major source of frustration for them when they read my words and cannot interpret or make the jump between something like VE and injector on-time in terms of code.
The definition in terms of VE for coding is not conceptual, it is idiopathic. We do not program the ECU therefore we are at the whim of the unknown programming, underlying conditions we could call it.
When we say something like VE Is ______. This can be true for some computers but not others. You must define the scope for which you pretend to evaluate the word VE.
For Haltech, I would say VE is merely injector on-time and that larger VE values result with larger injector on-times. It is that simple. If you want to globally reduce the perceived VE values you would simply adjust fuel injector size globally or engine displacement globally and walaa- a new VE table shape and form emerges for the same old engine.
In HPtuners it is a tiny bit more complex because the airflow modelling also influences other tables such as friction (calculations for torque) and transmission pressure (torque during a shift = pressure). However these limitations are merely perceived if you have not built and understood how a transmission works from the mechanical point of view. For example you can easily use a external transmission pressure gauge to dial in the force motor current table to desired real-world pressure no matter what the airflow model suggests. There is always some solution if you understand what the ECU is capable of and what is isn't. Another example I frequently see people complain about timing for boost, the g/cyl limitation in the timing map. They seem to think that because the table maxes out at 1.2g/cyl that you cannot adjust timing beyond that point. When in reality there are a couple other tables which allow us to continue to adjust timing into boost, AFR advance for example, some ECU have that table to change timing based on air fuel commanded ratio. Then by adjusting the commanded vs actual air fuel ratio we can achieve any desired timing at any boost despite the limitation of g/cyl timing table. It isn't so much thinking outside the box as it is just knowing what tools you have available I guess. But that means people are not looking at their software, they aren't delving into the possibilities offered to them, they don't check every table and read it and try to make sense of it. I could not imagine owning a piece of software that does anything and not understanding every single option contained within- but that is the difference some people don't care and suffer the consequences.