Official Progressive GPU Lightmapper preview

I mostly get this error which causes the system to fallback to PLM CPU:
Assertion failed on expression: 'IsCLEventCompleted(events->m_StartMarker, isStartEventAnError)'

And then this:
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_PROFILING_INFO_NOT_AVAILABLE

 

I'm also constantly getting this error, Currently in 2018.3 b3, but this happens a lot in previous 2018.x:

There are 69 objects in the Scene with overlapping UV's. Please see the details list below or use the 'UV Overlap' visualisation mode in the Scene View or Lightmaps in Lighting Settings for more information.

for meshes part of an FBX which has "Generate Lightmap UVs" option enabled in import settings, which probably means that there are no proper uv2's generated.





And this is the actual UV - visualised in custom editor - looks ok !

 

I've tried this in a few scenes noticed that the device name has changed from 900 to 901 and had amazing GPU enhanced rendering times to CPU hogging endless rendering to crashes the IDE graphics rendering (turned black) to crashes rendering of windows (sound still worked).

What settings are best for quick rendering on the GPU without crashing or getting bogged down in clustering on GI?

 

Nvidia 411.70

 

Yeah, this is actually confusing! However i am now aware of its meaning. Will have a look at the links. Thanks a lot !

 

I feel like that gif should be in that docs page, or even better if that were somehow linked into the editor(like click the console warning for more info and that pops up).

 

Ok, the first driver is 399.07, after I updated to the version 411.70 and now I have updated to the version 416.16 (the problem on unity also persists with this driver)

GPU : Nvidia GTX 1060 6GB

The scene : https://drive.google.com/open?id=1N_P6bLpnTH1s4aUT8kJbhYkIQuGlWstn

 

Just throwing this out there, maybe something like "Texel Bleeding" would be better? Overlapping UVs implies there is something inherently wrong with the UVs, which might be false (for example, they could be just fine if you did a higher res bake).

 

I tested the GPU lightmapper in current Unity 2018.3.0b4.
Seems already stable and very promising.

But, as I already mentioned in other threads, I seriously beg Unity developers to implement a

"Bake selected object(s)" - button.

(Imagine a single table with a little cube on it in a 5x5m room.
When I move the cube a little bit it would be fine to rebake the table and not the whole room, which will save tons of time.)

Please!

 

May I ask why moving the realtime GI to GPU is not in the plan?

 

Might be because it was using enlighten which i assume Unity doesn't have access to the source code to modify it. Unlike the progressive lightmapper it was Unity developed

 

Also, brute force algorithms are easier to translate to GPU.

 

So the lastest beta 2018.3.b5 still fails to properly bake any of my scenes/tests without reverting to CPU when encountering an issue. Guess I will have to wait even longer before this become useful. Shame.

 

very bad for the same scene bake with gpu bake, what's wrong??the cpu bake good very better...

 

I highly doubt this. Unity implemented this feature into Unity, which means they had access to source code - unless there is a magical box that cannot be altered or modified but still can be accessed for use. I'd understand if there were legal issues, but source code blackbox sounds absurd.

Also we are talking about using GPU baking to bake data that is to be fed into Enlighten, which btw, is what the progressive lightmapper is doing. So it has already been done, not quite apples to apples but is a good indicator.

Nevertheless, I could be totally wrong and want to know KEngelstoft thinks.

 

well he did state this in the post above "We can't move realtime GI precompute to the GPU, as that is done inside Enlighten."

 

I see, oh well...that really sucks then...

 

Well for now we can only that hope unity have their own realtime GI in the future

 

Raytracing support is coming to HDRP, and there is SEGI for voxel based GI. In another words, Unity will most likely not add realtime GI or improve it. My guess is that they will let it slowly die hahaha!

 

cpu bake lightmap is correct ,gpu missing the shadow....

 

I got an error with the GFX 1080 and 8700K, should I install OpenCL or something?
Failed to find a suitable OpenCL device, falling back to CPU lightmapper.

 

OpenCL support is in the GPU driver. Just be sure to have the latest driver installed and you should be good !

 

Should an hd630 be faster or slower than a 8700k? I had a few bakes where the mrays was lower than the cpu but the gpu finished faster?

 

I have one question !

As GPU Lightmapper is using RadeonRays, can we expect it to run somewhat better on AMD hardware, or nVidia takes the lead here as well !?

For example do you have any comparison between let's say RX 570 and GTX 1060 as they suppose to be close on performance in general ( well 1060 should be a little bit faster ) !?

 

I've got a scene in which I'd like to bake the shadows of my terrain trees. I just went ahead and created actual objects in place of each tree, and am attempting to bake the scene with these thousands of tree objects marked as lightmap static.

I've never had the patience to let this bake via CPU, and I would like to bake it using my GPU. However, my 2080ti doesn't have enough dedicated memory to bake the scene. What is the best way to reduce the memory usage of a lightmap bake?

Thanks!

 

Failed to find a suitable OpenCL device, falling back to CPU lightmapper.
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_INVALID_PROGRAM

Drivers updated on R9 280x

 

Any idea on why the MRays/sec fluctuate so wildly between 1.5-120 MRays/s? This is baked lighting only with 200 direct, 1500 indirect samples, 3 bounces, 30 texels and 1024 res lightmaps.

I've seen some people say it may jump over to virtual memory but would virtual memory bog it down that much? Though task manager says my secondary card only uses 5gb so could it just poor scene setup on my part?


i7 6700k 4ghz
2 x GTX 1070 8gb drivers 416.34
32gb ddr4

 

CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_NDRANGE_KERNEL on GeForce GTX 1060 3GB (Device 0).

CL_MEM_OBJECT_ALLOCATION_FAILURE

 

UPDATE: Work with new drivers update 18.10.2

 

I took a video of what is going on. I think I have it somewhat narrowed down after doing different tests for the video. I figure the fluctuation is actually just a long increase in MRays/sec because it goes up slowly and only decreases a little bit. The behaviour is not due to losing focus, as you can see in the vid. Maybe Unity is displaying the average MRays and not current?
A more reproducible issue I have noticed is that the maximum MRays/sec seems to be limited by the lightmap resolution selected. Is this supposed to happen?
Sped up video:

 

I'm on 2018.3 and I don't see the option of the GPU lightmaper preview at the lighting tab.
On the Package Manager I don't see either the option to install the package.
Where can I find it?

 

There is no way to get it from package manager.
It is included inside unity already in the lighting window.

What GPU you have !?

 

Ahhh, ok. I tried on a Mac. I'll do on Windows later today. Thanks.

 

Hi!, I'm using a sapphire amd r9 270, and was wondering if it will be able to handle the gpu lightmapper
Also my CPU is an AMD ryzen 5 1400

 

I'm playing with the GPU Lightmapper in the 2019.1.0a8 build. Partway through baking I got a red console error appearing for half a second before vanishing. I had to restart the bake a couple of times to try and get a glimpse of it but it seemed to say something about out of memory. The bake continued fine however, should I assume that means it's falling back to the CPU lightmapper?

 

I have GPU R9 390 with 18.11.1 drivers ( i tried also 18.10.2) and 2018.3.0b9 unity.
And i got this same warning spam for all three lightmapper options, what is going on? (i cleared console every time before clicking on generate lighting)
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_INVALID_PROGRAM

i made video: