GPU lightmapper preview

This is great, thanks!

 

OMG!!
and where is 2018.3b3?

 

Awesome news!

 

27th of September

 

oh snap

 

Getting good speed. about 10 times the speed of baking on the CPU.

This was a 14 core i9 CPU vs a 1080Ti graphics card.

 

damn ... i got this warning :\
what is this?


and seems that switching to CPU again :[

 

Really nice speed. Too bad, that it doesn't handle scaled meshes yet. I know that scaled transforms should be avoided in general, but there's usually no way around it and our level designers like to use scaling for a lot of things. Looking forward to the complete feature set. I'm liking the preview so far.

 

ok ... but what about this? [totally 10 GB memory??]

 

This is an exceptionally great improvement! Love it to death so far! Though now I only need to get a GPU with more memory...

 

so ... i have to planning to buying new AMD cards with more than 16 GB of vram

 

Im also getting the openCL issues as well on a gtx1080ti

 

well ... i hate AMD!! but seems that reality is different [specifically for using GPU lightmapper to baking large architectural scenes] ... GPU lightmapper can't use nVIDIA shared memory and gets lower speed when using AMD shared memory [means system ram] ... so, cuz nvidia don't have fair price cards with 16GB of vram , AMD is only real choice for now that have cards with 16GB of vram or at next release with over 16GB of vram maybe!?

 

i'm just curios about Bakery [nVIDIA Based] vs GPU Lightmapper [seems that AMD based??]

 

If they used Nvidia, I wonder if they could utilize their new RTX tech for ray traced lightmap baking.
But hey, at least it's already way faster than before.

 

RTX taking ages to implement in unity!! i guess
and its expensive tech ...

P.S: Holys**t !! i'm just testing bakery on old 750ti!! just 10 sec vs 4 hours CPU to baking an interior scene like as Archvizpro interior 1 ... its amazing!! [only nVIDIA]

 

Just tested my scene using a gtx 1080ti and it was 5 mins to bake vs over a hour with 2700x. Nice!

 

cool, and much faster...

but I have to question the workflow.
any small change and you are rebaking the entire level again and again and again.
while baking the editor is slow, and again any small change will restart the baking.

would it not make sense to preview what it looks like?
I made a proof of concept tool like a year and a half ago...stopped cause unity announced gpu lightmapper, otoy released, and bakery asset.
https://forum.unity.com/threads/wip-lightmapper-editor-runtime.473081/


even 4 years ago, you were showing preview with powervr while enlighten would bake final.

not complaining, just a critique

 

not working. what the hell.

Im have a i5 intel and 1080 ti. and it falls back on cpu. My Gpu has 11gbs of memory. That means I have to go into registry? Are there other steps I can take? Am I missing something. I know I'm not the only one with this setup, maes no since.

 

Tried a small scene and it works very well, with a larger more detailed scene it just stays "Baking..."

I have a 1080Ti.

 

It's simple to reproduce, just open the RFP2_DemoScene in the Rome Fantasy Pack II asset and try to bake it with the GPU.

(Presumably Unity devs have access to store assets for testing).

 

Try clearing the bake first from the dropdown on the bake button.

 

Seems restarting Unity fixed it, if it comes back I'll try that.

 

It seems when u bake halfway and stop it then continue to bake again u will get that issue.

 

I tried a much bigger scene than the Rome Fantasy Pack II demoscene and it doesn't work at all, gets few minutes into baking then these errors show up (below) and then it reverts to CPU and gets stuck "Baking..."

Code (CSharp):

1. [PathTracer] Loaded programs and built CL kernels in 0.092 secs -> Timestamps: [471.352 - 471.444].
2.  
3. OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_OUT_OF_RESOURCES error executing CL_COMMAND_READ_BUFFER on GeForce GTX 1080 Ti (Device 0).
4.  
5. OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_OUT_OF_RESOURCES
6.  
7. OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_OUT_OF_RESOURCES error executing clFlush on GeForce GTX 1080 Ti (Device 0).
8.  
9. OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_OUT_OF_RESOURCES error executing CL_COMMAND_NDRANGE_KERNEL on GeForce GTX 1080 Ti (Device 0).
10.  
11. OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_OUT_OF_RESOURCES error executing CL_COMMAND_COPY_IMAGE on GeForce GTX 1080 Ti (Device 0).
12.  
13. OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_OUT_OF_RESOURCES error executing CL_COMMAND_READ_IMAGE on GeForce GTX 1080 Ti (Device 0).
14.  
15. OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_INVALID_EVENT

Error # : Number of times

1 : 4
2 : 14202
3 : 4
4: 12806
5: 1408
6 : 6
7 : 4

 

I have a laptop with a gtx1080, but it says the rendering device is the intelHD card.

Is there a way to select the graphic card ? Or why is it using the onboard card ?

EDIT: did what was mentioned in the original post via command line, still falling back to CPU baking "CL_PROFILING_INFO_NOT_AVAILABLE"

 

It's works well on my GTX 1060 but sometimes i do experience some issues when it's says "out memory" and after that it's falls back to CPU

 

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

I'm just getting this error.

Also this one, not sure if its related:

Assertion failed on expression: 'IsCLEventCompleted(events->m_StartMarker, isStartEventAnError)'

My specs:

CPU - i7 7700K Intel
GPU - EVGA 1070 GTX FTW 8GB
RAM - Corsair Vengence Pro RBG 3200Mhz 2 x 16GB
MB - Z270 Mark 2

 

Seems like some sort of queue/memory management is needed to prevent this from overloading.

 

And please also release the Mac version, even if its unstable, I just want to start testing and saving time already

 

But it would probably fallback to cpu

 

Will Unity 2018.3 come out of beta till Unite LA?

 

Unity 2017.3 was released December 19th.

If they stick to this plan, I guess 2018.3 will not be out of beta till Unite LA, which starts at October 23rd, thus about two month earlier than 2017.3.

They made quite a few major changes/improvements in 2018.3, they probably need these two months to further stabilize the software.

 

Still getting memory issues in Beta4.

 

I know what you mean but ... I have a Nvidia card running on the Mac 1080 Ti

 

Yep, but those cards currently fall back to CPU too!

 

Tried Beta 5 and 6, still falling back.

Having a fallback at all gives me the impresion Unity isn't very confident in this new feature and their ability to implement it, I hope I am proved wrong though by the time of final release or my project will suffer greatly.

 

I haven’t had any problems. Working great on my end.

 

Try doing it on a huge scene.