I haven't uploaded it anywhere, but the video (3:50 onward) should cover all the nodes/settings required to get things to work. If you're having any issues, just give me a shout!
you did not show the first node, with the cogwheel. Maybe that's why my installation doesn't work. I just put in first node null and user data with cog speed link with output in range mapper. The time node is empty.
Is there a timestamp in the video which covers the part you're having issues with? What results are you getting at the moment? I'm not sure if it helps or not, but here's a summary of the bits which may be of relevance: - With the 'Cogwheel' node (Cogwheel spline; child of Extrude), I'm using the 'Teeth' parameter to drive the second 'Input' in the Math:Divide node. - With the 'Cogs' node (parent null), I'm using custom userdata to output a percentage (Cog Speed). This is fed into the 'Output Upper' in the first range mapper. - The time node should yield a value of 1 for every second of playback. This is fed into the 'Input' in the first range mapper. I apologise if this hasn't helped, but I'll try... it's just that I'm struggling a bit with what you've said
@@JTC4D Thank you so much for your answer and for trying to help. I think there is an error somewhere in the initial stage. The cog does not rotate, nothing happens in the node of time. But I repeated everything as in your tutorial. If you get a chance to look, maybe you can see where I made a mistake. drive.google.com/file/d/1OUfrmnOr7nOeBzVfaw9OYKIjLjQUFRLB/view?usp=sharing
@@pavelp.5398 I'd advise trying the following test, then let me know where things begin to break: 1. Create a Cube. 2. Place an Xpresso tag on the Cube. 3. In the Xpresso tag, create a 'Time' node and 'Range Mapper' node. 4. Plug the 'Time' node's output into the 'Range Mapper' node's 'Input'. 5. Plug the 'Range Mapper' output into the Cube's 'Rotation.H'. This should cause the Cube to spin. 6. Create a Null. 7. Add Userdata to the Null (using the default data settings). 8. Drag the Null into the Cube's Xpresso window. 9. Plug the Null node's 'User Data' output into the 'Range Mapper' node's 'Output Upper'. Now if you change the Null's userdata value, the Cube should spin at a different speed. NOTE: if the userdata is set at 0%, the Cube won't spin. 100% will be regular speed, 200% will be double speed, etc Let me know if you're having any issues with any of the steps above. If this works, then it should just be a case of replacing the Cube with a Cogwheel, and continuing with the remaining steps in the video!
@@JTC4D Thank you so much, everything works now, with your help! At first it didn't work after the 5th step. Then I tried to open the project in version 2023 and everything works there. In my version r23 the cube also did not rotate.
@@pavelp.5398 No worries at all, glad to help! I didn't expect the 'Time' node to differ between version 2023 and r23, so I'll have to look into that - thanks for mentioning!
Cool little trick JT. Thanks again for sharing.
No problem at all, thanks for watching!
Thank you sir. This channel will blow up in no time with such high quality tutorials.
Cheers, much appreciated (and I hope so)!
Very interesting! Do you share the expresso function by any chance?
I haven't uploaded it anywhere, but the video (3:50 onward) should cover all the nodes/settings required to get things to work. If you're having any issues, just give me a shout!
you did not show the first node, with the cogwheel. Maybe that's why my installation doesn't work. I just put in first node null and user data with cog speed link with output in range mapper. The time node is empty.
Is there a timestamp in the video which covers the part you're having issues with? What results are you getting at the moment?
I'm not sure if it helps or not, but here's a summary of the bits which may be of relevance:
- With the 'Cogwheel' node (Cogwheel spline; child of Extrude), I'm using the 'Teeth' parameter to drive the second 'Input' in the Math:Divide node.
- With the 'Cogs' node (parent null), I'm using custom userdata to output a percentage (Cog Speed). This is fed into the 'Output Upper' in the first range mapper.
- The time node should yield a value of 1 for every second of playback. This is fed into the 'Input' in the first range mapper.
I apologise if this hasn't helped, but I'll try... it's just that I'm struggling a bit with what you've said
@@JTC4D Thank you so much for your answer and for trying to help. I think there is an error somewhere in the initial stage.
The cog does not rotate, nothing happens in the node of time.
But I repeated everything as in your tutorial.
If you get a chance to look, maybe you can see where I made a mistake.
drive.google.com/file/d/1OUfrmnOr7nOeBzVfaw9OYKIjLjQUFRLB/view?usp=sharing
@@pavelp.5398 I'd advise trying the following test, then let me know where things begin to break:
1. Create a Cube.
2. Place an Xpresso tag on the Cube.
3. In the Xpresso tag, create a 'Time' node and 'Range Mapper' node.
4. Plug the 'Time' node's output into the 'Range Mapper' node's 'Input'.
5. Plug the 'Range Mapper' output into the Cube's 'Rotation.H'.
This should cause the Cube to spin.
6. Create a Null.
7. Add Userdata to the Null (using the default data settings).
8. Drag the Null into the Cube's Xpresso window.
9. Plug the Null node's 'User Data' output into the 'Range Mapper' node's 'Output Upper'.
Now if you change the Null's userdata value, the Cube should spin at a different speed.
NOTE: if the userdata is set at 0%, the Cube won't spin. 100% will be regular speed, 200% will be double speed, etc
Let me know if you're having any issues with any of the steps above. If this works, then it should just be a case of replacing the Cube with a Cogwheel, and continuing with the remaining steps in the video!
@@JTC4D Thank you so much, everything works now, with your help!
At first it didn't work after the 5th step. Then I tried to open the project in version 2023 and everything works there. In my version r23 the cube also did not rotate.
@@pavelp.5398 No worries at all, glad to help! I didn't expect the 'Time' node to differ between version 2023 and r23, so I'll have to look into that - thanks for mentioning!