Thanks again, Istvan. Good to know. It seems to be a similar problem as the frame export in MSP Replay in SUp 2017 using SUp 2016 models. The solution was to copy the content or to import the model into a new model.
BTW, thanks for your shape loader extension!

This are the bones and joints (jet not enough ... hands, head ...) and the result with Twilight renderer.

After tests with the late discovered Cenvexify (Fredo6 - Fredo Tools) here some problems with the relatively large torus segments with the usual MSP user interface settings.

Convexify_01.skp

What I did as a boy with my milk jug...
First tests for the animation of human gestures and movements. I hope that the robotic and jerky movements can still be turned off...

Have found a solution for the problem of SketchUp 2017 animation export of SketchUp 2016 MSPhysics models. Start SUp 2017 and import the SUp 2016 MSPhysics file with the .skp-import funktion. All scene data with layers, stiles, shadows etc. are lost, but the export of animations even of large models works. To open a SUp 2016 MSPhysics model directly and export the simulation from Replay brought the incomplete images. The underlying cause of the problem I could not find unfortunately...

Hi, Anton. Thank you very much. Again a great example of the particle effect and of a script to learn efficient programming. If we could do the smoke with emitters then there is a chance to render the simulation of the candle.

Thanks, Istvan. Now it works like desired. Much joints for a little candlelight...

Name: Spin It
By: sdmitch (http://sdmitch.blogspot.de/)
Usage: To rotate the view or objects for animation purposes.
works!

Another problem with a servo and a non-collision object. After the fall of the candle a strange behavior of the flame arises. Collision, gravitation, etc. do not seem to be completely canceled. The joint oscillates in high frequency, which can even lead to a crash. What can I do?

Noncollision-Test_02.skp

Makes a very professional impression. Congratulations to the fantastic result of the long work!

Thanks, Anton for the explanations.
The Indigo renderer update/halt time difference seems not to be a MSP or hardware problem. I've tested it with different model sizes on different machines. I'll try to ask this in the Indigo forum. In the SkIndigo Render Settings one can set the halt time a few seconds longer than the before tested update time and all is fine.

The incomplete results of the view.write_image function in SketchUp 2017 I will report in the SketchUp Community Forum.

I hope my problems with Servos I can demonstrate in the following examples more dramatically. A mode to hold connected objects in the pivot position would be fine.

The tests with the Update Rate I did only to improve that. No need to change the oscillator script. For non real time simulations (large models with much MSP-objects) the oscillators based on frames are better than based on world time. (on the end the film with 30 frames per second brings the "real time" feeling).

Servo-Test_06s.skp

OK, thank you.
Have tested MSPhysics "Export Replay to Images" with the new SketchUp Make 2017 M2 (windows 7) and got a similar result as with M1 (windows 10) as mentioned in an older question.
The example is a GIF of exported frames with an original resolution 1920x1080.

SketchyPhysics works only on 32 bit systems. No way to port it.
Please try MSPhysics by plugin author Anton S.
Search for MSPhysics under Board index - Plugins.

A little question regarding Export Replay to SkIndigo: The batch rendering doesn't save the frames complete rendered after the set Halt time but at the point of the last image update during the render process. This point can be minutes before the desired render time per frame. Is it an exporter question or should I ask in the Indigo forum?

Unfortunately, changing the Update Rate from 1 to 3 is not useful when camera, joints, emitter, etc. are based on scripts that use the OnUpdate function. Programmed objects become 3 times faster. The appearance of emitted objects no longer fits to the image rate. The weight of the emitted objects or the lifetime seems to change.
For the joints based on pivot points, an option independent of the Update Rate in the user interface seems to be useful for fixing at the pivot point. If this is possible...

Should make my question more precise:
The reason for the loose behaviour of the joints is the update rate in MSPhysics UI - Simulation - Update Rate = 1 (seems the best for my large model).
If I change this from 1 to 3, the servos remain more stable in the pivot but the spring no longer brings the steady up and down movement.
Have now tried to modify all settings at the Spring Joint, but do not get the desired result.
What can I do?
Thank you in advance, Anton!

Servo-Spring-Test

Interesting find. Helpful basics for MSPhysics animations...

Hi, Anton. Here I have yet an other question:
It would be great if, for example, there would be a mode for the servos to hold the joint exactly at the center of rotation and completely prevent the centrifugal forces and the pulling out of the components involved.
In the enclosed example, I have not found any way to keep the outer sections of the wings exactly at the center of rotation of the servos. There always develops a gap between the parts.
Have screwed at all settings and nothing was useful.
It seems to be a kind of inertia of the outer wing segments, which can not be stopped by reducing weight, gravitation, friction, etc.

Version 3.0.0 from SU EW has not the tools submenu 'Layer Manager'. This tool is completely deleted. V 3.0.0 has only the 'Layer Tools'.
But the 'Layer Manager' has useful tools like 'Save and Restore Layer Configuration' directly into the model file etc.

But my request for Version 2.2.0x is:
The function 'Create layer and control behaviour' in 'Layer Tools' brings problems in both versions.
To create a layer 'Visible in the current scene only' is very helpful if you have many scenes in which the new layer should be switched off.
The problem is that the tool not only makes the new layer invisible in all other scenes, it overwrites all scenes with the same layer configuration of the active scene. And there is no way back - no undo. All layer settings in all scenes are lost...

If that could be corrected, it would be fantastic. Thanks in advance!

Testing "export replay to images" in SketchUp 2017.
The result is incomplete images with always the same empty white parts..
The same happens when using the following line in a MSPhysics script:

Sketchup.active_model.active_view.write_image("e;/MSPh_Temp/frame_%06d.png" % frame,1600,900,true,1.0)

How should it be right for SUp 2017?