Hi jhpark, thanks for reaching out us.
Aside from the notes left by @blastframe - thanks dude for the remarks - I think it's worthy, thinking of a more generic scene, to mention the need BaseDocument::ExecutePasses() to be sure that everything is actually evaluated before querying the scene rather than the EventAdd() which serves a different scope.
This function is responsible to execute the scene evaluation and, consequently to be sure that, moving from a frame to another, all the items in the scene reflect the changes imposed by the frame switch.
The approach used by @blastframe actually operates on CTracks and key but, although this approach works fine for your specific case, when more evaluation dependencies are created in the scene you could easily end up in unexpected results.
The code could then look like
frames_count = 10 # [Set] frames counter
for f in range(0, frames_count):
doc.SetTime(c4d.BaseTime(f, doc.GetFps()))
# evaluate the scene
doc.ExecutePasses(None, True, True, True, c4d.BUILDFLAGS_NONE)
obj = doc.SearchObject('Cube')
# get object position
x = int(obj.GetMg().off.x)
y = int(obj.GetMg().off.y)
z = int(obj.GetMg().off.z)
# get object color
r = int(obj[c4d.ID_BASEOBJECT_COLOR].x * 255)
g = int(obj[c4d.ID_BASEOBJECT_COLOR].y * 255)
b = int(obj[c4d.ID_BASEOBJECT_COLOR].z * 255)
print("Frame = " + str(f) + ", (X,Y,Z) = " + str(x) + "," + str(y) + "," + str(z) + ", RGB = " + str(r) + "," + str(g) + "," + str(b))
