It's not supported yet in Eevee:
Wed, Sep 11
It's not supported yet in Eevee:
This causing the test that registers and unregisters add-ons to fail.
I'm fine with a some empirically determined prefiltering.
@Pablo Dobarro (pablodp606) I've been experimenting with the sculpt mode and it seems like for the flatten brush, 0.5 normal radius is too small, it is making the brush behave weirdly, flattening but also bulging near edges, I think it should be bigger, say 0.85.
Removed unneeded code, after fixing owner_id in cycles
Ah, release/scripts/startup/nodeitems_builtins.py doesn't have a poll method like the others. But why? And why are the other nodes hidden due to the used poll methods, even when bl_use_shading_nodes_custom is False?
Cycles now set the correct owner_id
Still happens in the latest 2.81 alpha. 4ce3fbd52ae8
I'm not getting errors in the console.
All non-master commits are "unpublished" since a while now
@William Reynish (billreynish) Ah, 'non-master'. Didn't spot that before. I haven't said anything!
From reading i don't see this is necessarily a threading issue, more like some missing update tag or so? Maybe need to do ID_RECALC_PSYS_RESET or ID_RECALC_PSYS_CHILD ?
I’m mostly with @Bastien Montagne (mont29) here. It was a fun exercise to put together but I don’t think I’d actually ever enable those columns for any purpose.
Sounds like passing depsgraph to PE_get_current() will make things more clear and less fragile?
I figured out my Blender white screen issue. It's interesting, but I have a small networked farm of 6 computers that are running crowdRender. Not all computers are plugged into a monitor and they are all run remotely. I just found that if you don't have a monitor plugged into the GPU Blender hangs on a white screen at startup. Its weird behavior, but, at least I now know why I had so much trouble.
This is probably fine, since brush_edit_init() is using original view layer as well.
My two cents on the columns:
As I already answered, it’s related to scopes. I didn’t add the feature. But please don’t add bug report tickets in order to ask a question.
Issue is fixed for me with latest master. Perhaps it's something to do with all the bump-mapping related commits recently.
Why do you close this task and marked as Invalid without answering my question?
A comment perhaps related to this.
PBRT filters the environment map when creating the distribution:
Build date/time in Blender is available from py API (bpy.app.build_date and bpy.app.build_time), or from the blender --version command (the one used here to retrieve Blender version already).
We could also changing the name and description here:
Draw order for alpha under pass
I just played with 2x2 supersampling when generating the distribution, thus avoiding sampling texels exactly in the middle (= no linear interpolation). This gave me a significant reduction in noise with linear interpolation, just slightly noisier as with closest interpolation.
Indeed, it was not discussed for blender.
2.81 release is scheduled for november as far as I remember, I'd bet they won't release a corrective 2.80a version but rather count on 2.81.
The fixes will be available in the net round of nightly builds and in 2.81.
Thank you, Michael!
I don’t see any reason to accept that patch tbh… I don’t see why that would matter, especially for the manpage.
If we were to do any change in that script, imho it would rather be to use the build timestamp stored in Blender app itself, instead of current time… Note that in our CMake config there are already options to define a fixed, static date/time stamps if desired. If we actually want to follow that new thing, then would make more sense to use SOURCE_DATE_EPOCH in that CMake config. But that should remain an option, even when that envvar is defined.
Folder for the disk cache
I don't have a strong opinion here. It is more accessible in side panel and custom dir for proxies is also in side panel.
Thank you Sergey. Is the 2.8 build updated after the final release last month with these fixes? Should I reinstall the 2.8 version? Or is this fix only in the 2.81 version?
The current code samples the CDF as a piecewise linear function, but the underlying PDF is piecewise constant since it's the derivative of the CDF.
imported the file mentioned above
cannot see a file mentioned here, mind uploading it?
I think the sampling is already piecewise linear? But it's only along one axis at a time which may be the problem.
I installed the latest driver but the problem is still there.
I don't have a Windows PC to debug this. Does this patch fix the issue?