At 2:00 you use the graphs to multiply the values, could you explain how and why that works the way it does, and if there is another way to achieve a similar result? I'm just not understanding the concept behind using the graphs the way they are being used and how it creates that result. Thank-you!
Hi Daniel! Great tutorials. I need a clarification at 20:42, I get an error when I plug "Divide Curve" into "Cull Index". It shows me "1. Data conversion failed from Number to Curve". Kindly advise. Thank you!
Great tutorials, I learned a lot. I could only ask to explain in greater depth on why and how you get to some of the solutions, as I feel that without proper logic explanation, it will be somewhat hard for anyone, transitioning from intermediate to advanced level in GH, to understand why you are doing what you are doing (from personal experience of teaching GH to my friends).
Hey Tim! That's an interesting critique you're making there, do you think you could elaborate on that a little? For the most part I try to be reasonably thorough in my tutorials, but at the same time I'm sure you can appreciate that it takes a while to get to higher levels of understanding in grasshopper - and it becomes a lot harder to give purely intuitive explanations of the subject matter. I'm always open to criticisms, so is there anything more specific you think I could address/that I'm not doing in these tutorials?
Hi, Daniel and thank you for noting. So, when I do your tutorials, in some parts I have a hard time understanding right away the logic behind of what you are doing. Usually, I just pause and scrutinize the steps you did with param viewer, panel or point order components, you know, the usual stuff that, as I believe, experienced GH users do a lot. When I was teaching GH to my friend I noticed that she never did that and if she had a problem understanding the logic behind something, I had to literally explain each step with a mess of param viewers and point orders, sometimes drawing arrows explaining what goes where and why (and she still had hard time grasping it XD). So I think, although your tutorials are great for someone who understands how GH works and can explain your logic behind the scenes to him/herself, I still think new users will find it daunting and somewhat discouraging, because they don't know that before we come to the finished algorithm, we too have to sit there, sometimes for hours, scrutinizing the tricky parts of the logic. I'm going to rewatch this tutorial once again and pick one tricky (from my point of view) moment where I felt like I could use a deeper explanation and bring it up here and try to explain why it knocked me off balance and how I explained it to myself. Maybe it can help new users a lot or maybe I'm just dumb XD
Ahh, I see... Naturally, I try to encourage using panels and param viewers to inspect the data a lot throughout my tutorials, and I suppose I'm riding on the assumption that by this point users would understand to a greater degree how we are using them to debug and workout the next part of the definition. I believe I tried to steadily build this logic leading up to these advanced tutorials, but I might go back and look at some of my earlier material to see if this is also the case. Of course at the same time, some of these definitions have taken several hours to work-out, so trying to fit all that thought process into a ~30 min tutorial can be a bit of work. Chances are the problem is not unique to you, so anyway to improve the content is always beneficial.
Yeah, I understand that your goal it to make easy to digest, compact tutorials and trying not to bore us to death at the same time, which I believe you do nicely (not the death part). I only worry that some users will wonder, how did you come up with these numbers at 10:50 and why are you so certain that we need these numbers and stuff like that. Maybe I'm worrying too much, I haven't watched much from beginner and intermediate tutorials, to be honest. Maybe get a quiet mouse? XD Just kidding man, I saw some complain about it, I'm ok with that.
Oh yeah, fair enough. I covered the relative item component in an earlier tutorial in a fair bit more detail, maybe I'll add a pingback to that part of the tutorial. Hahahaha! Cheers for that! There was on person that was particularly salty about that a while back...
![ละลาย (LALALYE) - DAOU PITTAYA ต้าห์อู๋ พิทยา [OFFICIAL MV]](http://i.ytimg.com/vi/wo6r9TgausI/mqdefault.jpg)
Another excellent tutorial mate. Thanks again. You're great at teaching the deeper reasons behind the logic at each step.
At 2:00 you use the graphs to multiply the values, could you explain how and why that works the way it does, and if there is another way to achieve a similar result? I'm just not understanding the concept behind using the graphs the way they are being used and how it creates that result. Thank-you!
Hi Daniel! Great tutorials.
I need a clarification at 20:42, I get an error when I plug "Divide Curve" into "Cull Index". It shows me "1. Data conversion failed from Number to Curve".
Kindly advise.
Thank you!
Great tutorials, I learned a lot. I could only ask to explain in greater depth on why and how you get to some of the solutions, as I feel that without proper logic explanation, it will be somewhat hard for anyone, transitioning from intermediate to advanced level in GH, to understand why you are doing what you are doing (from personal experience of teaching GH to my friends).
Hey Tim! That's an interesting critique you're making there, do you think you could elaborate on that a little? For the most part I try to be reasonably thorough in my tutorials, but at the same time I'm sure you can appreciate that it takes a while to get to higher levels of understanding in grasshopper - and it becomes a lot harder to give purely intuitive explanations of the subject matter. I'm always open to criticisms, so is there anything more specific you think I could address/that I'm not doing in these tutorials?
Hi, Daniel and thank you for noting.
So, when I do your tutorials, in some parts I have a hard time understanding right away the logic behind of what you are doing. Usually, I just pause and scrutinize the steps you did with param viewer, panel or point order components, you know, the usual stuff that, as I believe, experienced GH users do a lot. When I was teaching GH to my friend I noticed that she never did that and if she had a problem understanding the logic behind something, I had to literally explain each step with a mess of param viewers and point orders, sometimes drawing arrows explaining what goes where and why (and she still had hard time grasping it XD). So I think, although your tutorials are great for someone who understands how GH works and can explain your logic behind the scenes to him/herself, I still think new users will find it daunting and somewhat discouraging, because they don't know that before we come to the finished algorithm, we too have to sit there, sometimes for hours, scrutinizing the tricky parts of the logic.
I'm going to rewatch this tutorial once again and pick one tricky (from my point of view) moment where I felt like I could use a deeper explanation and bring it up here and try to explain why it knocked me off balance and how I explained it to myself.
Maybe it can help new users a lot or maybe I'm just dumb XD
Ahh, I see... Naturally, I try to encourage using panels and param viewers to inspect the data a lot throughout my tutorials, and I suppose I'm riding on the assumption that by this point users would understand to a greater degree how we are using them to debug and workout the next part of the definition. I believe I tried to steadily build this logic leading up to these advanced tutorials, but I might go back and look at some of my earlier material to see if this is also the case. Of course at the same time, some of these definitions have taken several hours to work-out, so trying to fit all that thought process into a ~30 min tutorial can be a bit of work.
Chances are the problem is not unique to you, so anyway to improve the content is always beneficial.
Yeah, I understand that your goal it to make easy to digest, compact tutorials and trying not to bore us to death at the same time, which I believe you do nicely (not the death part). I only worry that some users will wonder, how did you come up with these numbers at 10:50 and why are you so certain that we need these numbers and stuff like that. Maybe I'm worrying too much, I haven't watched much from beginner and intermediate tutorials, to be honest.
Maybe get a quiet mouse? XD Just kidding man, I saw some complain about it, I'm ok with that.
Oh yeah, fair enough. I covered the relative item component in an earlier tutorial in a fair bit more detail, maybe I'll add a pingback to that part of the tutorial.
Hahahaha! Cheers for that! There was on person that was particularly salty about that a while back...
I can not see the expresion from range, could you tell me which is that expresision? Please
+Paula at what timecode are you referring to?
the expression from "range" before use "point cylindrical"
Paula I'm sorry but once again, at what specific time in the video are you referring to?
If I had a nickel for every click, I'd have a whole bunch of nickels.
+Ray Fletcher thanks man. A lot of people get annoyed about my incessant clicking.. I'll work on it for future tutorials.
@@DanielChristev Buy one of those silent click mouses lol! I got one off of amazon that is really quiet, you hardly notice the clicking.