| |

Can’t see or select light probes

Bycodemonkey

Can’t see any light probes? Make sure your Light Probe Group is selected in the Hierarchy. Still not visible? Make sure to enable the Gizmos button in the top-right of your Scene view tab. Still not visible? Click the down arrow next to the Gizmos button and make sure the checkbox near LightProbeGroup is enabled.

Still not working? I’m out of ideas, sorry!

Moving on…

Are you having problems selecting light probes in your scene? Do you only have one Inspector tab open? Try closing the Inspector tab and re-opening it:

Are you having problems selecting light probes in your scene and you have more than one Inspector tab open? Try the above solution first. If that doesn’t work, make sure all Inspector tabs are visible. Then, click Edit Light Probes in one of the Inspector tabs and try to select a light probe in your scene. Doesn’t work? Click Edit Light Probes in a different Inspector tab and try selecting a light probe. Still not working? Keep repeating through all visible Inspector tabs, eventually one of them should work.

Still doesn’t work? Try selecting on of the default layouts available via Window > Layouts menu.

Similar Posts

| | |

Asset Prefab preview image thumbnails are black, missing, outdated, or incorrect

Bycodemonkey

Are you using Universal Rendering Pipeline (URP) and some prefab previews in your Project > Assets folders are black, missing (shown as blue cubes) or not reflecting changes you made to prefabs? Just right-click on one or more prefabs and select Reimport and wait a couple seconds. If the preview images are still black, missing…

| | |

Unable to apply changes to a Prefab

Bycodemonkey

Ever make changes to a Prefab in your Hierarchy and click in the Inspector under Overrides > Apply and nothing happens? That’s because your Prefab has at least one reference to something outside of the Prefab itself. Simply move these referenced objects/scripts inside the prefab (or delete the references to things outside of the Prefab…

|

Don’t compare floats or Vector3 variables directly

Bycodemonkey

Since the float implementation in Unity is built for performance and not accuracy (which is why in the Editor you will often see weird values like 0.000000001 instead of 0), you should never compare float values with the equality operator such as: if (floatVar == 0.5f) { … } …otherwise the result will most likely…

| | |

Speeding up Addressable Assets Loading

Bycodemonkey

Are you using Addressable assets in your project? Is loading very slow, especially while pressing Play in the Editor? Make sure you are loading a list of Tasks and running them in parallel instead of individually waiting for each Task to finish. // get locations of all Addressables var locations = await Addressables.LoadResourceLocationsAsync(label).Task; // this…

Leave a Reply