Hello,
In the first screenshot below if you place down a Path(utility) node first then followed by the two PathCV nodes, you get the line centred on the “crosshairs”. This is the desirable effect I want.
However, I've made a digital asset for a single PathCV which will have about 70 control parameters ( when I finish it ).
I was just testing some of those paramters and decided I would try connecting a path between them to play around.
In the second screen shot is what I get.
The path does not connect to the centre of the “crosshairs”.
And this is not because of my digital asset. I've tried just using plain PathCvs and get the same result.
I've checked all the parameters of both Path and PathCvs and they are the same. It just seems for some reason the order in which you create the Path will determine how they connect.
In my siutation that would render my digital asset useless as I won't be able to get rotation control from the centre of the “crosshairs”, which is what I need.
Any help on this is appreciated.
PathCV connections on Path
3084 6 1-
- BabaJ
- Member
- 2184 posts
- Joined: Sept. 2015
- Offline
-
- Enivob
- Member
- 2660 posts
- Joined: June 2008
- Offline
-
- BabaJ
- Member
- 2184 posts
- Joined: Sept. 2015
- Offline
Hi Enivob,
It seems that the order doesn't change the behaviour.
However, I've been playing around with it for a while now and the solution seems to be when selecting the objects for the path to go into the PathCV node and select the point node( the last one ) of the PathCV instead of just the PathCV.
It's a bit odd since the other way of doing it ( create path then pathcvs ) doesn't do it that way.
But as long as it works I guess I will go with this for the time being.
Thanks for the suggestion.
It seems that the order doesn't change the behaviour.
However, I've been playing around with it for a while now and the solution seems to be when selecting the objects for the path to go into the PathCV node and select the point node( the last one ) of the PathCV instead of just the PathCV.
It's a bit odd since the other way of doing it ( create path then pathcvs ) doesn't do it that way.
But as long as it works I guess I will go with this for the time being.
Thanks for the suggestion.
-
- BabaJ
- Member
- 2184 posts
- Joined: Sept. 2015
- Offline
I just wanted to post to clarify what is happening a bit, just for general info.
In both screenshots there are only two points being connected.
And yes the order doesn't change the behaviour.
Each single PathCv has 3 “crosshairs” one for each axis ( x,y,z ).
All three share the same centre point from which they can extend out depending on their scale parameter.
The odd behaviour that is seen in the second screenshot is that instead of the path line going from centre point to centre point it goes to one end of each of the “crosshairs” thereby by giving the twisted loops seen.
In both screenshots there are only two points being connected.
And yes the order doesn't change the behaviour.
Each single PathCv has 3 “crosshairs” one for each axis ( x,y,z ).
All three share the same centre point from which they can extend out depending on their scale parameter.
The odd behaviour that is seen in the second screenshot is that instead of the path line going from centre point to centre point it goes to one end of each of the “crosshairs” thereby by giving the twisted loops seen.
-
- edward
- Member
- 8161 posts
- Joined: July 2005
- Offline
-
- BabaJ
- Member
- 2184 posts
- Joined: Sept. 2015
- Offline
-
- BabaJ
- Member
- 2184 posts
- Joined: Sept. 2015
- Offline
-
- Quick Links
