It most likely has to do with shadowmap impercision. Above 60 studs, shadowmaps become very splotchy and multiple aspects of local light shadowmaps begin to fall apart.
The resolution for the shadow atlas begins to appear more pixilated, the depth buffer becomes too impercise and no longer respects the shadow bias and begins to project shadows on top of the objects that are supposed to be casting them, and the amount of objects and tris the light needs to render greatly increases (when the cast shadow property is turned on) which consequently tanks performance.
Theres a lot of issues that come with increasing local light range but I agree that it should still be left uncapped to allow developers to control how their game looks, and to finally get proper inverse square light falloff.
Honestly the better solution would be to just give developers the option to bake or import lightmaps and have better control over ambient occlusion to fake shadows.
All graphics on Roblox are processed on the GPU and this rumor that Roblox does not utilize the GPU needs to stop being spread because its blatantly obvious.
Light ranges on the FiB build were uncapped because it was only meant for testing and feedback purposes. It was far from ready and still required a lot of work and optimization. The local light shadows still exhibited the issues mentioned above but to a lesser extent because the shadowmaps were rendered at a higher resolution and used a different filtering technique.
I am curious what the “Server Authority” will bring since I know developers follow this kind of format already. Server handles all the authoritative content and the clients can replicate and send requests and whatnot.
Thank you for the feedback; hear you on the lighting improvements, and we’ve passed it along to the team working on it to discuss what we can do here. Good catch on the ‘Engine can support any type of experience’ section being blank; this was an error and we’re working on getting that section repopulated.
It’s still on the roadmap; the section that contained the item ‘Engine can support any type of experience’ wasn’t correctly populated. Working on getting that fixed now.
this sounds cool but i think once this gets added the first thing thats gonna happen is all of the big game studios will merge together and control everything lol
but it would also be kinda cool to create my own empire of groups
I see “Engine can support any type of experience” section got repopulated again which is great, but this isn’t fixed yet. “Universe Navigation Back & Forward UI” is mentioned twice under “Enabling higer fidelity experiences that scale across devices”
The revamped Explorer launched recently! It was in a bit of an odd place, as it was launching at close to he same time as the roadmap, which is why the discrepancy here.
i second this sentiment, my experience Bus Simulator was pretty badly hit by the lack of cross-server chatting. it was pretty much one of the main features of the game and ever since april 30th it had to be cut, and now the chat feels a lot more barren than it used to be. it also ended up cutting features before they even got to come out, as i had made an entire cross-server whisper system months before the migration was even announced… T_T
if there end up being any updates on cross-server textchatservice please let us know!! i would really appreciate it and im sure there are a LOT of other people who would too :')
You could have kept it for a bit until Roblox actually removes the legacy chat system and begins forced migration. It’s May 2 and they haven’t done that yet frankly.
