REDKIT / LEVEL LIGHTING / THE WITCHER 3

Green envprobes ruining your REDkit level? Repair the lighting.

Regenerate reflection-probe cubemaps, check priority and ambient tint, and isolate broken spotlight projections in custom Witcher 3 REDkit worlds.

Start fixing it ↓
Article 34 / WalkerBexUpdated 20 Oct 2026PC & Console Guide

A green lighting cast can come from the captured cubemap, probe overlap, a strong ambient tint, or a bad world export. These checks keep your original level safe while narrowing down the faulty lighting stage.

Quick Answer

Activate the probe’s layer, select its entity, then use Generate cube map in the viewport. Inspect NestingLevel, ambientColor, and effectIntensity before recooking the world. For a broken spotlight, first test its projection without the surrounding probes.

Use the reversible tests first; hardware, driver and game versions may change results.

Test the fix before changing your game

REDkit lighting isolation checklist

Select the editor tests you have completed. This diagnostic doesn't alter project files.

Environment Probe

Spotlight Projection

0 of 6 checks completed.

Editor property names supported by CDPR: NestingLevel, effectIntensity, ambientColor, ambientIntensity, areaMarginFactor. No undocumented .env syntax is required.

Follow these steps in order

01

Back up the level and identify one affected room

Duplicate the world project and open one reproducible interior. Disable nearby effects selectively and take screenshots of the editor versus cooked build.

02

Regenerate the correct cubemap

Activate the probe layer, select the EnvProbe in Scene Editor, then right-click the viewport and choose Generate cube map. If the command is hidden, confirm the layer is active and the probe selected.

03

Inspect priority and tint

Compare NestingLevel, effectIntensity, ambientColor, ambientIntensity and areaMarginFactor against a working nearby probe. Adjust one setting at a time; avoid copying guessed values into an .env file.

04

Isolate spotlight projection artifacts

Temporarily reduce probe influence, test the spotlight alone, check its projection texture/material, orientation and frustum, then turn probe lighting back on gradually.

05

Recook and verify in game

Rebuild the affected level and review it in a clean, mod-free test session at different times of day. Keep only changes that survive the cooked-world test.

What to check before calling it fixed

Repeat the same scene or test after each change. Save a record of the settings that worked and keep a clean backup so you can reverse any unsuccessful tweak.

Frequently asked questions

What is an EnvProbe?

REDkit environment probes supply reflections and indirect lighting from a captured cubemap within a defined volume.

Where is Generate cube map?

Right-click the editor viewport with the relevant EnvProbe selected and its layer active.

Does changing .env always fix green probes?

No. Many green-probe bugs are caused by stale cubemaps or overlapping probe contributions, not an environment-file value.

Can a projection texture cause broken spotlight shapes?

Yes. Test the spotlight without probe influence to separate material/projection issues from ambient lighting.

Should I overwrite original world assets?

No. Work on a backup or a copied level while troubleshooting.

Useful sources

Independent player and creator guide. Third-party mod availability and configuration options may change. Canonical URLs are publishing placeholders until confirmed on the live website.