You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open the Vibrant Visuals panel, Global lighting tab, in the Bedrock Editor.
Look at the sun illuminance control and its value.
Compare against vanilla resource_pack/lighting/global.json (minecraft:default_lighting), where the sun's daytime illuminance keyframe is 100.0, stepping down through 1.0, 0.01, 0.0 across the dusk transition.
4.Observe the editor's control does not represent or round-trip that value: the displayed/applied sun illuminance does not correspond to the lux value the engine and the JSON use.
All values between 0-100 in illuminance are squished on the bottom of the graph since this field expects values 0-100000 ( lux)
where in my opinion it should be something between 0-200 max .
Observed result vs. what you actually expected to happen
Observed: the Global lighting tab maps the sun illuminance value onto a range/scale that does not match the engine's lux scale. Values authored or imported at the vanilla range cannot be represented or are remapped, so what the editor shows and applies for sun illuminance diverges from what the same value produces in game and in the saved JSON.
Expected: the sun illuminance control should accept and round-trip the full lux range the engine uses. Vanilla deferred lighting files set the sun's daytime illuminance to 100, with documented dawn/dusk transition steps down to 1.0 and 0.01. From testing, the usable range is roughly 0.1 to 100. The editor value should be 1:1 with the JSON value across that range.
Evidence (vanilla source, preview branch): Mojang/bedrock-samples/resource_pack/lighting/global.json, desert_lighting.json, end_lighting.json all use a 100.0 sun daytime illuminance peak.
Other helpful info
Preview build version: 26.40.26 (Bedrock Editor 26.40.26, Windows build 46393405)
Frequency: Always
Local single-player, peer-to-peer, dedicated server: Local single-player (Editor)
Graphics card: NVIDIA RTX 4090 (DX12)
Device info: Desktop, Windows 11 Pro, Intel i9-13900KF
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Repro steps
Observed result vs. what you actually expected to happen
Observed: the Global lighting tab maps the sun illuminance value onto a range/scale that does not match the engine's lux scale. Values authored or imported at the vanilla range cannot be represented or are remapped, so what the editor shows and applies for sun illuminance diverges from what the same value produces in game and in the saved JSON.
Expected: the sun illuminance control should accept and round-trip the full lux range the engine uses. Vanilla deferred lighting files set the sun's daytime illuminance to 100, with documented dawn/dusk transition steps down to 1.0 and 0.01. From testing, the usable range is roughly 0.1 to 100. The editor value should be 1:1 with the JSON value across that range.
Evidence (vanilla source, preview branch): Mojang/bedrock-samples/resource_pack/lighting/global.json, desert_lighting.json, end_lighting.json all use a 100.0 sun daytime illuminance peak.
Other helpful info
Preview build version: 26.40.26 (Bedrock Editor 26.40.26, Windows build 46393405)
Frequency: Always
Local single-player, peer-to-peer, dedicated server: Local single-player (Editor)
Graphics card: NVIDIA RTX 4090 (DX12)
Device info: Desktop, Windows 11 Pro, Intel i9-13900KF
All reactions