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...]

any updates on this case please?

Removed MOD_Featureline.c. No longer needed.

A symbol problem in one of the python script. Fixed. Sorry...

Undone Freestyle changes.

Changed target material and layer selector from number into string selector.

Issue is fixed for me with latest master. Perhaps it's something to do with all the bump-mapping related commits recently.

So afaict, you can enable that, save preferences and should be fine?

Hello! So i created another task like this, but it was for meshes. https://developer.blender.org/T65893

I think T57389: Culling not working correctly when using array modifier is related [seems like bounding box is not correct in our case here?].
I know @Bastien Montagne (mont29) has all hands full, but maybe he is interested?

Can confirm, think something similar was reported before, let me dig that up...

Thx for investigating.
Not sure how we ran into the situation that Preferences -> Editing -> Objects -> Duplicate Data -> Light Probe got unchecked tbh.
So afaict, you can enable that, save preferences and should be fine?

but another problem appears:
When you do Reset To Default and open Preferences then WHOLE BLENDER UI LAGS as HELL ! :)
Until rerun. After restart works fine.
It also works like that when you run 2.81 with no config directory and when you pick the usage of config from the 2.80 version.
Then after that when you open Preferences Blender will LAG as hell till restart.

FOUND!
Just a config checkbox:
Preferences->Editing->Objects->Duplicate Data->Light Probe [ v ]
This Light Probe option needs to be checked.

I have checked.
This is not an add-on. I have disabled all add-on and rerun Blender but problem still appears.
Still searching for the cause...

This looks a bit like T69278.
this might be caused by an Addon?
A good way to help track down the problem would be to disable Addons one by one and see if any of these might cause the issue.
You could also have a read in T69278 and see if you are running into any other issue mentioned there (Single User)
Thx in advance!

Hi. Philipp. Thanks for checking.
After Reset to Defaults it works.
But I have all my UI setup already done and how can I fix this problem avoid reset to defaults ?
It is quite strange that kind of behaviour need total Blender reset.
Maybe it is another way ?

I cannot reproduce this.
Tried both 2.80 and current master and for me the objects as well as the datablocks have unique names and I can edit all their properties [resolution etc,] independently...

• could you check if this happens with Factory Settings as well?
• could you check if this happens with a fresh build from https://builder.blender.org/download/?

i have followed your instructions and it has failed so find above the system info

Seems you are using a blender version from 2019-04-03, could you check the same in a current build from https://builder.blender.org/download/?
Also try upgrading your GPU drivers.
If all that fails, please post the output of Help > Save System Info here...

Thats because you are not using a Mac with a Vega video card. Its been confirmed on another thread that its a Vega specific issue.

I cannot reproduce it on OSX 10.12.6

Can confirm what is described here.
However I am not sure hiding them from the viewport is actually desired here, since hiding them in the outliner doesnt really take away their influence on the render.
So this might give you the (false) impression that this cache will not contribute to the render if it is not visible.