dynamicMotionSolver plays catch up when started from a non-zero time step
Not sure if this is a bug or a limitation. But when using the dynamic mesh rotating solid body functionality in interDyMFoam, the dynamic mesh will play catch up if started from a non-zero time step. In other words, if I run a simulation for 0.5s without mesh motion (staticFvMesh), stop it, turn on mesh motion (dynamicMotionSolverFvMesh), and restart from the latestTime, the mesh will jump to the 0.5s position (as if it had already run for 0.5s) to begin the simulation rather than starting at the location where staticFvMesh left off. I did try different combinations of startTime and startFrom in the controlDict before the restart, but still couldn't get it to stop playing catch up.
I don't have a good quick test model for you yet, but the mixerVesselAMI tutorial I imagine could be modified to show this (even though it too takes a while to run).