Am I smoking something or did IS_CPP always report a (0,0,0) vector if not in Shift+U mode? The docs just say:
So the behavior outside Shift+U is not defined. I thought it used to actually provide the camera's current position.
The reason i ask is that if I hit the Shift+U, it enters the mode at the place the current car was at that point, but if i request a IS_CPP, just set the ShiftU flag and send that back, it puts the camera at (0,0,0) and makes LFS upset.
The only workaround I can see is to request a IS_CPP and get the IS_MCI for the current car and use that coordinate info to mod the IS_CPP before sending it back.
// Position vector (Vec Pos) - in SHIFT+U mode, Pos can be either relative or absolute.
So the behavior outside Shift+U is not defined. I thought it used to actually provide the camera's current position.
The reason i ask is that if I hit the Shift+U, it enters the mode at the place the current car was at that point, but if i request a IS_CPP, just set the ShiftU flag and send that back, it puts the camera at (0,0,0) and makes LFS upset.
The only workaround I can see is to request a IS_CPP and get the IS_MCI for the current car and use that coordinate info to mod the IS_CPP before sending it back.