It appears ffd5e1e6acd296a187e7af016f9d7f8a9f209f87 is the commit that introduced this behavior. Perhaps due to the instruction limit described in the commit message.

It is not immediately clear to me why this is happening. I will try to debug that now.

Yeah, but shouldnt the cone be excluded from the selection buffer?

I'd definitely say yes, the select menu is a workaround (and doesn't work by emulating the MMB … )

In T70112#780756, @Martin Capitanio (capnm) wrote:

It works with the alt-LMB select menu.

It works with the alt-LMB select menu.

Can confirm, was working in 2.79

Caused by rB3a08153d7a84

As far as I can tell, the issue here is the temporal blending applied to volumetrics which is not able to reposition the volumetric lighting correctly and the Anisotropy value at 1 amplifying the issue.
You can see this phenomenon easier by setting the Viewport Samples to 1 and moving around the scene.

The light strike doesn't work even if you manually advance the frames (as oppose to playback).

Closing this as resolved. Thanks for the reply!

I have downloaded the latest driver's for my card, as well as the 2.8.1 Alpha build of blender, the problem does not seem to appear any longer as of right now, hopefully it wont happen again, if it does, i will make sure to let you know. Thank you for your patience !

To me it also seems practical as often I have Irradiance Volume in it's own collection and use the irradiance spheres visibility toggle to check stuff.

@Dariusz (Dellishia) if you update your nvidia drivers to the newest version, does it still happen?
Can't reproduce this on the 5 computers I have access to. I think it must be something with that specific GPU.

I was probably a little to quick to call this a bug...

Please go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue (so animation nodes doesn't interfere with the crash).

I can reproduce the issue. There is something wrong with the projection.

@Clément Foucault (fclem): I havent done any detective work yet, does this ring a bell for you?
(it sounds worrying, not sure though if this is rather harmless...)

I think it's more related to the de-correlation factor I applied on soft shadows sampling. The factor is ~1000 so maybe changing this factor may reduce convergence time. But it's a bit black magic at this point, it can work in some case and fail in others.

Some notes:

I did more testing on Scene1_AA flickering. To solve most flickering left I had to increase samples 1024 and the film increase "Filter Size" to 2.0 to soften the thin highlights.

Note crash will also happen if you do all this in solid mode and go to lookdev/rendered afterwards...

Can confirm.
This also happens for at least tris to quads so it is not bound to triangulate op alone...

any news please philipp

hi philipp. here it is{F7739597}

In T69751#774136, @Philipp Oeser (lichtwerk) wrote:

Not sure if there is anything we can do here...

Actually (since this is working in my simple test), could you provide the .blend you are getting this issue in?
[this makes sure we are all on the same page... thx in advance...]