Brightness Snaps After 20:48:58

Using Unified Lighting - Realistic - Prioritize Lighting Quality - Player Quality 10, Studio Quality 21
Although, this issue occurs regardless of Unified Lighting setting, user quality setting, or studio quality setting.
20:48:58


20:48:59


Expected behavior

It should interpolate brightness properly instead of snapping to brightness… why is this happening to 20:48:58 in particular anyway?

A private message is associated with this bug report

Hi Borange Man,

Thank you for submitting this bug report - do you mind sharing a repro file so we can try to reproduce it on our own machines? If there are any repro steps other than change the time from 20:48:58 to 20:48:59, please let us know.

Best,
M0bsterLobster

Okay, so I think I just discovered something else really weird about this.

I tried it in a blank place, then found out it wasn’t really bugging out like it used to.
Then I changed the GeographicLatitude and discovered that it does an effect on this issue.
There’s some weird behavior from latitudes 86.99-87 and 319.99-320:

  • at 86.99 it would snap at 20:48:56-20:48:57
  • at 87 it would snap at 20:49:00-20:49:01
  • at 319.99 it would snap at 20:49:02-20:49:03.
  • at 320 it would snap at 20:48:58-20:48:59

Using negative and excessive values instead didn’t seem to change much here.
This is pretty weird.

GeographicallyNotBright.rbxl (94.5 KB)

Thank you for sending that along. This turns out to be a limitation of the current system, not a bug. We know the sky system overall needs a good overhaul. We’ll add this to the list of references for when we plan this overhaul.

1 Like