Closed quadural closed 10 years ago
I'm on it.
i tested this : i was not clear enough. This is ok on the "vehicleDataTitanium.xml" side, but then, at the script level, I need the "additionalWheels" to be added to the normal "wheels" list.
so,
<additionalWheels>
<wheel repr="0>2" radius="0.5" deltaY="0.4" suspTravel="0.2" spring="20" damper="20" brakeRatio="1" antiRollFx="0" lateralStiffness="0.1" continousBrakeForceWhenNotActive="100" />
<wheel repr="0>3" radius="0.5" deltaY="0.4" suspTravel="0.2" spring="20" damper="20" brakeRatio="1" antiRollFx="0" lateralStiffness="0.1" continousBrakeForceWhenNotActive="100" />
</additionalWheels>
should add 2 new wheels to the "wheels" section of the base vehicle xml
Ah ok, now I understand. Will fix this in a bit.
The case ih combines header are very wide. I need "virtual" wheels to simulate a self-leveling system (autocontour ?) so that the header can "follow" the landscape. To achieve that, I need to be able to add some "wheelshape" to the xml config file. Here is and example of what I need for the 3020 header :
This "system" can also be used for some tools. Example : when a tool is so "heavy" that its friction alone is above the wanted draftforce in game. In such case, we have to use "virtual wheels" so that the friction force is lowered and use the "mr" draftforce.