Hi Andreas, thanks for the quick and helpful response and guidance.

For OMSimulator users it would certainly be nice if they could drag Modelica models from the tree browser and directly drop them as new subsystem in the composite model view without the manual export-to-fmu-then-load-from-filesystem steps, but as there is a feasible way, this might be kept low priority.

Therefore as you recommended I will keep using OMSimulator and the SSP editor and look forward to the bright future :-)

Best Regards, Thomas

Does this problem still persist?

I wrote a FMI 1.0 CS fmu in Golang which works fine with e.g. fmpy, but
when imported into OpenModelica (1.16, 1.18-nightly) "fmiSetReal" is never called (as observed above/before)

fmiDoStep and fmiGetReal and all other ".so" functions are called as expected.

Could the problem have started with the transition to C++ for the simulator?
I found that there is an empty function body for ::SetReal here:
  https://github.com/OpenModelica/OpenMod … .cpp#L1245

If there is a chance that only this little code is missing, I could try and provide a fix,
only if it is not, I would rather not spend the time to setup the build environment.

My FMUs also support FMI 2.0 CS and run well in OMSimulator, but working with SSP-Models seems a lot more uncomfortable,
especially because every bloc has to be exported to fmu, and there is no nice element browser...

Did you finally find a way to resolve this?
Could it be caused by this function having an empty body:
  https://github.com/OpenModelica/OpenMod … .cpp#L1245
??