I think I've had this.
Make your game windowed and open up taskmanager, and check if some program is taking up alot of memory.
There's this program, (Unnamed atm,) that slows you down when you start UT.
It doesn't seem essential, since you can just shut it off without UT crashing or anything.
More info when available. _________________ Kick up that pan.
There a few windows background processes basically, such as a set of WMI (Windows management Interface) programs that do performance and GUI status logging that do glitch out the mouse and the program your trying to run for the first minute or so it seems - then after all the initial program variables and properties are setup it smooths out.
Mine does a similar thing but not quite as drastic, it seems to take about 2-3 minutes for it to stop glitching on mine - then it smooths out.
I would normally think that it's the connection between the editor and the game, but it also does it when I run the game first and then the editor so the game & test map load & run much faster - and when I'm done testing I leave the game open but minimized and FLUSH the memory buffer caches and run the nVidiaLogo or nointro map to sever the connection between it and UED, otherwise you can't do another test map(autoplay) right away after fixing something because the game still has 'Autoplay.ut2' in it's buffer.
After testing once with that configuration, the glitching doesn't happen - but it may also be something related to the regular download cache too, since even running a test map - the engine still checks the cache for relevant content(ie. player & map data) even though it wouldn't normally be able to use it unless it were in the regular ut folders.
. _________________ http://www.gamefront.com/files/user/likemikes/ " War is lost, without it's Shepard's to sustain it. " :P
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum