[bB.0d]Freeze detect

[zarexz]

Sometimes when I open a specific track, in the Canyon track editor, the screen freezes for a while and generates a FreezDetect.txt with the code 01602DE4

[TMarc]

Does the freeze lead to a crash, or is it only a temporary freeze?

Are you running full-screen or windowed?
Because in windowed mode, you can see the title bar message changing, it says different loading messages, up to shader and shadow calculation. This can take some while, or it could be a timeout of inaccessible manialinks used in that map.

Does the freeze happen everytime you load this specific map, or does it happen only at the very first loading attempt?

Could you perhaps upload or give a link to such a map?

[zarexz]

No it never leeds to a crash. It's just a temporary freeze. I noticed it happend on a new empty map aswell today. It looks like it happens when I move the mouse arround too soon but I'm not sure.

The durations of the freezes differ aswell. It also freezes while driving in editor mode but those don't get recorded. The ones that get recorded are always from opening a map. It's also always the same code in the freezedetect.txt.

I always run in fullscreen mode.

GreetingZ!

[TMarc]

In fact there are many places where such freezes can be perceived, especially if the CPU is not the fastest.
I have observed freezes at map loading, opening the editor, and also when placing blocks for the first time (this is a "cache and shader calculation thing", as Hylis explained a while ago).

[zarexz]

In fact there are many places where such freezes can be perceived, especially if the CPU is not the fastest.

My CPU is a 3Ghz quadcore. 3 of them cores are ALWAYS bored to death or extra lazy or picking their nose or doing nothing at all. I doubt that's the problem

But seriously, when I play TM, the only other thing I may be running in the background too is my ancient photoshop version, nothing else. Freezes are there when I only run TM aswell.