i did press migrate
it still looks off
1 Like
You can change the lighting mid-test in studio using the explorer and it only takes a few seconds to re-render the gameâs lighting, so it doesnât seem like it would break if changed
1 Like
This is honestly disappointing, there is no point in removing compatibility. Compatibility only disables features from voxel interally, so why remove it?
1 Like
Because you can disable the features with another instance mentioned inside of the post⌠which you clearly havenât bothered to read at all.
1 Like
Not sure that makes much sense considering itâs literally the same one they used for compatibility.
For bloom, change bloom settings.
For shadows, change ambient. How many times.
1 Like
I feel bad for you man. Seen like 50 of your posts telling people about the actual easy migration steps on retro tone mappings. I actually agree, this isnât even remotely bad update or anything itâs just⌠easy and smooth. Whatâs there to complain about? 
6 Likes
Initially, I believed this to be a terrible change that I wanted to opt out of at any chance I could, but after trying the migration out myself, I can confirm that the migration practically changes nothing (aside from some lights)
Compatibility:
Voxel:
Very nice results! I appreciate the efforts to preserve Compatibility.
3 Likes
both screenshots have bloom disabled
voxel + retro tonemapping:
compatibility:
i see no notable difference other than the point light being slightly brighter in voxel which is an easy fix
1 Like
Also, the only reason your shadows havenât changed is because your ambient is already at zero.
you shouldnât need to change your settings for a âsimple migrationâ especially when its as breaking as changing lighting colors entirely
1 Like
Well unfortunately roblox couldnât be bothered to change the settings themselves 
But itâs only 1 or 2 you need to change iirc
still breaks any script controlled lighting things
1 Like
why compatibility is exhibiting a light leaking issue? voxel solves this issue, if anything, its a slight improvement. i dont see the problem other than the bloom appearing harsher
Creator of Super Nostalgia Zone here.
This change is fine. Iâll adapt and itâs not as big of a deal as people are making it out to be. I do respect peopleâs wishes to preserve the retro aesthetic as an artistic measure, but perhaps itâd be more productive to push for more abstraction in Robloxâs rendering to allow for more cartoony/retro aesthetics.
In other words, retro aesthetics shouldnât be propped up by old technology and compatibility modes. It should be emulated and approximated through a richer modern toolset that provides that kind of flexibility.
Probably sooner than you think. Thereâs some work being done that suggests Roblox is trying to unify Lighting.Technology in some capacity:
Added Property Lighting.Intent: Enum.Intent [NotScriptable]
Added Property Lighting.Quality: Enum.Quality [NotScriptable]
Added Enum Intent
Added EnumItem Intent.Realistic : 0
Added EnumItem Intent.Flat : 1
Added Enum Quality
Added EnumItem Quality.Performance : 0
Added EnumItem Quality.Quality : 1
Added EnumItem Technology.Unified : 5 [Preliminary]
12 Likes
I liked Compatibility lighting for performance though 
2 Likes
Such as� Please elaborate further.
any day night script that makes the lighting more yellow (actually i think Middle of Nowhere may use compatibility and 100% has one of those)
There are some issues with âemulatingâ old technology with newer systems
You canât get character shadows with GlobalShadows disabled unless you make a script that monitors DescendantAdded and make all parts have CastShadow disabled