- User Since
- Nov 16 2016, 1:34 AM (152 w, 6 d)
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.