Iâd rather see all of the bugs present with Voxel & Compatibility, which has been posted by myself & various other developers, be fixed first before Legacy is killed off, rather than allowing several bugs be present.
The over compensation for Compatibility and under compensation for Voxel seriously needs to be looked into before the 9th of May.
Materials look washed out & honestly lose most if not all of their sharpness while running Voxel or Compatibility.
I think we have addressed most of the issues. If you have got concrete example of legacy->compatibility switch being game breaking⌠or just making it really ugly, please send it to me in PM or post it to this forum:
I would love if roblox could keep all their old items, it does put pressure on developers to keep their game up to date with robloxâs updates. However, roblox has to get rid of older features to bring in new features to keep performance high. Now I will say it does not take a powerful computer to run roblox, but it keeps it accessible for everyone.
Legacy is being removed because it is not nicely compatible with the new lighting system and is iirc just spliced in as a special case. Itâs not sustainable to keep it.
Loadstring is a function which loads code from a string. Roblox removed the ability for developers to use this in client scripts. If they left this function in, the client would need to have code to create Lua from a string allowing an exploiter to simply run this code and now run any Lua they want.
This is similar but it has different intentions which arenât security related. Roblox has Legacy which is a lighting system which is less realistic and less performant. Currently, Roblox needs to have all of the code to run Legacy, Compatibility, Voxel, etc and they need to be able to change the code the client uses at runtime. That means the client is doing a lot of extra work.
Robloxâs goal is to only use one method of rendering so they can in the end give us better performance, and keep their code clean. Itâs a tradeoff: More work for us to adapt our games, but in the end we get better performance, more realistic graphics, and Roblox can continue to grow.
For a platform to survive there needs to be change and this is what weâre seeing. Roblox does need to âkeep removing everythingâ because if they didnât the engine would be a cluttered, laggy mess and we would be missing tons of features we have today, and the engine would be held back by these old features
As you can see, Voxel & Compatibility both causes color to be lost or sent through the roof. Both look ugly in outside environments, and I feel like both are only good for internal environments.
This could also be fixed with new specular highlights, but this honestly looks way too ugly to be forced onto developers.
Being completely honest, I think your criticism is disproportionate. 99% of players would not even notice in that example, me included, and Iâm a complete nerd when it comes to colour and colour theory. Itâs not ever going to be completely accurate so ÂŻ\_(ă)_/ÂŻ
But in all seriousness, the difference is very slight at best. Especially considering the target audience for many games on Roblox is for a younger audience, I doubt theyâll lose sleep over this as much as you seem to imply:
It would definitely be good to fix these issues but I wouldnât say theyâve rushed anything out at all. Theyâve worked on Future is Bright for a very long time, and theyâve planned this a long time coming.
Update: Legacy was removed, all games set in Legacy are now running in Compatibility.
