Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
Issue ID
1331794
Regression
No
GPU lightmapper isn't detecting the discrete Intel IRIS Xe MAX GPU with 4GB memory
Open a project using the GPU lightmapper on a machine with a discrete Intel® IRIS Xᵉ MAX GPU with 4GB dedicated memory.
Observed result:
The OpenCL driver is reporting just over 3 gigabytes of global memory but I would expect the full 4GB to be available.
Both the integrated Xe GPU and the discrete one are showing up when enumerating the devices, but the Iris Xe max is filtered out.
Expected result:
The Iris Xe max is available for baking.
The amount of memory we reserve for the driver is empirical, based on our experiments with AMD and Nvidia drivers and is based just on the type of workloads the Unity editor generate. Getting a number from the driver is of course ideal but is not part of the OpenCL spec. The way we identify compatible devices is based on global memory size so one option would be to allow 3GB+ devices if they are from Intel and don't subtract the kOpenCLDriverReservedMemory chunk later. I think I have convinced myself that this is the best solution as it will work on current drivers too.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Add comment