#Failed bakes 2020.3
1 messages ยท Page 1 of 1 (latest)
Let's keep going here
Ok I took a look at your logs
An initial thing that stands out: is there any particular reason you are using Enlighten?
i don't know what that is
I know it's there, but it' worse than the other two options
Ok wait
Do you have "Realtime GI" enabled?
don't know
Can you send me a screencap of the entire lighting window?
It may be slowing down your bake. I also recommend updating to most recent 2020.3 if you have to stay on the 2020 versions or going all the way up to 2021.3
I just prefer to stay on the same version to not have any updates mess up anything i have already
Has happened before and it took hours to get back to normal
Oh interesting. Can you click where it says "Progressive GPU (Preview)" and send me the options you see?
Makes sense
So even though you have GPU selected you're somehow kicking off a lot of Enlighten jobs which seem to loop around themselves
Did you only click generate lighting once or click auto generate?
Or smth else?
so they are going into a recursive state basically
and no, i did not press generate at any time
i have it on auto generate
Hmm ok that explains it
I think there's something messing with auto generate here where it enters a broken state
Not sure how you're getting enlighten jobs with no realtime gi
๐คทโโ๏ธ
sure
And don't use auto generate it's kind of bad (sorry)
As in I hate it and we're sort of getting rid of it
ok
I think going to latest 2020 is safe
No new features, just bugfixes go into LTS minor versions
i dont know if it's a unity thing or windows thing
but this copy-paste the folder seems super slow (it is on an m.2 ssd)
If it takes too long delete the library, logs and temp folders and try again
(They are generated by the editor it's non-destructive)
But if that's too scary I understand
i didnt even get the update message this time going into the duplicated project
just restart unity?
Can you check the title bar for the version?
Ok download latest 2020.3 and open in that
ok, downloading through the hub
Did someone else by any chance generate lighting for this scene before you and then pass on the project?
no, im alone on this project
created it and only one worked on it
Did you maybe work on it on a different computer?
i have opened the project on an older laptop
but i dont think i transferred the project back to my pc
i transferred through usb
Ok so your main PC has been handling the project
yes
Ok im asking this because if you baked with the Enlighten backend on separate computers there's a chance their gi caches went out of sync and are causing this hiccup
But seems not to be the case
Just a hunch. Did the editor install?
i dont think thats the case
i opened this project on the older laptop a while back and have done baking after that on my main pc
yes, opening the project right now in the newer version
Alright nice hopefully no borked shaders ๐
I did find this in your log btw
[PathTracer] Failed to render lightmap with hash: 79edbc228a0ec64e906396d147b0d478 -> scheduledDirect: 0rpt, scheduledGI: 0rpt, scheduledEnv: 0rpt
[PathTracer] Failed to render lightmap with hash: eb0c58f6a114f16d018f388b449236d3 -> scheduledDirect: 0rpt, scheduledGI: 0rpt, scheduledEnv: 0rpt
No clue what that error is, looks like the lightmapper scheduled 0 rays per texel ๐ค and then broke
Which either means that you have a really terrible mesh or we have/had a bug
when is that error from?
The first file you sent
i did get the mesh from a guy i worked with, and he did give me a lot of broken meshes at first until i fixed them
The second file looks like it's baking with enlighten
anyway, even with crazy high lighting settings and indirect multipliers
it is going really quick now
also had no errors with the updating to latest 2020 version
500 samples is pretty standard
Check the 2023.1 manual for sample counts I just rewrote it :))
increased to 5000, and still not taking too long
Yeah as it should with gpu
Are you getting decent results?
Fantastic then problem solved ๐
thanks a lot ๐
I recommend in the future using 2021.3 and don't use auto generate it's bad ๐ฆ
No worries, have fun with the project!
That has seemed to be the case
Does it do the generation itself in some fundamentally different way?
No, it uses the same backend but it saves the lighting data asset in the gi cache instead of in the project
Most of the crashes and more serious issues we have gotten on the progressive lightmapper have been timing based because you can restart the bake over and over
So in 2023.1 we only use the progressive backend in auto mode and have rewritten baking completely for on-demand
So it's now a separate thread and doesn't use any global state / state machine logic to restart jobs and sometimes crash.
Generally auto mode is bad news because it's unstable and we've been talking about deleting it for the longest time ๐