At some point I would like to natively support all race sims. Not being an rFactor player though, I'd need somebody to provide all the data I need to work with their setup format, and give me some data on the tyres and aero properties of the various cars. With the very mod-based nature of rFactor though, I think I'd have to leave most of it for the user to enter, perhaps covering some of the more popular mods / official cars for reference.
This will all be much easier once I've made the tyre and aero editors, so those values are no longer hard coded into the exe. Perhaps when the time comes and VHPA is ready, I'll make some theads in the appropriate places and see how helpful people are with getting what I need.
There's your problem just kidding, as I'm sure Bob will tell you this isn't really a LFS tool but rather a true, real life car analyzer that just happens to work with the LFS cars 'cause the physics are so darn good.
-You can load LFS setups to it.
-You can save configurations as LFS setups.
-You cannot change anything in VHPA in such a way that it affects LFS in-game, if you cannot already make that change in-game.
Best way to use it (imo) is to obtain values using VHPA and then manually apply them one-by-one into your LFS setups and then fine-tuning.
VHPA is not specific to LFS, so this is expected.
Because by default an LFS profile is loaded. This doesn't mean it's the only thing it is good for.
VHPA is not an LFS setup maker. It *can* be used for it, but VHPA is what it says it is: Vehicle Handling and Performance Analyser. That means any vehicle which VHPA allows you to make a profile for, LFS car or not.
All the settings that you can change in-game can be changed in VHPA, and will load correctly in LFS (patch Y, afaik). None of the settings that you cannot change in-game that can be changed in VHPA will load correctly in LFS. That is to say, you cannot change LFS car specs using VHPA. I just checked that gearing works just fine.
Yeah, thanks, I'll add this question to the FAQ as it has come up a couple of times recently. In earlier versions you could not edit the LFS cars, so this confusion was not possible. In short, if you have to click edit and then change something in a text box, then those changes cannot be brought into LFS. If you can adjust it with a slider, then they can.
I am just a newcomer in the magic world of setups,but i feel right to say a big thanks for this great tool. Helped me alot. As i changed a value in LFS and i instantly loaded again the setup in VHPA i saw the impact that change had,so i could make a setup that suited me! The really odd is that i first found a nice and compromised setup without any test driving and then i went on track to see that this was what i wanted! I was amazed of how those graphs and a bit of trial and error in the garage led me to a set that i was confident to drive even though i hadnt done any prior driving. so no more endless driving,guessing setup changes. Thanks again! sorry but mozilla problem caused this awfully unreadable text!Problem with spacing!
Just posting to say I'm aware that the LFS vehicle presets need updating for patch Z. I'm actually about half way to v3.1.3 anyway, so I'll finish off what I started and release that with the updated data. I'll see how much I can get done this weekend but next weekend is likelier.
Hey Bob I saw that u had ferrari's and mazda rx8 for download on the website but i cant figure out how to get them to load in vhpa, its says Incorrect vehicle data file version, when i first start it up, but it will continue then when i try to load the f430 or the mazda from load user vehicles its says the same thing:Incorrect vehicle data file version.
If i try to open the set file from the regular open menu it says: this setup is for a vehicle not currently loaded in the program. load the relvant vehicle before attempting to load this setup again.
I'm still planning to add language support back into VHPA. I need a better system that what I used for GRC2 though. More importantly I need to dust off the source (not done any programming at home for months), get it matched with patch Z and finish off all the other features I've started for v3.1.3.
Once my car is starting again, the karting meet is out of the way, and I've moved house (all this month), I should have time on my hands to get the ball rolling again.
Thats good news, I'm waiting for a new version. Atm I think VHPA works best for the GTRs (:homersimp hmm, neutral setups), it seems to have some issues with the small cars, like the XFG, it seems to have a wrong limit for the spring stiffness. Only halfway through the slider is already above the ingame limit
The slider limits do not adjust on a per car basis. I didn't see the point of collecting, storing, applying, and updating all that info. TBH I can't see it being an issue during normal usage as the limits in LFS are pretty generous.
For users of v3.1.2, attached is an upgrade package of v3.1.3 for you to test. It contains updated data for LFS cars to match patch Z, as well as some other changes to the program itself. It needs to be extracted over you existing v3.1.2 install.
This release does not have all the new features I had initally planned for it, but since patch Z has been about for ages I've spent the last couple of days finishing off what new features I had started, and fixing the odd bug, and will put the other planned features into v3.1.4 instead.
I'm mostly interested in making sure the data matches with LFS again, so that VHPA is useful to LFS users once again, so if you notice any discrepancies, please let me know.
Tomorrow I'll update the manual and repackage the installer, and get this version live, assuming I can quickly fix any issues that people find in the meantime.
XRR weight and distribution are also off. VHPA has its weight as 1206kg, whereas ingame it's 1170. VHPA distribution is 51.43% whereas ingame it's 53.0% EDIT: nevermind this, the XRR default setup has 36kg added mass for some reason
mythdat - you must be comparing the figures with fuel for VHPA, to the figures without fuel in LFS. They both match for me. I have corrected the error for the FZR though. Thanks for pointing that out scipy.
duke_toaster - Yeah, that's easy enough to do.
Edit: Attached updated test version, has a few extras bug fixes, and corrected the data for the FZR and dp1. <removed again, seems there were no issues with that version>