#include <PxVehicleComponents.h>
Public Member Functions | |
PxVehicleClutchData () | |
PxVehicleClutchData (const PxEMPTY) | |
Public Attributes | |
PxReal | mStrength |
Strength of clutch. | |
PxVehicleClutchAccuracyMode::Enum | mAccuracyMode |
The engine and wheel rotation speeds that are coupled through the clutch can be updated by choosing one of two modes: eESTIMATE and eBEST_POSSIBLE. | |
PxU32 | mEstimateIterations |
Tune the mathematical accuracy and computational cost of the computed estimate to the wheel and engine rotation speeds if eESTIMATE is chosen. | |
Private Member Functions | |
bool | isValid () const |
Private Attributes | |
PxU8 | mPad [4] |
Friends | |
class | PxVehicleDriveSimData |
PxVehicleClutchData::PxVehicleClutchData | ( | ) | [inline] |
PxVehicleClutchData::PxVehicleClutchData | ( | const | PxEMPTY | ) | [inline] |
bool PxVehicleClutchData::isValid | ( | ) | const [private] |
friend class PxVehicleDriveSimData [friend] |
The engine and wheel rotation speeds that are coupled through the clutch can be updated by choosing one of two modes: eESTIMATE and eBEST_POSSIBLE.
If eBEST_POSSIBLE is chosen the vehicle sdk will compute the best possible solution (within floating point tolerance) to the implemented clutch model. This is the recommended mode.
The clutch model remains the same if either eESTIMATE or eBEST_POSSIBLE is chosen but the accuracy and computational cost of the solution to the model can be tuned as required.
Tune the mathematical accuracy and computational cost of the computed estimate to the wheel and engine rotation speeds if eESTIMATE is chosen.
This has no effect if eBEST_POSSIBLE is chosen as the accuracy mode.
A value of zero is not allowed if eESTIMATE is chosen as the accuracy mode.
PxU8 PxVehicleClutchData::mPad[4] [private] |
Strength of clutch.
Specified in kilograms metres-squared per second (kg m^2 s^-1)