No "Real" input for python node in Xpresso? (but it comes with Real inputs as default)
-
Hey guys, just using Xpresso for some calculations, and after fiddling around with a ton of nodes, I chucked it all out and am recreating it in Python for simplicity!
So among other inputs, I want 3 inputs of type "Real" to input mixed values to my script. This is where it gets weird:
- When I create a new Python node, it comes with two inputs, and both of these are "Real" inputs. Right click on them > port inspector > says they're "Real".
- However, when I click on the blue corner to create a new input, there is no "Real" type in the list??
so it comes with two as standard, but you can't duplicate them, copy them or create them. (But you can delete them). I need 3 real inputs... how do I fix this?
Steps to reproduce: create a null, add an Xpresso tag, open it in the Xpresso editor and add a Python node. Check the default inputs - both "Real". Then try and create a new input - be interested to know if it's standard for everyone not to have a Real input option. I'm running C4d Version 2025.3.3
-
Hi atomician,
Yes, that is not clearly set up. Use the Float entry to create a new Real input.
Example:
CV4_2025_drs_25_XPpn_01.c4d
For anything Python, I'm sure you have visited the Developer Forum already. (Please note: for security reasons, this forum is strictly code-free, and everything Python is on the specialized forum.)https://developers.maxon.net/?_gl=1jduutk_gcl_au*MTgxOTY2NjY5My4xNzU0NTg4NjU0
My best wishes
-
Thanks Dr. Sassi. The real inputs are just super useful for connecting any data type, whereas the float is fixed to be a float only - you can't link anything into it. I don't use the dev forum a lot - will have a look though.
Is this a bug do you think? wasn't sure whether to report it to maxon but not sure if theres any reason that real inputs aren't included?
-
Hi atomician,
Float here is any single number (vs. Vector or Matrix). You can "pipe" in, even Boolean values. Think of it as a family name used in Cinema 4D for numbers. Internally, it is changed to a "real" float.
The User Data interface might provide a good hint at how it is used. Float the group name, units for the evaluation what the input is.
The term Float is used (for example) for image formats, like the industry standard OpenEXR, whereby the numbers used here are exponential numbers, but also with such formats, no image or compositing app to my knowledge requires placing exponential formatting into the parameter fields to even change a single pixel.
The input in Cinema 4D is anything when set to float, single parameter for Real, or three for Vector, or 12 for Matrix. Each time it accepts Real, integer, or even other number-based data (Again, Boolean, 0 or 1 for false or true). So, I can't even see remotely a limitation here.
Example:
CV4_2025_drs_25_XPpn_02.c4dHere is the manual: Float is not listed, just real
https://help.maxon.net/c4d/2025/en-us/Default.htm#html/5829.html?TocPath=XPresso%257CXPresso%2520Editor%257C_____0You can report anything you like to Maxon, but you are the first in a few decades you ask me that. I do not see that this would trigger a change through the application; all documentation and the change would require recording all tutorials that newly use this term in the way it was used. Changing it now might be a very confusing change, given the tens of thousands of YouTube tutorials that might have it somewhere. I consider this an app-wide agreed understanding since the '90s. Yes, float as a term might be misleading, but when you set up a variable in Python, the first value provided defines the Variable, no labels needed.
All the best
-
Thanks Dr. Sassi, that makes loads more sense now. I was thinking of it like a float in javascript, where it can literally only allow a floating point number. I can see now that float inputs can accept all different inputs - thanks for the clarification!
-
Thank you for your input and reply, atomician.
Enjoy your project.My best wishes