Usually in cases like this they roll it back. I’m a bit flabbergasted that they haven done this yet, considering they’ve done it before for lesser problems.
I can’t show off any new pictures of my game to my community until this is fixed. This sucks.
Same. I had an auditorium that used hundreds of beams to make the lighting more realistic, and I ended up having to disable all the beams. There is a really steep curve for editing transparency on beams now. When using a number sequence, or even general transparency, to get the beam like partially visible you literally have to set the variables to crazy things like 0.9985.
My game’s visuals have been significantly messed up for a week now, with no way for developers to fix these issues themselves as rebalancing visual effects would need to be reversed once Roblox fixed these bugs.
For something this impactful, being left in the dark (ahem, bright) for 6 days is disappointing.
I completely agree regarding the lack of communication – It’s been nearly a week with no communication on an issue that cripples all of my existing and upcoming maps, it would be great to hear about any updates regarding this bug so I can resume development of my games… Lets hope to hear some good news soon.
I’ve been speaking to a Roblox Staff member, and I’d like to share with what they said to me to help all of you concerned with this issue:
From Roblox Staff:
“Version 430, which is now deployed to Windows, addresses the beam brightness/transparency issue many folks have reported duplicates of the same issue. Version 431 will include update for the SSAO issue that was reported and also the rope not being fogged.”
I greatly appreciate them reaching out, and I’d figure I could share this here to provide answers for some of you with questions regarding the situation.
When I first read your post, I had my doubts that it would fix all the issues we’re seeing as the message you showed us from Roblox staff mentions nothing regarding the issues for fog itself. Version 431 was released yesterday and while I’m very happy to see that the SSAO issue is fixed, there are still problems that are left unsolved.
Additionally, as previously mentioned, fog is appearing a lot “thicker” than usual.
Here is a photo provided by one of my players showing an area before this issue started occurring:
It looks to me that fog is starting much earlier without the FogStart property ever being touched (in both images, FogStart was always set to 0 and FogEnd always 1500). While this can easily be fixed by developers adjusting the FogStart/FogEnd properties accordingly, the question is whether this change was intentional and permanent or entirely accidental and temporary?
I’d be VERY happy if you could ask the staff member you’ve been contacting if these issues have been noticed? And if that’s the case, when (and if) they’re planned to be fixed!
I just took a screenshot of the settings before the issue, then changed them to the best of my ability to try to get the look back to the original look.
For me personally 2 weeks is a lot of time and I don’t even think they fully addressed all the issues in that time frame so if i were you I would just go ahead and change the lighting settings.