View Full Version : Memory Mapped API and UDP have different sets of values, is it going away anytime?

18-06-2018, 19:44
In particular i'm interested in rideHeight, which presents in UDP api, but not in in-memory one, which is really inconvinient. I can't figure out what mLocalWheelPositionY exactly is, and if i can infer ride height out of what presents in memory mapped file. Send help please :)