Ghoults
Lasse Luisu
I have questions about the aeromap feature of shaders patch
1. How do you actually use the aeromaps to add yaw sensitivity to a rear wing in a car using the map? If car has:
wheelbase 2.5m
cog 45% front, f-cog is 1.375m
cog height 0.44
wing 1.5 meters behind cog, 0.5m above
Would this be correct?
2. DRAG_FORCE_DELAY=0.045 ;delay for drag forces - higher numbers mean less lag.
How much time is 0.045, how much is 1?
1. How do you actually use the aeromaps to add yaw sensitivity to a rear wing in a car using the map? If car has:
wheelbase 2.5m
cog 45% front, f-cog is 1.375m
cog height 0.44
wing 1.5 meters behind cog, 0.5m above
Would this be correct?
[MAP_0]
NAME = rear_wing
MAP_CL_RH = CL_RH.2Dlut ;cl*area versus meters (ride heights at each axle)
CL_RH.2Dlut:
(wing aoa changes as front changes relative to rear. Wing height is 0.44m + 0.5m = 0.94m)
MAP_CD_RH = CD_RH.2Dlut ;cd*area versus meters (ride heights at each axle)
CD_RH.2Dlut
(wing aoa changes as front changes relative to rear. Wing height is 0.44m + 0.5m = 0.94m)
MAP_BALANCE_RH = filename.2Dlut ;ratio of front:rear cl*area versus meters (ride heights at each axle)
(map is one wing. 1 is at front axle, 0 is at rear? Would -0.3 work, rear wing being behind rear axle?)
MAP_YAW_CL = filename.lut ;degrees|multiplier
lut contents:
0|1
5|1
10|1
30|0.7
Do numbers need to go to 90? Asymmetric works, as such?:
-30|0.67
-10|0.98
-5|0.98
0|1
5|1
10|1
30|0.7
MAP_YAW_CD = filename.lut ;degrees|multiplier
lut contents:
0|1
5|1
10|1
30|0.7
FRONT_RH_OFFSET = 0.0 ;meters (static ride height offset - it adds to the ride height input that's sent to the 2D-LUT lookup)
REAR_RH_OFFSET = 0.0 ;same as above
(0 because earlier we set our 2d cd and cl maps for the correct wing height)
CL_MULT = 1.00
CD_MULT = 0.3
BALANCE_OFFSET = 0.00 ;%/100
INTERPOLATION = LINEAR ; LINEAR, CUBIC
DRAG_OFFSET = 0.00, 0.00 ;meters, meters - left/right, up/down
REAR_FORCE_DELAY=0.04 ;delay for forces at the rear of the car - higher numbers mean less lag
DRAG_FORCE_DELAY=0.045 ;delay for drag forces - higher numbers mean less lag
NAME = rear_wing
MAP_CL_RH = CL_RH.2Dlut ;cl*area versus meters (ride heights at each axle)
CL_RH.2Dlut:
Code:
0.015 0.020 0.025
0.015 1 0.95 0.95
0.020 1.05 1 0.95
0.025 1.1 1.05 1
MAP_CD_RH = CD_RH.2Dlut ;cd*area versus meters (ride heights at each axle)
CD_RH.2Dlut
Code:
0.84 0.94 1.04
0.84 1 0.95 0.95
0.94 1.05 1 0.95
1.04 1.1 1.05 1
MAP_BALANCE_RH = filename.2Dlut ;ratio of front:rear cl*area versus meters (ride heights at each axle)
Code:
0.84 0.94 1.04
0.84 0 0 0
0.94 0 0 0
1.04 0 0 0
MAP_YAW_CL = filename.lut ;degrees|multiplier
lut contents:
0|1
5|1
10|1
30|0.7
Do numbers need to go to 90? Asymmetric works, as such?:
-30|0.67
-10|0.98
-5|0.98
0|1
5|1
10|1
30|0.7
MAP_YAW_CD = filename.lut ;degrees|multiplier
lut contents:
0|1
5|1
10|1
30|0.7
FRONT_RH_OFFSET = 0.0 ;meters (static ride height offset - it adds to the ride height input that's sent to the 2D-LUT lookup)
REAR_RH_OFFSET = 0.0 ;same as above
(0 because earlier we set our 2d cd and cl maps for the correct wing height)
CL_MULT = 1.00
CD_MULT = 0.3
BALANCE_OFFSET = 0.00 ;%/100
INTERPOLATION = LINEAR ; LINEAR, CUBIC
DRAG_OFFSET = 0.00, 0.00 ;meters, meters - left/right, up/down
REAR_FORCE_DELAY=0.04 ;delay for forces at the rear of the car - higher numbers mean less lag
DRAG_FORCE_DELAY=0.045 ;delay for drag forces - higher numbers mean less lag
2. DRAG_FORCE_DELAY=0.045 ;delay for drag forces - higher numbers mean less lag.
How much time is 0.045, how much is 1?
Last edited: