Found 10 posts.
Search results Show results as topic list.
Technical Discussion » How to find currently selected tab in multiparm folder?
- UtilitasArts
- 10 posts
- Offline
I wanted to see if I could have a tab be forced on the user. But I think you inspired me to go for a workaround!
Technical Discussion » How to find currently selected tab in multiparm folder?
- UtilitasArts
- 10 posts
- Offline
Rigging » APEX Curve Solver?
- UtilitasArts
- 10 posts
- Offline
My issue with the rig::SplintInterpolateTransform is that the matrices flip for certain angles. and it's difficult to control this behaviour. this is something I tried to solve for my own rig. Here I have a video that shows the issue.
Rigging » APEX Curve Solver?
- UtilitasArts
- 10 posts
- Offline
A little Bezier-rig based on kodra's suggestion.
I currently build this completely using one vex node (inside the apex graph).
I know it was mentioned before that vex would slow down the rigs. Currently this still updates with 120 fps. what is the best way to test my rig's performance? do rigs get more expensive as frames are added?
I currently build this completely using one vex node (inside the apex graph).
I know it was mentioned before that vex would slow down the rigs. Currently this still updates with 120 fps. what is the best way to test my rig's performance? do rigs get more expensive as frames are added?
Edited by UtilitasArts - Feb. 7, 2024 12:09:31
Rigging » Apex rig IK setup with 5 joints and limiting rotation
- UtilitasArts
- 10 posts
- Offline
Here I have a file that locks a matrix from rotating further than specified rotation angles.
Rigging » Apex rig IK setup with 5 joints and limiting rotation
- UtilitasArts
- 10 posts
- Offline
I build a digitigrade IK leg yesterday (posted it on the discord server).
perhaps you can take a look at it to get some inspiration.
I'm pretty confident the same could be done to for more joints.
I am not sure yet how to do the limiting rotation part. I will take a look into limiting rotations today.
perhaps you can take a look at it to get some inspiration.
I'm pretty confident the same could be done to for more joints.
I am not sure yet how to do the limiting rotation part. I will take a look into limiting rotations today.
Edited by UtilitasArts - Feb. 3, 2024 04:13:19
Rigging » APEX look at
- UtilitasArts
- 10 posts
- Offline
I took another look at it "no pun intended".
And I believe the last matrix is a point in space that is used to determine the "look-up".
I've got results when modifying the "translate" aspect of the matrix upwards.
I'm not sure if this is correct as I don't know why the look-up vector requires X Y and Z vectors.
And I believe the last matrix is a point in space that is used to determine the "look-up".
I've got results when modifying the "translate" aspect of the matrix upwards.
I'm not sure if this is correct as I don't know why the look-up vector requires X Y and Z vectors.
Rigging » APEX look at
- UtilitasArts
- 10 posts
- Offline
you can do pretty much anything you'd want with apex in it's current stage.
Apex is literally just a bunch of different houdini-contexts thrown together into a system that allows for functions to be fired through attributes. Quite amazing.
I personally was not able to get the Look-at working, because I did not understand the 3 matrix inputs it required and I dislike finding anything in the currently existing rigs. I'm more used to a 3 vector input look-at constraint. There is probably a good reason for it requiring matrices.
But you are always able to create your own look-at if you'd want. here is an example I quickly build using vector inputs.
Apex is literally just a bunch of different houdini-contexts thrown together into a system that allows for functions to be fired through attributes. Quite amazing.
I personally was not able to get the Look-at working, because I did not understand the 3 matrix inputs it required and I dislike finding anything in the currently existing rigs. I'm more used to a 3 vector input look-at constraint. There is probably a good reason for it requiring matrices.
But you are always able to create your own look-at if you'd want. here is an example I quickly build using vector inputs.
Rigging » Multi Parent Constraint + Hybrid Spine IK
- UtilitasArts
- 10 posts
- Offline
seeing that we can run vex in the apex graph makes me quite exciting.
should running vex inside apex still be considered optimal, performance wise? or should we notice slowdowns when using it compared to pre-existing nodes?
I have done quite a bit of rigging with kinefx in the meantime. it would be nice if I can convert my previous rig-logic work to apex rigs.
should running vex inside apex still be considered optimal, performance wise? or should we notice slowdowns when using it compared to pre-existing nodes?
I have done quite a bit of rigging with kinefx in the meantime. it would be nice if I can convert my previous rig-logic work to apex rigs.
Edited by UtilitasArts - Jan. 30, 2024 14:33:11
Technical Discussion » The "pivot" in cracktransform() and matrix?
- UtilitasArts
- 10 posts
- Offline
Hey there,
Allright, here we go.
the pivot inside the functions cracktransform and maketransform are actually more or less a function themselves.
For example in the function maketransform:
The pivot is applied like this:
Inside of a point attribute wrangle paste this code:
vector T = chv("T");
vector R = chv("R");
vector S = chv("S");
vector pivot = chv("P");
matrix m = maketransform(0,0,T,R,S);
matrix m2 = ident();
translate(m2,-pivot);
m2 *= m;
translate(m2,+pivot);
v@P *= m2;
if you create wrangle and apply this wrangle to a cube, you will start to understand it.
As you can see I did not use the "pivot" inside the maketransform function, I just recreated what it does behind the scenes.
The pivot is something that "alters" the actually stored transform.
In the function cracktransform it does the opposite of this. therefore it changes the rotationpoint of the matrix before extracting the data out of it.
Allright, here we go.
the pivot inside the functions cracktransform and maketransform are actually more or less a function themselves.
For example in the function maketransform:
The pivot is applied like this:
Inside of a point attribute wrangle paste this code:
vector T = chv("T");
vector R = chv("R");
vector S = chv("S");
vector pivot = chv("P");
matrix m = maketransform(0,0,T,R,S);
matrix m2 = ident();
translate(m2,-pivot);
m2 *= m;
translate(m2,+pivot);
v@P *= m2;
if you create wrangle and apply this wrangle to a cube, you will start to understand it.
As you can see I did not use the "pivot" inside the maketransform function, I just recreated what it does behind the scenes.
The pivot is something that "alters" the actually stored transform.
In the function cracktransform it does the opposite of this. therefore it changes the rotationpoint of the matrix before extracting the data out of it.
-
- Quick Links