I'm happy to see that ISI is making new tools for us, like the new spreadsheet for suspensions. It contains 2 main parts for generating the .pm and the chassis.ini. I suppose that we must fill the white cells with data of the real cars, because I do not find a relation between the name of the cells and the name of the coefficients into the "old" HDV, in case we have data from a previous version of the mod in rF1 or rF2. I mean just for instance: first data we need for FL is "design ride height", then "Lower Front/rear/Outer", etc etc etc... and I do not think the data are available into the HDV of the rF2 mod we want to upgrade to this new technology. Is it true? Or am I wrong? But here I want to talk about the Steering Wheel values, that seem the easiest part of the spreadsheet. Data we can generate must be added manually to the HDV. I tried it, but every time rF2 crashes! Let me explain what I did to have some help and to understand what I did wrong. I know or I can calculate 2 main data: Turns Lock (that is the same of TrunsLockToLock in the HDV) and Steer Ratio (that I can calculate knowing also the Steer Lock of the car). Last main data I need is "Degrees" and I do not know what it means in the spreadsheet (so here I followed the ISI original spreadsheet that comes with data similar to the Honda NSX). Maybe other cells can be ignored (?): RackDisplacement ? SrackFract ? Also the "Wheel Range" column can be ignored... I suppose that more or less numbers of data need to generate more or less steps for the steering wheel setting in game. Here are data I wrote: - Turns Lock = 1.5 (known data both from real car and from HDV) - Steer Ratio = 9 (I calculated it from real car data knowing the Steer Lock that is 30 degrees) - Degrees = no idea at all, so I tried once writing 9 and the second attempt writing 30 I generated the following data to be added / replaced into the HDV: with 9 "degrees": TurnsLockToLock=1.5 SteeringShaftBaseLeft=(0,0.06738,-0.184449) SteeringShaftBaseRight=(0,0.06738,-0.184449) SteeringShaftAxis=(0.156434,0,0.987688) SteeringInnerTable=(0.2978,0.05078,-0.18182)-0.4562,0.05078,-0.18182) SteeringInnerTable=(0.4562,0.05078,-0.18182)-0.2978,0.05078,-0.18182) SteerLockCaption="WHEEL RANGE (LOCK)" SteerLockRange=(30,0,6) SteerLockSetting=5 SteerLockSpecial=(0,"240 ","(13) deg","TurnsLockToLock=0.666667;SteeringFraction=0.444444") SteerLockSpecial=(1,"270 ","(15) deg","TurnsLockToLock=0.75;SteeringFraction=0.5") SteerLockSpecial=(2,"310 ","(17) deg","TurnsLockToLock=0.861111;SteeringFraction=0.574074") SteerLockSpecial=(3,"360 ","(20) deg","TurnsLockToLock=1;SteeringFraction=0.666667") SteerLockSpecial=(4,"450 ","(25) deg","TurnsLockToLock=1.25;SteeringFraction=0.833333") SteerLockSpecial=(5,"540 ","(30) deg","TurnsLockToLock=1.5;SteeringFraction=1") with 30 "degrees" change only the values below: SteeringShaftBaseLeft=(0,0.065335,-0.190223) SteeringShaftBaseRight=(0,0.065335,-0.190223) SteeringShaftAxis=(0.5,0,0.866025) Into the HDV (previous): //NominalMaxSteeringTorque=10 //TurnsLockToLock=1.5 //SteerLockRange=(7.0, 0.5, 60) //SteerLockSetting=46 (new lines): NominalMaxSteeringTorque=10 TurnsLockToLock=1.5 SteeringShaftBaseLeft=(0,0.06738,-0.184449) SteeringShaftBaseRight=(0,0.06738,-0.184449) SteeringShaftAxis=(0.156434,0,0.987688) SteeringInnerTable=(0.2978,0.05078,-0.18182)-0.4562,0.05078,-0.18182) SteeringInnerTable=(0.4562,0.05078,-0.18182)-0.2978,0.05078,-0.18182) SteerLockCaption="WHEEL RANGE (LOCK)" SteerLockRange=(30,0,6) SteerLockSetting=5 SteerLockSpecial=(0,"240 ","(13) deg","TurnsLockToLock=0.666667;SteeringFraction=0.444444") SteerLockSpecial=(1,"270 ","(15) deg","TurnsLockToLock=0.75;SteeringFraction=0.5") SteerLockSpecial=(2,"310 ","(17) deg","TurnsLockToLock=0.861111;SteeringFraction=0.574074") SteerLockSpecial=(3,"360 ","(20) deg","TurnsLockToLock=1;SteeringFraction=0.666667") SteerLockSpecial=(4,"450 ","(25) deg","TurnsLockToLock=1.25;SteeringFraction=0.833333") SteerLockSpecial=(5,"540 ","(30) deg","TurnsLockToLock=1.5;SteeringFraction=1") May I have some help about the procedure to follow to avoid the crash and to have the steering wheel working? And, in addition, I'd like to know what are the meaning and the performance of the line: SteerLockCaption="WHEEL RANGE (LOCK)"... I see also for brakes a similar line: BrakePressureCaption="MAX PEDAL FORCE". Do these lines working automatically linked to the steering wheel driver? Last point: why is there a double identical description that contains different data (it seems for left and right)? SteeringInnerTable=(0.2978,0.05078,-0.18182)-0.4562,0.05078,-0.18182) SteeringInnerTable=(0.4562,0.05078,-0.18182)-0.2978,0.05078,-0.18182) How can rF2 understand?? View attachment 15483 Many thanks in advance!
Where are the Values for the "SteeringInnerTable=.." entries are taken from. Are that XYZ-coordinates? If yes, from which points? I played around with it a little bit and it seems as if a Chassis.ini is needed to make it work. Do you have one for the Palatov? And maybe there are some more entries of the "SteeringInnerTable=.." lines needed. I have taken a Corvette as pattern and added some lines. And it worked (it worked ****t_y, but it worked ) SteeringInnerTable=(0.4936,0.25,-0.398215)-0.3464,0.25,-0.398215) SteeringInnerTable=(0.454592,0.25,-0.398215)-0.385408,0.25,-0.398215) SteeringInnerTable=(0.42,0.25,-0.398215)-0.42,0.25,-0.398215) SteeringInnerTable=(0.385408,0.25,-0.398215)-0.454592,0.25,-0.398215) SteeringInnerTable=(0.3464,0.25,-0.398215)-0.4936,0.25,-0.398215) I think with a matching Chassis.ini it would work normal.
Also here; nice to see ISI making this, but with no explanation of how it works.....it's not much use. This could be really nice I think. I'm also looking for what values to put in there and I found the buttons to put out a .pm and an ultra chassis file; great! But from what
What I can say is that a person of ISI staff is working to help us in understanding how everything works. For sure the best should be to have a "legenda" with detailed explanations as well as updated documentation, but it takes time. We are not the owners of ISI and we can only hope that ISI will take the decision to spend time and efforts in updating the documentation, in detailing any single raw to give tools that can be useful also for "people of good will and enthusiastic". But from the point of view of engineers, usually it is considered like wasting time. On my side I spent my life (also working life) writing manuals and organizing and managing Technical Support Centers and my "must" was and is to produce understandable documentation, so maybe I'm not objective in my requests to have easy explanations! Coming back to the main point: how to use the spreadsheet. I'm ready to share the private beta of the Palatov D4 to people that is available to help me and later, if and when we'll be able to update the .PM + chassis.ini + hdv files to release these files to people interested into understanding this new technology. At this step, the Palatov D4 (classes "base" Custom and Trackday, that are in effect the same car for the physic) are working with the new autogenerated chassis, but with the old rF2 steering wheel; mass, inertia, cg and aero are set with real values. The other big problem is related to the TGM for the 3 compounds that comes from a tire not really appropriate to this car, also if I adapted it. But for trying the Supension Spreadsheet it is right. I'm also asked Mr. Palatov for real data to fill the spreadsheet for suspensions and data will come in inches to be converted in mm. Please PM me if you like to help me.
Hi thanks, this was a great hint @ Navigator. I possibly found a correlation. As you may know, i'm working on my suspension editor I spend lot of time to figure out, what causes my CTD by using CHASSIS INI files and strange steering behaviour by using PM files with SteeringInnerTable. HDV (C6 Z06): SteeringInnerTable=(0.5,0.25,-0.40143)-0.34,0.25,-0.40143) SteeringInnerTable=(0.34,0.25,-0.40143)-0.5,0.25,-0.40143) Chassis.INI: Name="FL_STEERING" LocalOffsetA=(0.42,0.25,-0.40142999999999995) Name="FR_STEERING" LocalOffsetA=(-0.42,0.25,-0.40142999999999995) It seems that the SteeringInnerTable looks like strait lines, with correlation to the LocalOffsetA of Bar_2 Name="FL_STEERING" and "FR_STEERING" in the *CHASSIS.INI file. These coordinates seems to be values relative to the body position of BodyA=(Front_Subbody). With other words they look like the movement- range of the steering Arm (mounted on Front_Subbody). The first x value for the left wheel provides about 8cm travel towards left wheel, the second one gives much more travel as needed to the other side. It seems, that these relative coordinate values in .hdv have to fit to the "relative" steering arm position im PM or chassis.ini, or you might get a strange steering behaviour or even a CTD. The CTD doesn't occure if the "SteeringInnerTable" lines are commented out good luck for your moddings Leonardo (Peter)
The "funny" side is, that i played around with settings that have caused a CTD too and on the way to trying to solve that, i've added the 2nd, 3rd and 4th row into the existing scheme, that it looked like that then: And the funny part is: The Values of the 3 lines came from my fantasy At the end the steering worked as wanted. It's like often mentioned before: a little more information from ISI would help a lot a would save a lot of time.
