In 4.0 Sport lights do also project backwards a small spots. This depend to the size of the spot light, a parameter used to soften the shadow caused by the spot light before.
Now all my scenes render different, I get the white round spot on a ceiling where I used a spot light. I often just use them in addition and that will reveal where ever I placed one.
So, anyone knows how to turn that off? Avoid it?
In the changes note its written: Use the incoming socket of the geometry shader node.
But that didnât work here.
Not sure how to do that âincomingâ thing either.
The only way I have found so far is to use light linking and exclude the âceilingâ from the spot lightâs linking group. (the ceiling does have to be a separate object from the lighted part)
Yeah, thats not always easy. The backside geometry output can change the color and intensity of the light, but it never gets below 1.0.
The only other solution is that size to 0.0.
In other render software the size is for reflection not shadows. Or you can set a light offset, where the light starts its effect. I tried to do that with ray distance, but again, it doesnât remove the spherical spot on the back.
I would say that at the least it is not behavior that a user would expect.
I can not see the advantage of the spot lampâs radius illuminating the area outside of its cone.
Hardly a solution. The whole thing is a total misbehavior. Its not realistic, nor physical accurate. Iâm not sure why they do not fix that.
Light Linking is not realistic and will cause other problems. The shader solution is better, but again, this is all a giant glitch.
Blender needs a user discussion on new features, or developers will ruin the software.
Nope. You have no idea what happens in production?
I have seen hundreds of cases where we run into a bug and HAD TO GO BACK.
I just have this in Blender, as 4.0 does crash MacOS with ever there is more than one UV channel, because they removed the option to switch to OpenCL.
So just a sample where I had to go back. Thankfully I only tested 4.0, but bang backwards. And there are many more bugs in 4.0.
Beside this, SOFTWARE DOESNâT demand that. Rhino, Maya, C4D all have backwards options. Modo is one of the best software here, you can go back and forth between 5-8 versions. Its a way how you develop a software. If every new feature is an option that can be skipped⌠well than its easy.
I do, yes. And due to there always being bugs in new versions, our production depts stayed on previous versions for a very extended time. People were free to play with the new toys, but under no circumstances were allowed to use for any production-level creation until the new software had been decided to be used in full. âWeâll go backwards if thereâs a problemâ was considered not an option, and absolutely not with âmade in new versionâ files.
This period could last between weeks and months, as we would do our own eval on âwhat works, what doesnâtâ as well as pay very close attention to what people outside our company were experiencing.
As to âother software doesnât do thisâ - false, it does. Not with every new release, but it happens. Blender also doesnât do it with every release, so looks to me like theyâre not outside the norm.
To be fair, 4.0.1 is the first release that caused quite a lot problems, in areas where it made no sense. Before, nearly all changes where logical and wanted.
, I just checked.