- User Since
- Aug 16 2019, 5:37 PM (27 w, 6 d)
Thu, Feb 6
Wed, Feb 5
Tue, Feb 4
Mon, Feb 3
Sat, Feb 1
Jan 14 2020
Dec 27 2019
Dec 15 2019
Dec 13 2019
Dec 12 2019
Cheers Reiner -- I only pinged you because I thought you might enjoy knowing that your code made it into Blender, even if a few years has passed since you proposed it for inclusion in the first place. =)
Dec 11 2019
Would you guys be ok with PDT absorbing this functionality in a button in the PDT View panel? It's quite useful and I don't think it was ever brought up to 2.80 standards?
Dec 9 2019
Dec 3 2019
Thank you very much for your patience and input during the review phase.
Dec 2 2019
We believe that we have fixed all the review nits you have mentioned, including suggestions. We've done our best to reference the relevant review nits in the commit logs.
Thanks. I'm afraid that I accidentally mistyped 'import' and wrote 'input' instead, so it was really two questions -- the first of which was intended to be:
Nov 18 2019
I'm guessing you're quite busy so this is just meant as a heads up that we feel that the v1.1.5 code is ready for serious review as we don't expect any more significant churn in the v1.1.x branch.
Nov 13 2019
Oct 29 2019
Another solution could be to add a print() statement like in the if clause above? This wouldn't change the exception propagated to the user, but it'd still offer some more context?
Oct 28 2019
Oct 15 2019
We would like to prepare a manual for PDT. Should we be using the official Blender wiki or ...?
Oct 8 2019
For maintainability's sake, we've gone with Google-style docstrings for now.
Sep 28 2019
Aug 19 2019
Just a quick note that @Maurice Raybaud (mauriceraybaud) (the povray plugin maintainer) has gotten in touch with me and stated that, while the povray plugin doesn't currently work with 2.80, he and his team are working on getting it functional again.
Aug 16 2019
The povray add-on included in 2.80 isn't working for me when trying to render the BMW27 demo with povray -- I'm also dropped to a checkerboard background: