Setting any axis of workspace’s property GlobalWind to inf (as simple as 1/0) makes all terrain grass blades disappear, leaving only their shadows behind, until the project is re-run and squeezes clouds, making them look infinitely stretched on the axis perpendicular to the infinite one, until Studio or Player (desktop app) is fully restarted. This means that the problem can persist through other games. Setting an axis to nan, however, is simply treated as 0.
I first came across this issue when working with noise to create procedural weather patterns on April 5th, 2024. The bug would occur spontaneously as I had forgotten to clamp the noise function. I couldn’t find any reports of it, so I applied to enter the bug reports group.
When the issue occurs in a live experience, leaving to the desktop app and launching any game will fix the grass. However, the squeezed/stretched clouds persist until the program is fully shut down. When it happens in Studio, the clouds also remain bugged even after stopping the simulation. Setting the GlobalWind to a different value doesn’t fix the visual problems, but works as expected otherwise. Setting the Y axis or both the X and Z axes to inf will make a single “cloud coordinate” cover the entirety of the sky.
Here is a game and place file to reproduce the bug. Everything necessary should be under workspace, including a script that sets the X axis to inf after a short timer. ClockTime is also changed with GlobalWind for debugging purposes. This place is able to reproduce the bug very consistently on my friends’ and I’s systems.
globalwind bug.rbxl (60.0 KB)
System specifications:
OS - Windows 11 Pro N
CPU - AMD Ryzen 5 5600X @ 3.7 GHz
RAM - 4x8 GB DDR4 @ 3200 MHz
GPU - NVIDIA GeForce RTX 3060 Ti
I could not find another report for this bug, so please forgive me if this is a duplicate. This is also my first bug report, so please let me know if I missed any information.