ShelbyUSA

Hello. Is there any further definition of the telemetry attributes below? In other words, the importance of the measurement(s) or the receipt of measurements combining? struct CarMotionData { float m_worldPositionX; // World space X position float m_worldPositionY; // World space Y position float m_worldPositionZ; // World space Z position float m_worldVelocityX; // Velocity in world space X float m_worldVelocityY; // Velocity in world space Y float m_worldVelocityZ; // Velocity in world space Z int16 m_worldForwardDirX; // World space forward X direction (normalised) int16 m_worldForwardDirY; // World space forward Y direction (normalised) int16 m_worldForwardDirZ; // World space forward Z direction (normalised) int16 m_worldRightDirX; // World space right X direction (normalised) int16 m_worldRightDirY; // World space right Y direction (normalised) int16 m_worldRightDirZ; // World space right Z direction (normalised) float m_gForceLateral; // Lateral G-Force component float m_gForceLongitudinal; // Longitudinal G-Force component float m_gForceVertical; // Vertical G-Force component float m_yaw; // Yaw angle in radians float m_pitch; // Pitch angle in radians float m_roll; // Roll angle in radians }; struct PacketMotionData { PacketHeader m_header; // Header CarMotionData m_carMotionData[22]; // Data for all cars on track // Extra player car ONLY data float m_suspensionPosition[4]; // Note: All wheel arrays have the following order: float m_suspensionVelocity[4]; // RL, RR, FL, FR float m_suspensionAcceleration[4]; // RL, RR, FL, FR float m_wheelSpeed[4]; // Speed of each wheel float m_wheelSlip[4]; // Slip ratio for each wheel float m_localVelocityX; // Velocity in local space float m_localVelocityY; // Velocity in local space float m_localVelocityZ; // Velocity in local space float m_angularVelocityX; // Angular velocity x-component float m_angularVelocityY; // Angular velocity y-component float m_angularVelocityZ; // Angular velocity z-component float m_angularAccelerationX; // Angular velocity x-component float m_angularAccelerationY; // Angular velocity y-component float m_angularAccelerationZ; // Angular velocity z-component float m_frontWheelsAngle; // Current front wheels angle in radians

Do you job. I don’t work for you. I am sure it’s not a new revelation. BTW, you’re welcome for spending the time to help this game/your revenue continues. Lazy.

Yep My video if you don’t report it in their specific format, like you work for then, it will not get fixed.

I have a concern if the current Codemaster’s business model can bear out an incredible eSports opportunity. As the eSport Event is in full stride, I am afraid there is a disconnect what your game is promoting and what your game can do. Let’s stop with pretending, it’s not a platform to promote eSports for real people with real dreams. For instance, I am curious how Codemasters are combating the replay glitch, as there will be a flood of cheaters pushing down eSport hopefuls crushing their dream. As of today, you haven’t figured out a way to combat this or done anything to ban them. I am curious if you will separate controller and wheel users, because we all know there are quite a bit advantages. I am also curious to see if the lack of long list of severe bug will have give everyone a fair chance. This is crazy. There is real money and real dreams. Level the playing field and fix it before executing. You have an amazing opportunity to get it right and you are failing.

This happens on the Xbox.

Also, it happened again tonight with another league race. The game crashed, and horrible FPS. It’s unplayable.

Fix the game. we had a league race that was disaster. Here is my video League race Xbox. the video explains all. Not sure I need to do your job by inserting it in your “template.” So, you’re welcome for helping you make this game better.

Excellent. I am waiting for SRT App to be updated or I can use another comprehensive app. I will do another comparison especially for F1 2020 and compare the difference from F1 2019.

I can send it. It’s telemetry data.

Omg. I expected this again. Folks. Data doesn’t lie. Pad is faster if you know how to use it. The pad has massive grip advantages due to the code built into the game. The data show there is less slippage both lateral and horizontal loads. Furthermore, codemasters has only built FFB code into controllers only for braking and accelerating so you can fine tune even further with grip advantages. The wheel doesn’t have this as rumble pedals are not supported. I can tell you the wheel has improved this year, thank God. But you will have major challenges if you are completing with a good driver racing with thumbs.

I am getting tons of penalties.

It’s not drivable at certain corners. It’s like the contrast or over exposure is out of whack.

1. A detailed description of the issue. Please include any error codes here. On certain parts of the track where the sun is pointed, especially when it’s in your face, I can not see the corners. For example, turn 1 and turn 5 at Austria. It’s completely white out 2. Platform Xbox One X 3. What version of the game you are using (Shown on the start screen in the bottom left corner of the screen) latest version 4. Game-mode? all modes 5. What are your replication numbers? Minimum test attempts are 4. Please also add EXACT replication steps for us to try too. 6. What troubleshooting have you attempted? Please always try to attempt to fix the issue I have tried to adjust my monitor. Didn’t work. I tried to adjust the HDR circle, did not work. I can’t adjust the gamma either. It’s locked. 7. What peripherals are you are using (gamepad, wheel make & model etc) Thrustmaster ts-xw 8. Any screenshots or video of the issue? If the video is long, please include a timestamp for when the issue appears.

I had looked at the bug reporting rules, and it followed the guidelines. 🤷🏻‍♂️

advancing game into a platform from a seasonal release to a subscription model is the only business model to support really cool ideas like this above. Shame.