Hi giogos.ele,
It is always easier to use an attach scene file (reduced to the items which are connected to the problem) than a screen shot. Thanks for considering.
The screen shot is not really helping as it takes all interactivity out. What I see is that you have placed the MoInstances on the top, which should work, but is not a suggested practice. The information flow in its simplest form goes from top to bottom. Normally it works anyway, but each step that is not calculated, will most-likely take older information, and the scene looks wrong. Check out the tutorials from Kai Pedersen about “Priority”. It is a core knowledge for C4D.
Besides that, the Editing screen is optimized to allow you to work without pressing constantly the “A” key [refresh]. Even the time isn’t progressing the scene becomes updated. Which allows for results that aren’t possible from the information flow—in terms of priority—as it refreshes often. This is a typical problem, to take the editor view as proof of concept. The Picture Viewer, calculates one time through, then renders, What is not available in this flow at the right position will be replaced with what is there, typically old or none information. If you scrub in the timeline, the Editor view might provide you with something, but the Picture viewer misses information.
Similar to this, the MoInstance needs the frames before to calculate, or you have to provide the information. How to do that? Use on the MoInstance an Object Manager>Tags>MoGraph Tags>MoGraph Cache. Then click on the new Cache Tag and in the Attribute Manager go to Tag [tab] and press the Bake button. Now try agin to render. It should be all there.
If not, provide a scene file, Then we can take a look.
All the best
Sassi