Using the data from CAR info binary format is for sure better than 1/4 of unsprung mass. FWIR exporting of it was added in LFS later than the discussion in this thread took place.
Have you tried calibrating it in LFS like a normal controller? I mean the steering program moving all the virtual axes through their whole ranges and then staying in neutral positions so that you can also click centering button in LFS.
PVM is not what you think it is probably. It shouldn't be confused with software like VirtualBox or VMware. PVM is just a library and API for writing parallel programs and a console for managing "nodes" on which these programs can run.
It seems this is not even necessary. PTH files (http://www.lfs.net/file_lfs.php?name=SMX_PTH_S2Y.zip) contain this information. I'll quote their specification below because I could not find it anywhere apart from the zip file.
In the console version of Dirt 2 there is no Pikes Peak. The only group B cars available are Metro 6R4 and Ford RS200 (you have to unlock them), but they are in rallycross versions. It's possible to drive them on rally stages but you don't have the co-driver reading the pacenotes. Most probably this also applies to PC version unless they've added some content.
However, doing it from scratch will take some time , so maybe you should consider playing with existing libraries like Bullet, ODE, PhysX or Havok first.
Moment of inertia is only one factor. The other is the torque, which in this case (polar rotation) is generated by the tyres. The car having much more grip (Mazda) may also more easily generate bigger difference in lateral forces of front and rear tires (assuming 50/50 weight static weight distribution for simplicity so that these forces have approximately the same arm relative to CoM of the car) and as a result bigger torque causing the rotation. With similar polar moment of inertia to Skippy, Mazda should be able to change its orientation much more quickly.
But that only means that the level of weight transfer or load transfer isn't changing. Not that there is no weigh transfer or load transfer, which are not beneficial during turning due to load sensitivity of tyres.
Automatic report generation could be optional. Of course, such system would have to be experimentally verified and its parameters fine-tuned. I will not try to guess how large percentage of time spent reviewing reports (as opposed to racing) would be acceptable to users, and it's all interrelated.
I thought meta-moderation would prevent that. Meta-moderator (trusted admin) could basically change the result of incident assessment and all the people that assessed the same incident differently would have their "fuel points" taken away (possibly leading to "fuel points" deficit if they managed to use them for racing already). In this way a single action by the admin would enforce moderation behaviour of several users. If admins have less time, they may meta-moderate smaller sample of all the incidents but make the penalty (negative "fuel points") for wrong assessment bigger to still keep users on their toes while mass-moderating.
Has anyone thought about building a system for processing reports similar in concept to mass moderation used on Slashdot? Every driver would need to have "fuel points" to be able to race and they would earn them by reviewing racing incidents. Every incident would be assessed by several people selected randomly and the result decided by majority. Assessments different from majority would be considered wrong and not give "fuel points" or even cause penalty. People reviewing incidents would be forced to learn the rules of clean racing from the very beginning. There could be a level of meta-moderation performed by admins (but with little intensity of work required) to resolve controversial cases and to make sure that the assessments are done in accordance with the regulations and not only based on common sense. Possibly a large throughput of report processing could be achieved this way and racers could even be encouraged to report even little incidents by using a simple command usable during a race (which could automatically prepare replay fragment of a certain time lengh before the moment this command was used). Maybe such solution would allow achieving very clean racing environment.
Yes, it works, but I guess it depends on console locale settings. I don't remember Live registration asking any questions about country and there are no clauses about it in the terms of use.
I decided that I cannot live without 131 Abarth and ordered non-LCE version from UK.
There are many point-to-point tracks in general but only very little part of them may be driven like rally stages with pacenotes. They could at least add pacenotes to all the trailblazer tracks, maybe also to the raid tracks (although there could be problems because of optional routes). With little additional work CM could give rally fans so much more.
IMO the graphics are not that great, especially when compared to Dirt 2 or even Shift (it's not the blur that I like in them though). It is detailed and crisp but just does not seem very impressive to me. OK, maybe that means it is lifelike. The cockpit view is really half-cockpit view or even quarter-cockpit view to be exact.
"Slip fraction" from RAF is not slip angle. It's defined here (and in the RAF spec).
RAF does not contain slip angle directly. I am not sure if slip angle shown by F1PerfView is correct.
You can use my programs from this post to get slip angles (example). However, they are not very easy to use. Not that they are not user friendly, they are but in a geeky way. One factor that is not taken into account in the calculation is the movement (mainly lateral) of front wheel contact patches relative to car body due to steering input changes and caster (scrub radius also but its influence should be much smaller).
I just could not resist posting this: http://www.rallybase.nl/index. ... rofile&driverid=20537
Your "driving god" is over 20 % off the pace in his class (N4) when competing with international rally drivers. Imagine someone being 20 % off the pace in LFS. What would you think?