favorite
Development Fund
Support Blender Core Development with a monthly contribution.
theaters
Blender Studio
The creators who share. Access production content and knowledge from the Open Movies.
code
Blender Developer Blog
Latest news and updates on Blender development.
people
Get Involved
Join the community and help with design, development, docs and more.
bar_chart
Open Data
A platform to collect and display the Blender Benchmark results.
menu_book
Blender Docs
Documentation on Blender's features, tools and API.
Blender Conference
The yearly event that brings together the Blender community in one place.
download
Get Blender
Download the latest Blender version, or try the beta!
4 Comments
Join to comment publicly.
Jim Conrad
30th June 2022 - 01:32
This one video helped demystify attributes more than any other I've seen so far. The fact that the Geometry Nodes development swung wildly back and forth between workflows didn't help, but glad to see that a sensible middle ground was found. Love this series! Thank you, Simon!
mark mi
28th July 2022 - 11:07
Hello teacher, I want to ask about the difference between value and float, these two definitions have been giving me a headache
Simon Thommes
28th July 2022 - 11:44
@mark mi Hey Mark, this is a bit of an unfortunate legacy naming. Float is a more accurate description of what the actual datatype is, while value is more loose. The reason why in previous node systems this didn't matter so much and it was simply called value was that Blender handles the datatypes on the backend while the user doesn't need to be concerned with the exact type. With geometry nodes the user is much closer to the actual data-structures and it matters a lot more. So there it is useful to differentiate.
mark mi
3rd August 2022 - 05:00
@西蒙·托姆斯 Thank you very much