- User Since
- Mar 2 2019, 7:01 AM (19 w, 3 d)
Fri, Jul 12
Tue, Jul 9
Sat, Jun 22
Thu, Jun 20
Apologies for the inactivity. I've been dealing with classes. Once 2.80 releases I'll make sure to get the backwards compatibility finished and address any remaining issues so it can make it into 2.81.
Jun 1 2019
May 31 2019
May 30 2019
May 29 2019
After some troubleshooting I just did a fresh installation of the blender source and applied the patches.
(will become a part of D4971)
oops accidentally replaced the entire diff. (I don't know how to use git, sorry let me figure this out.)
Fixed hard-coded socket indices.
Edit: cycles socket for emission_strength default value has been updated to 1.0. (doesn't actually seem to have an effect but doing it just to be safe)
May 15 2019
May 14 2019
May 13 2019
May 6 2019
Sure thing! Just hit play.
May 4 2019
Apr 18 2019
Apr 15 2019
Looks Awesome! Is there any room for tweaking the light intensity? Sometimes when working with real world light units and tweaking the exposure in the render settings to componsate the material preview gets really dark.
Apr 5 2019
Mar 30 2019
Mar 29 2019
Mar 24 2019
Again, apologies about tagging everyone I'm new to this and still learning.
Mar 23 2019
Apologies, I'm new to this.
After a long search through the code I think I've come across the easiest solution.
The diff file can be found here if anyone can approve it, thanks: https://developer.blender.org/D4581
I'd vote to override the defaults for text since it seems like the better short term solution. It should keep the best of both worlds (full curves and full text). Its just curious that blender has this discrepancy in the meaning behind those flags in 2D and 3D, I'm pretty sure that decision was made long ago and might be worth looking into cleaning up that inconsistency in a future task. For now since I was the one who authored the original change I'm going to try to fix this one by overriding the defaults for text objects and I'll post the diff if that's okay.
Mar 22 2019
Mar 13 2019
I split the properties between edit and object mode using a custom interface.
Thanks for the response. Good to see the curve default changes are pretty much ready to go. Feel free to commit those.
Mar 2 2019
It seems the issue stems from the fact that Curves are added as primitives which can be created in both object and edit mode. So a fix to this might require some unwieldy code duplication.
Unless someone can suggest a potential fix or is okay with this bit of UI inconsistency. I'm thinking of leaving out the extension to the add curve menu and make my only change a default to full fill mode/bevel resolution.
I've been made aware that the extra add curve options only make sense in the context of object mode (creating a new curve).