Leaderboard

Hello @everyone, Yes, it is, but it is a bit clunky. While this is probably practically true, it is technically not. You can always spice up your Xpresso with Python, which also means you can do whatever you want to do. The question then is how "Xpresso-esque" the results are when 99% of the stuff happens inside a Python node. There is also the problem of Xpresso that it really dislikes linking classic API node types other than BaseObjects, i.e., objects, so that one must use the user data trick for linking other node types. The attached example has a null called "Xpresso" which has a user data field "Slot". With this Slot field we pass in some node into our Xpresso graph. In this case the track of an animation. Also passed in is the x-position of another null. The final result is then that one can select a key via its index. The frame time value of that key is then driven by the position x-component of that driving null. I.e., effectively, when the null is at (40, 0, 0) units, then the second key in that track will be at 40 frames in the example file. You could animate that null and the key frame value will follow. The result would be rather non-sensical, as that track animation would change over time, but it works ^^ How practical all that is, is up to you. It is certainly technically possible. But it makes much more sense to do such things right away as a Python Programming Tag IMHO. But opinions can differ here, and some people find such mixed setups useful. Cheers, Ferdinand xpresso_keyframes.c4d

@Cerberain the BIOS, TPM also goes under the names of PTT (platform trust technology) on Intel and fTPM on AMD Ryzen.