OTOY Forums

I am short on time, but have encountered crashing when accidently typing a value of "0" into the field located at:

Node Editor> Transform Node > UVW Transform > S.Y (Setting this to "0" causes a crash).

Please see signature for system details and feel free to let me know if more info is needed.

there's some requirements for bug reports. Please read these before posting. It avoids to ask same questions several times. And try to think as a 3rd people who develop software. How can estimate the case with an information like that?

Hi Aoktar,

No problem. Hopefully this helps.

Win 10 Pro 64Bit
4X Geforce GTX 1070 Hybrid FTW > Nvidia Driver 21.21.13.7595
2X Xeon V4 10 Core
64GB
1600W PSU
Octane Standalone 3.05.2
Octane Plugin 3.05.1
C4D R18.028 |Build RB177006

Basically, when a value of zero is entered into the transform node's S.X attribute, I get a consistent crash. This is when using an ImageTexture node with a Displacement node.

Steps:

Setup basic environment
Make cube
Make editable
Apply texture
Create Poly Selection
Apply second texture to selection
Setup Displacement and imageTexture nodes
Setup transform node, set S.X value to "0"
Crash

I've also taken the time to attach a screenshot and the scene file.

Thanks for taking a look!

Thanks for very good information. That's what i need as always. Here as you can see it's not about transform node. It's about being under displacement. It crashes in standalone too. I'll report it to Octane developers. thnx

You bet, and good point about it needing to be under a Displacement node. I've updated the post title for logging/clarification purposes.

Thanks for passing that on, Aoktar!

Hi, we are currently investigating this crash, thanks for reporting it.

The issue is caused due to an incorrect handling of scaling with zero values generating some numerical issues.

What would be the behavior you would expect in this case?

Hi Mojave,

No problem and thanks for looking into it.

That makes sense about the math issue. The UX issue is that users are allowed to input a problematic value.

A few options off the top of my head would be:

A: Set a floor for the values within the input field so that they can't go below a number that your team finds reasonable. For instance, if I type in "0", the field sets itself to something like 0.00001.
B: Notify the user that the value must be larger than 0 through some type of message.
C: Try to handle the numerical problem under the hood.

If "C" isn't possible, I'd prefer something like "A" over "B" as it's less obtrusive.

I've been a UI designer for 16 years, so if you'd like any additional ideas on that side, feel free to give a shout. Unfortunately, I have to run at the moment but can check back later.

Thanks again - cheers!

Thanks for your feedback.

Jaydekay wrote: A: Set a floor for the values within the input field so that they can't go below a number that your team finds reasonable. For instance, if I type in "0", the field sets itself to something like 0.00001.

Octane Standalone already has a floor value but can be overridden by the user, so the case should be handled anyway, also if such value is provided by any plugin.

Jaydekay wrote: C: Try to handle the numerical problem under the hood..

This will probably be the desired behaviour by most users. We'll release a new version of Octane with this and other bugfixes this week, so you can expect a new version of the plugin after that happens.

Thanks for helping improving Octane!

Sounds great, and happy to help!

Cheers -