I didn't see this problem immediately after opening a saved file for I soon clicked "mesh only" mode. The effect appeared normaly after a while with copying in new objects or animating, for instants changing to "smoothed" mode to adjust one object to another.
My experience with "exploding" views are a quite old effect in AoI. It happens normally with big files clicking another viewmode than "mesh only" not depending from how many RAM you offer. When you have offered enough RAM from the start on, clicking back from other viewmodes to "mesh only" brings everything back into the right position . But If there is to less RAM offered at start of AoI lost datas are beginning to mess up the file exactely when you're saving it.
My experience with "exploding" views are a quite old effect in AoI. It happens normally with big files clicking another viewmode than "mesh only" not depending from how many RAM you offer. When you have offered enough RAM from the start on, clicking back from other viewmodes to "mesh only" brings everything back into the right position . But If there is to less RAM offered at start of AoI lost datas are beginning to mess up the file even if you saved it.
My experience with "exploding" views are a quite old effect in AoI. It happens normally with big files clicking another viewmode than "mesh only" not depending from how many RAM you offer. When you have offered enough RAM from the start on, clicking back from other viewmodes to "mesh only" brings everithing back into the right position . But If there is to less RAM offered at start of AoI lost datas are beginning to mess up the file even if you saved it.
My experience with "exploding" views are a quite old effect in AoI. It happens normally with big files clicking another viewmode than "mesh only" not depending from how many RAM you offer. When you have offered enough RAM from the start on, clicking back from other viewmodes to "mesh only" brings everithing back into the right position . But If there is to less RAM offered at start of AoI lost datas are beginning to mess up the file.
Thank you very much for all your efforts! @Luke: This case happened the first time to me. So I copied some items from my original animation file to the rendertest file to make a proof by my own. The two frames I added above are the result I got from the rendertest file I attached. So may be, there were some informations still in my RAM, which brought the - for me obviously reproducable - flaw into my upper post. @ Pete: I don't know, how I managed to place the keys not in the right place. My original...
Thank you very much for all your efforts! @Luke: This case happened the first time to me. So I copied some items from my original animation file to the rendertest file to make a proof by my own. The two frames I added above are the result I got from the rendertest file I attached. So may be, there were some informations still in my RAM, which brought the - for me obviously reproducable - flaw into my upper post. @ Pete: I don't know, how I managed to place the keys not in the right place. My original...
Here is my next question for help: Rendering in moviemode gives back frames with wrong positioning of camera. Please try the testfile at frame 257 or later for this to verify. Rendering in single image mode gives the correct position in the render. Again I'm using AoI 3.2.0 on a windows pc with 64 GB RAM. ...?