I have polished up findings with custom components to share it here:
Optimized code generated with Maple’s codegen package cannot be used in the same way as it was possible with older versions of MapleSim’s Custom Component Template.
Intermediate variables `tx` (where x is an integer) of the optimized code are interpreted as physical parameters in the current template version and not as variables. This makes sense and is more consistent with MapleSim’s definition of variables and parameters, but leads to errors in MapleSim.
The attached model shows how optimized code can be generated for the current template and compares an older, still working (!) template with the new one.
The attached worksheet contains commands to programmatically generate optimized code for the current Custom Component Template.