Lag with new client

[Polo]

My fans dont adjust speed, and on Classic, Graal is only using like 2 or 3% cpu time on my AthlonXP 2600+.... I dont know, I dont exactly think its grossly innefficient.

[Ibonic]

Originally Posted by Polo

the GFX are not the CPU intensive thing as thats all handled by the GFX card.

I believe Graal 2 does (or did) use DelphiX; If you look at the samples/tutorials for that, DirectX or OpenGL, most of them take as much CPU as possible before you have anything more than some simple text or a single graphic displayed on the screen -- but those are generally bad coding practices where people continuously redraw the entire scene when it's not needed, or they have no kind of 'sleeping' taking place in the timer. I assume Stefan didn't do something like that, but it's ridiculous when you see how many people do.

Originally Posted by Polo

Graal is only using like 2 or 3% cpu time on my AthlonXP 2600+

First time I've ever seen that reported
The new level editor only uses 2-3% of the CPU for me too, but I have even better processors than that with good video cards in my desktops and Graal 2.2.2 still uses 99% or as much is available.

[Polo]

Originally Posted by Ibonic

Graal 2.2.2 still uses 99% or as much is available.

Graal 2.2.2 is not the current verion though. Since 2.3 it has been optimised to not take full CPU time.

[superb]

Originally Posted by Polo

Graal 2.2.2 is not the current verion though. Since 2.3 it has been optimised to not take full CPU time.

And Stefan said he was going to put THAT BACK IN. That was what my post was about in the first place... x.x

[Ibonic]

Originally Posted by Polo

Graal 2.2.2 is not the current verion

I typed it out for that reason, in hope that people will know I was referring to the old version. And I mentioned what I did about heat and so on because I also thought we were talking about Stefan readding the CPU hammering / personal oven feature from pre-2.3 versions.

[Admins]

Originally Posted by superb

And Stefan said he was going to put THAT BACK IN. That was what my post was about in the first place... x.x

The question is if Graal should go back into the old mode when it's running slow, e.g. if people ignore to install good gfx drivers. v2.3 and v3.1 should only take 3-5% CPU time on a normal PC, but if you have a bad gfx driver or programs running which take a lot of cpu time then the new version might be slower because it is not trying to steall all the cpu time.

[Ibonic]

Originally Posted by Stefan

The question is if Graal should go back into the old mode when it's running slow ...

That might be the easiest solution, but probably not the best.

If you decide to make it automatically detect if it's running slow, can you add some kind of override so that it doesn't force you to use the old timing? Maybe even ask in a dialog, e.g. "Graal has detected a very low frame rate, would you like to try the pre-2.3 timing method?" and then save the preference which can also be toggled in the options window.