Idea for Sketchy Physics enhancement
-
Hello, everybody
I previously posted this in the Plugin Forum, may be this forum is more aimed.
I just send an idea. As far as Sketchy-physic is involved in animation. Could it be possible
to write some plug-in in order to simulate sensor or end-switches?
This would allow to build sequential movements. I mean the block B for instance may move after the block A reached a kown position.... (in french we name that AUTOMATISMES ..)
We may program the positions or links on the same way we do, for joints and blocks.
(my Ruby Level is unfortunally very basic )
Pierre MALAISE
frendly yours -
I have been thinking about features along those lines and you will probably see something in a future version.
The biggest problem so far is how to "program" the sensors. I mean that when a sensor is triggered how do you as the designer specify what should happen.
I was originaly thinking of allowing Ruby events. But that turned out to be a big security hole. I am still pondering....
@malaise said:
Hello, everybody
I previously posted this in the Plugin Forum, may be this forum is more aimed.
I just send an idea. As far as Sketchy-physic is involved in animation. Could it be possible
to write some plug-in in order to simulate sensor or end-switches?
This would allow to build sequential movements. I mean the block B for instance may move after the block A reached a kown position.... (in french we name that AUTOMATISMES ..)
We may program the positions or links on the same way we do, for joints and blocks.
(my Ruby Level is unfortunally very basic )
Pierre MALAISE
frendly yours -
Thanks for the time you've taken reading my post, Cphillips.
Sensors and/or switches could be defined on such a way :
on hidden layer we put the path ( line or circle ) with active or non active segments
which lengths are given by the user. On the moving group, a small piece (index) is attached on the same way you do for hinges etc...
This index has 2 binary level depending on its position inside or outside the programmed segment
then according to its value( working as a binary latch ), a key could activate or stop an other task.
I easily realize this is pretty hard to program, mainly the relationship between sequential
eventsI appreciate once more time your answer
Thanks a lot
MALAISE -
I don't think I follow the segment bit.
But where the problem lies is in where you say "a key could activate or stop an other task". How does the user define a "task"?
Here is an example. I have a robot tank. When the tank "sees"(sensor) another tank I want him to:
-Stop moving the treads
-Calculate the bearing to the target
-Rotate the turret to that bearing
-Wait until turret rotation is finished.
-Create a new bullet object at the barrel of the gun
-Start the bullet moving at a given velocity.
-Resume moving.What does the UI that will allow a user to create that task look like?
-
Hello, Cphillips
You're right. I'm not thinking to such a complex task. I thought to some trigger
to initiate the next movement ( sequential ) whatever this movement involves one
or several groups.Let's see as example,in the present Ruby folder, ( Proper_animation..) the file, I've done
( passeur animé2.skp , you'll need also the plugin ).Friendly, and enjoy yours hollydays
MALAISEPasseur anime2.skp
Advertisement