Open this file in Play Solo mode to see what should be happening, then try again in a live server to reproduce the issue.
The red part stops rotating ONLY in live servers because changing MaxTorque to inf breaks the BodyGyro.
Expected Behavior:
Changing MaxTorque to inf should allow the part to rotate.
Actual Behavior:
Changing MaxTorque to inf makes the BodyGyro act as if MaxForce was 0. It makes the BodyGyro do nothing.
Workaround:
Changing MaxTorque to a high value like 100,000 fixes the issue.
This is affecting the entire Ro-Aviation community on Roblox and every other game that utilizes the features. All planes are broken, other post reference here:
This is also affecting tools like drones. I’m experiencing this in two of my games. I’m wondering which change caused this issue to arise, as I couldn’t find anything related to this in the release notes of the latest update (Release Notes for 467).
Yep, I had to ‘fix’ all of my V1 plane kit derived planes, luckily I only had 4 to edit. PTFS must have hundreds.
If anyone wants to fix their V1 kit vs. wait for a Roblox client fix do this, in the Main localscript, search for torque, change any math.huge references to 100000
Its in three different places so do them all, example:
Can confirm this impacted my game but can be resolved by changing math.huge to a large number. Disappointing this happened as new users temporarily experienced an unplayable game just after they’d bought access.
Can confirm. Last night I was playing at 3am (Pacific time) and this issue wasn’t happening, but this morning I played at 11am and this issue was occurring. It has broken flying in Feather Family.
May an engineer who sees this please confirm/deny it? Since ROBLOX uses 64 bit, does that mean math.huge (aka inf) is 1.7e308 and is causing an overflow of physics running at 32 bit (limit of 3.4e38)?
yup, BodyGyros are definitely broken, i only first noticed this while attempting to play Tower of Wicked Wedges in JToH, the moving platforms wobbled uncontrollably, and found that everybody else was encountering the same issue, which is how i found this thread. Hopefully this bug gets resolved soon.