- User Since
- Nov 16 2016, 1:34 AM (223 w, 4 d)
Tue, Feb 23
Tue, Feb 9
Update based on review.
Thu, Feb 4
Tue, Feb 2
Jan 22 2021
Jan 21 2021
Jan 20 2021
Fixes based on feedback.
Jan 19 2021
Dec 2 2020
Nov 26 2020
Nov 22 2020
Nov 18 2020
Nov 13 2020
Nov 12 2020
Nov 11 2020
Nov 10 2020
Looking for feedback on licensing approach. But as we see it, this is directly in line with the current usage of Optix Denoising library.
Sep 9 2020
Also adding this being an issue with Radeon ProRender addon (only windows). I've tried forcefully unloading DLL but so far unsuccessfully.
May 8 2020
Yep will test. Here's what I've done so far:
Might this be related to https://developer.blender.org/T76442 ?
May 7 2020
Not sure about status how that got changed. Sybren marked it in valid, which I think is erroneous.
Furthermore. After filing this I am able to work around this by building blender from source without USD support (which obviously removes the symbol conflict), but I would claim that's not a valid workaround for most users
You're mistaken about the python3 compatibility:
USD 20.05 supports Python 3:
"Added support for Python 3. This may be enabled by specifying PXR_USE_PYTHON_3=TRUE when running cmake or by running build_usd.py with Python 3."
Mar 6 2020
Jan 21 2020
PyQt has been used for many tools within Tangent since Next Gen. The Blender UI toolkit is too limiting for certain kinds of interfaces that PyQt makes trivial.
The main loop of PyQt was fixed specifically to allow for this kind of foreign embedding many, many versions ago and requires very little code to get going. The main issues tends to be around uncaught exceptions and some threading shenanigans but it’s very doable.
Nov 20 2019
Strictly speaking about the Python 3.8 decision, I think this comment hit it on the head.
Jul 17 2019
https://www.amd.com/en/support/kb/release-notes/rn-rad-win-19-7-2 should fix it I am told.
Jul 15 2019
Thanks @Brecht Van Lommel (brecht) That seems to do the trick.
Hi @Brecht Van Lommel (brecht) . I'm still seeing an issue with that link you sent.
Jun 21 2017
Why should it be creating it own? We use the native nodetree for various reasons:
I can buy Brecht's argument. There is however something to be said for keeping to the original paper for compatibility with other renderers that implement it, and wanting to keep the settings the same.
Jun 20 2017
@Brecht Van Lommel (brecht) Isn't compatibility with other renderers THE reason for leaving it as it now? I.e, many other renderers have a Disney/principled shader, so if you want to match look you have to do a 1 - n to on this one setting.
Dec 21 2016
Nov 16 2016
Ok sorry for the duplicate, I couldn't find another report of this. The one thing I will say is that releases from github that have a version tag on them will automatically get a "." in them, which is why this came up. I changed the release to delimit with _ in the tag.
Error is <!> event has invalid window.