Just a quick report coming through. Hope you don't mind! I've just started working with the 1.62 version of the DW12. Since that update, MoTeC no longer reports ride height it seems. I'm using the worksheet from the second post. Does ISI no longer have that data unlocked, or is there an error in the plugin or the way the worksheet translates that? In short: how can I get the ride heights to be read out again? Thanks advance!
Bound to be the car I'm afraid. It's locked so I can't confirm the HDV entries, but in the past 'missing' data has been intentional. Worth double checking the list of logged channels, but the plugin won't suddenly change the output names so if it worked before (and/or works with other cars) it points to the info being blocked.
This is the case for others cars as well including Skippy. Ride heights stopped working with latest version release
I don't understand why the dynamic ride height would be a secret, as the ride height is setup specific and you can adjust it in the garage. So drivers need to find their own optimal ride height anyway for their setup. Telemetry is more useful than an example setup? I am hoping this is an oversight? But it would be nice to know one way or the other, in order to manage expectations of the update!
It does make you wonder, doesn't it? Just did a quick test in the DW and yep, ride height is about the only thing not being reported. And camber, but that hasn't worked yet in rF2 Testing in devmode with the skip barber, it looks to be the Code: [PLUGIN] // Whether certain sensors are available as telemetry outputs AerodynamicSensor=0 setting. This one off blocks the expected aero data (front and rear downforce, drag, front wing height) as well as front and rear ride height and the corner ride heights. If you're looking to protect the aero data I guess it makes some sense to take away the ride heights, because they would help you try to work out the aero effects.
It's beyond me. Why... iRacing gets data too and they aren't hiding anything. I'm almost certain once they get that mp4-30 data it won't be hidden for motec or atlas. Can't understand this procedure. I'm little flustered because I rely heavily on telemetry once I get into fine tuning when my other senses can't pick anything else up. Losing aero data with ride heights will be a huge let down for me. Sent from my RM-825_eu_poland_261 using Tapatalk
i agree, in GT being able to read camber under load is really important to figure out both tire wear and optimal grip in specific corners and at different fuel loads, i've been hoping at least Camber would be opened up soon but still no go..
Apparently it's now notified and possibly a bug that will be fixed with new build. Tim wasn't sure why, if and when. But something about plugin updates in the next build was said. Will see. Hope this is it.
Lets hope it is the case, but for the new version of the BT20 it was not a bug with the build, but changed in the hdv not to report ride heights (if it is for realism sake, it logs oil temps...). The FR 2014 3.5 doesn't report neither ride eights since it's first day. I simply don't drive the cars that don't log their data, and I strongly dislike cars with files encrypted, I enjoy for my pleasure tinkering with them. We have been stuck for more than a year with many URD cars having wrong motor cooling and hence temps, and brake cooling, it would have taken an hour work to solve the problem for off line racing, impossible because encrypted. The Viper was uncompetitive, could have been solved easily also. Cheers.
Since when are the URD cars encrypted? At least the Corvettes arent and I think I had a look at the others as well in the past.
I can't check at the moment the new version of the cars (not before two weeks), but I think that the hdv files were encrypted for 1.8 EGT cars. If not, please show me the content of a Ferrucio hdv. Maybe some leagues were allowed to enjoy unencrypted cars. If I am wrong I apologize, it was not my intention to spread wrong information. Cheers.
Thank you Lazza! Only have one problem. I2Pro does not let me open the log file. It says something like: This version only supports pro logging enabled files Whatever that means. What am I doing wrong?
Not directly, no. I wonder if a combination of patch&ground velocities and wheel rotation would allow you to derive it? When I get enough time around work to get the next version out I'll be open to requests for specialist channels - I think in many cases it would be easier to do in the plugin than in motec (especially any sort of sums). The current version wouldn't scale well with many 'optional' channels, plus the next one will allow extra precision. An initial version isn't far off now.
This version of i2 only supports Pro logging enabled files.. what do i download? :-D EDIT: ye just read what i should ve read before i posted my question, DLing 1,0.x
With rF1, GSC etc. we have Damper Position with 0 meaning full compression of the Damper. Now we have Suspension Position with somewhat "not that clear" scale. Any ideas on how do I know when my dampers are hitting their full course?
rF1 has suspension position (mSuspensionDeflection) and ride height, same as rF2. Neither tells you when you're hitting the bump stops.
