So, when loading a tox into the EngineCOMP and setting “Start on Init” to false, it loads the custom-params but also seems to break the link between the engine and the custom-pars on the engineCOMP as changes to the custom-pars do net get received in the instanced process.
When starting on init this problems does not consist!
Yikes, not sure how we missed that. Sorry - fixed in the next update.