when ever i try to bake lighting in simple scene unity get stuck at 5-7% only in linux version
i have tried baking on windows 11 it works fine
CPU: Ryzen 5 5600x
GPU: rx6700xt
System: Ubuntu 24.04
when ever i try to bake lighting in simple scene unity get stuck at 5-7% only in linux version
i have tried baking on windows 11 it works fine
CPU: Ryzen 5 5600x
GPU: rx6700xt
System: Ubuntu 24.04
having the same issue, but on Arch. somewhat fixed it by installing proprietary AMD GPU drivers, but now baking works only on tiny scenes (a few static cubes and a model) - on bigger ones (like the sample ones for example) it either stops at ~5% like on the screenshot above with the time remaining going up infinitely or the percentage doesn’t even show up. Trying to stop the bake also hangs the editor completely without any crash message, so can’t even include any logs.
Using the GPU lightmapper specifically, I assume? Does the CPU lightmapper also hang?
I’d check the editor log, might contain some useful leads near the end.
Not OP, but I could really use working GPU lightmapping. Can’t really find anything interesting that’d lead me anywhere inside of the log file. Tried multiple setting combinations, nothing really helps. Tried waiting as long as I could to see if it somehow would unstuck itself, but the timer went up to almost 50 hours, so I gave up and killed the process.
The CPU lightmapper thankfully doesn’t hang on my end - I incorrectly assumed that this was a GPU lightmapper specific thread, my bad.
It’s hard to say what is going on without more information. The log doesn’t give much away. The best you can do in cases like this is to submit a bug report.
One random idea if you want to investigate further: IIRC on Linux we bake in a background process called LightBaker
. You should see it pop in your process viewer of choice when you kick off a bake - do you? And if so, does anything look off the with memory consumption over time? We had some memory leak on Linux a while ago, wondering if this is a similar issue.
Submitted a report, hopefully in a correct manner.
As for the LightBaker
process, it doesn’t show up at all on my end unfortunately. Seems like it doesn’t even start anymore, or never did in the first place. The GPU isn’t being used at all, and VRAM/Memory usage doesn’t go up either.
Hmm. What does the result of running clinfo
look like?
sry for late reply i dont use arch but here is my clinfo
clinfo
Number of platforms: 1
Platform Profile: FULL_PROFILE
Platform Version: OpenCL 2.1 AMD-APP (3625.0)
Platform Name: AMD Accelerated Parallel Processing
Platform Vendor: Advanced Micro Devices, Inc.
Platform Extensions: cl_khr_icd cl_amd_event_callback
Platform Name: AMD Accelerated Parallel Processing
Number of devices: 1
Device Type: CL_DEVICE_TYPE_GPU
Vendor ID: 1002h
Board name: AMD Radeon RX 6700 XT
Device Topology: PCI[ B#37, D#0, F#0 ]
Max compute units: 20
Max work items dimensions: 3
Max work items[0]: 1024
Max work items[1]: 1024
Max work items[2]: 1024
Max work group size: 256
Preferred vector width char: 4
Preferred vector width short: 2
Preferred vector width int: 1
Preferred vector width long: 1
Preferred vector width float: 1
Preferred vector width double: 1
Native vector width char: 4
Native vector width short: 2
Native vector width int: 1
Native vector width long: 1
Native vector width float: 1
Native vector width double: 1
Max clock frequency: 2725Mhz
Address bits: 64
Max memory allocation: 10937905968
Image support: Yes
Max number of images read arguments: 128
Max number of images write arguments: 8
Max image 2D width: 16384
Max image 2D height: 16384
Max image 3D width: 16384
Max image 3D height: 16384
Max image 3D depth: 8192
Max samplers within kernel: 16
Max size of kernel argument: 1024
Alignment (bits) of base address: 1024
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: Yes
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: Yes
Round to +ve and infinity: Yes
IEEE754-2008 fused multiply-add: Yes
Cache type: Read/Write
Cache line size: 64
Cache size: 16384
Global memory size: 12868124672
Constant buffer size: 10937905968
Max number of constant args: 8
Local memory type: Local
Local memory size: 65536
Max pipe arguments: 16
Max pipe active reservations: 16
Max pipe packet size: 2347971376
Max global variable size: 10937905968
Max global variable preferred total size: 12868124672
Max read/write image args: 64
Max on device events: 1024
Queue on device max size: 8388608
Max on device queues: 1
Queue on device preferred size: 262144
SVM capabilities:
Coarse grain buffer: Yes
Fine grain buffer: Yes
Fine grain system: No
Atomics: No
Preferred platform atomic alignment: 0
Preferred global atomic alignment: 0
Preferred local atomic alignment: 0
Kernel Preferred work group size multiple: 32
Error correction support: 0
Unified memory for Host and Device: 0
Profiling timer resolution: 1
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: No
Queue on Host properties:
Out-of-Order: No
Profiling : Yes
Queue on Device properties:
Out-of-Order: Yes
Profiling : Yes
Platform ID: 0x70977dbf0fb0
Name: gfx1031
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 3625.0 (HSA1.1,LC)
Profile: FULL_PROFILE
Version: OpenCL 2.0
Extensions: cl_khr_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_media_ops cl_amd_media_ops2 cl_khr_image2d_from_buffer cl_khr_subgroups cl_khr_depth_images cl_amd_copy_buffer_p2p cl_amd_assembly_program
i start to think this amd only issue for linux mybe amd drivers doing somthing in linux that dont happen in windows
Hmm… I don’t see anything out of the ordinary. At this point I think the only thing left to do is submit a bug report. This might be a driver issue caused by a specific combination or hardware and operating system - it’s happened in the past.