Hello, i want to make an Upgrade on the GT3s to make sure everybody uses the same RearWing value but without going full Fixed setup. I'm using redapg tools to generate rearwing values to put in the Upgrade.ini. Example with only one value of 5° : Code: HDV= HDV=[REARWING] HDV=RWRange=(0, 0, 1) HDV=RWSpecial=(0,5," deg",5) HDV=RWSetting=0 I'm used to it, but on the BMW M4 GT3, for example, there is no "degrees", only P1 to P9 in the "Stock" one. How can i make an upgrade of that kind of values ? The idea is to leave only one choice in the Upgrade ... Will it work ? Thanks.
I would try putting only the RWRange=() in there. The first parameter sets which value to start from; if you make that some number, the Special command for that parameter might still take effect and define the setting as before, but because you're limiting it to the single value that'll be the only one. e.g. HDV=RWRange=(5,0,1) Then, hopefully, if there are special commands defining what each RWSetting does on the original range of values (0... x), the one that begins RWSpecial=(5, ...) will still take effect. The rest will either be ignored or won't be applied to anything anyway. If that is how it works, you may need to test which range value(s) gives the result you want, because there won't necessarily be a 1:1 correlation. By the same token, you can't wholly trust the display values shown in game; by redefining the RWSpecial value the way you are, you could end up with a different wing to the original one, despite it appearing the same. So I'd see if just the Range parameter, and relying on the original definition hidden in the car, will do it. (of course in the case of cars that have things like wings defined in the upgrades, you can see what it actually is)
Thanks, i will try using only RWRange and see it works properly. Making a BOP or trying to balance cars in rFactor2 is really not easy but it is makable. Thanks to the moddable property of rF2 and some really useful tools ...
I tried on the M4 GT3 : Code: UpgradeType="Rear Wing" { UpgradeLevel="P5" { Description="Package with only P5 Rear wing." HDV= HDV=[REARWING] HDV=RWRange=(5,0,1) } } and i get 3, without units, not P3 on the setup menu ...
I would say it would stay at 3 ... I'm trying other combinations. Can somebody explain what are each values in RWRange ? RWRange=(a,b,c) a = start value b = increment c = number of choices Is it right ?
Yes. When you do it in the described Way, the Setting has to 0, because there is only 1 Setting available and the Settings start to count with 0.
Short "Addon": If the original HDV Entries use "Special" Options, what seems to be the Case, i'm not sure if the Structure without Special Options in the Upgrades.ini will overwrite it properly. I would suggest to try it out in DevMode, with another Car. EDIT And another Problem is, that you don't know the originally used Values for the Base Setting and Steps. So P5 in the Menu can be 15 for Example.
Code: UpgradeType="Rear Wing" { UpgradeLevel="P5" { HDV= HDV=[REARWING] HDV=RWRange=(5, 0, 1) HDV=RWSetting=0 } } This one should work but i get P1 only Option. It looks like it still uses the "native" RWSpecials, because 0 is P1 natively ... I'm lost Totally unpredictable behaviour in my case ...
@DanRZ I think the biggest Problem in such Cases is, that we don't have Access to the Physics Files or at least can get some Info about such Things. So, no matter what is shown in the Menu, you never know what Values get used. Yes, that is not optimal at all.
My biggest reproach is somebody in this planet probably knows or has knwon all the "Specials" used and could probably give them. Modifying it by trial/error is not a good way to do such things ... I got some weird datas in Rear Wing setup like "C_ARM001.gmt" instead of PX when i did some random tries ... Thanks for the help/support.
It’s only my guess….and Chris and Lazza may correct me…but…if You try to make this? For dlc car, when you load it in RF2 game, you can save setup as default….and in this manner you should see the basic, default value in saved svm for the rear wing. Then, always in game, you could save other 2 setups, with the lowest, and the highest value for rear wing. In this way, maybe you could know also the range ( low-max ) of the rear wing in dlc car.
In the svm files we only see indexes and not the "Specials" values. P1 is index 0, P2 is index 1 and so on but P1 probably means 2.345° and P2 is 3.146° ... You will never see actuals Physics values in degrees in the svm files unless Physics was done explicitly by the creator like fuel, more predictable.
Hello @Nicola59 i hope you are fine. In the svm File only the Setting Number is stored and in Case of the M4 GT3 also the "Description" of the Special Option (default is P3). Ooooops, too slow..
I will use Specials in ° units hoping it work and do a few checks like Max Speed which should be lower at higher degree values ... Wish me luck
On my Tools Site i have a Special Entries Generator, you can use it to see the Structure of these Entries too.
It seems to work. M4 at 5° RearWing : 270 km/h and at at 10° RearWing : 267 km/h. We loose 3 km/h with 5° more Rear Wing. Looks legit. Edit : MacLAren at 45° gets back to 230 km/h instead of 270 at P4 Rear Wing.. Degrees values with ° are definitely working properly. I can use that to make some BOP adjustments. I just can't found the proper correspondance to P1 to P9 ...
That can be done by "some" Try and Error. With the Special Entries, you can simply use the same Value for each Option. Something like the below for Example. You "only" have to find out which Value you have to use for XXX, to gain the 270 km/h (original P5). RWRange=(0, 0, 9) RWSpecial=(0,," P5",XXX) RWSpecial=(1,," P5",XXX) RWSpecial=(2,," P5",XXX) RWSpecial=(3,," P5",XXX) RWSpecial=(4,," P5",XXX) RWSpecial=(5,," P5",XXX) RWSpecial=(6,," P5",XXX) RWSpecial=(7,," P5",XXX) RWSpecial=(8,," P5",XXX) RWSetting=0