Hello,
please may I ask whether this is expected behavior?
opex_test.1.toe (3.9 KB)
It seems to me like a problem with opex(), but I am not sure, so I thought I might rather post it here. Tested in 2025.31550. Thanks.
Hello,
please may I ask whether this is expected behavior?
It seems to me like a problem with opex(), but I am not sure, so I thought I might rather post it here. Tested in 2025.31550. Thanks.
hanks for reporting this. Looks like currently you’d have to specify a start reference with self.ownerComp.opex('constant1') for this to work.
Logged it as a bug and we will have a look at it.
cheers
Markus
No problem, thanks for info. ![]()
This will be fixed in the next posted builds 2025.31630 and later. Thanks for the report.
Great, thanks for the fix.