I did post about this in the update thread but it appears to have gotten a little buried/only one person saw it and had no idea yet.
Since the new update, the G-force readout has gone absolutely haywire. Here's what I've noticed:
1) The forces turn deadly at anything faster than x1 speed, even if they are totally fine at normal speed. I'll get a reading of -0.2 accel in one spot at 1x speed, and something absolutely crazy like -40.3 accel at the same spot at 4x speed.
2) There are problems at 1x speed during periods of relatively sudden acceleration/deceleration. The forces are again reading way higher than they should.
3) There seems to be a problem with force reading at 1x speed for tracks designed using Newton or FVD++, like there's a bump at every node.
Ideas? Is there a fix besides e-mailing the developers and waiting for the next update which will hopefully fix it?
ED: Someone let me know if they want a photo of the problem. I tried taking one but with pro, the G-force readout disappears in poster screens.