It is a result of windows dynamic Ram management. In the Beginning DirectX is still busy with moving things from A to B etc. after several seconds Windows has removed all unneccessary stuff from Ram (such as other apps you used before you started the game) and loaded all textures to the right memory, as described before. First I have thought this is a weakness of blitz, but then I realized it's a DirectX thing. You have to use some tricks to prevent this. EG: render the first scene to the backbuffer several times while rotating the camera around its axis, but don't Flip the Scene to the visible buffer. Or, when you're in Windowed Mode, you might need to use an other trick. Then, when DirectX has everything ready on the right place, you can start the game as usual.
I have also seen this effect with the Lithtech Engine: When you run NOLF and press Esc nervously to skip all those Intro Movies, the game jumps exactly in the same way like some hungry blitz apps in the first 5 or ten seconds.
I have also seen this effect with the Lithtech Engine: When you run NOLF and press Esc nervously to skip all those Intro Movies, the game jumps exactly in the same way like some hungry blitz apps in the first 5 or ten seconds.