I see that others are making turns with no problem.
But, I'm still stuck with this odd behavior.
I will try again in a few days.
Work stuff comes first.
I wish you can add some functions to the API to mimic the Move Steering Block ( which has angle / degrees of turn )
which was so easy to use in Lego IDE.
Thanks, LA Guy
njsokalski wrote 2014-02-20 at 14:28
I am not trying to prevent features from being added; and some features could obviously be more useful or have more included in them than I thought. However, I always viewed the purpose of using .NET (or some other full fledged language) rather than the
Lego programming interface for EV3 as being having the option and capability to do more complex calculations and be more efficient. One of these things would be steering, since there are multiple types of steering, and how they are used will vary for every
robot. Steering, in my opinion, is one of the things that is so simple it is easier to simply write your own function or sub for each robot. But don't get me wrong, because I will admit that when I first learned .NET that's what I thought about some classes
that I didn't know about or didn't know how to use, but now I am glad that I know them. To put it simply, steering has never been one of the hard parts for me (even though navigation has been a significant function of my robots), but everybody finds different
parts harder than others, and I would be happy to share my basic steering algorithms with anybody who would like to see them.
This issue was imported from CodePlex
peekb wrote 2014-02-19 at 13:05 @peekb,
Thanks for testing.
I see that others are making turns with no problem.
But, I'm still stuck with this odd behavior.
I will try again in a few days.
Work stuff comes first.
I wish you can add some functions to the API to mimic the Move Steering Block ( which has angle / degrees of turn )
which was so easy to use in Lego IDE.
Thanks, LA Guy
njsokalski wrote 2014-02-20 at 14:28 I am not trying to prevent features from being added; and some features could obviously be more useful or have more included in them than I thought. However, I always viewed the purpose of using .NET (or some other full fledged language) rather than the Lego programming interface for EV3 as being having the option and capability to do more complex calculations and be more efficient. One of these things would be steering, since there are multiple types of steering, and how they are used will vary for every robot. Steering, in my opinion, is one of the things that is so simple it is easier to simply write your own function or sub for each robot. But don't get me wrong, because I will admit that when I first learned .NET that's what I thought about some classes that I didn't know about or didn't know how to use, but now I am glad that I know them. To put it simply, steering has never been one of the hard parts for me (even though navigation has been a significant function of my robots), but everybody finds different parts harder than others, and I would be happy to share my basic steering algorithms with anybody who would like to see them.