Ii think your language skills is a pretty steep barrier to understanding what I tried to say. Google translate is not probably the best possible tool to understand complex English. Especially since negation seems to loose meaning mostly in conversion to a lot of languages.
See its easier for us to understand you than for you to understand us. Because data form you to us gets corrupted 4 times whereas its gets corrupted 7 times. (you, your language, translation , me versus you, your language, translated, me, English, translation, you)
At what here rig if in mtor it works correctly?
Yes but mtor steps trough time. Stepping trough time is different.
If are correctly created playblast?
playblast steps trough time.
I consider as nonsense to adjust rig under renderer, rather the reverse
language barrier.
Im just telling you why querying node at different context may not always work. And why in practice there's very few exporters that do not refresh the actual global time. Even makers of maya rely on this rather than the context. (they provide a option not to update but they say it wont work in all cases)
See the context relies on the node graph to resolve all functions. So it can just easily change time context for all those nodes.
However there exist nodes, most notably expression node and some of the simulation nodes, that may under some circumstances change the nodes state outside the graph. Changing time context does not help you because it will not know how to trigger these actions because it does not see them. Manually changing time triggers these nodes in ways in which mdgcontext does not.
So your only real option is to do what you try not to do. Fortunately what you think it results in is not true.
It is a problem of work of functional set MFnDependencyNode.
Partially. Its a problem with maya usability design. Maya does not enforce that people use maya right it just advocates you to do so. When you open this door for this then you can not rely on methods that are different form normal use to work right, because they dont gets tested by the user.
But yes you can think of it as a problem with MFnDependencyNode. Tough factually it is not, as the problem is not within the realm of MFnDependencyNode. Its a superset problem.
If there is no answer - you mean it don't know. I will look forward to hearing that who knows.
Ive told tou the answer 2 times. (this is the 3rd time)
change time but dont notify the gui OR suspend gui temporarily. It all accomplishes same limited graph evaluation you need BUT it will trigger out of graph evaluation.
MDGContext to me it is necessary not to recalculate all scene
False assumption.
Even if you update time Maya does not recalculate the scene just what gets asked for. You can control that.
PS: i will try to make a scene that illustrates the point.