Tuesday, February 8, 2011

DirectQ Update - 8th February 2011

Been doing some more benchmarking, and I'm now getting almost 100 FPS in the main canyon area of the Marcher Fortress on an Intel 945. Yeah, this one is gonna be good.

Fixed the PF_VarString crash. It only happens when you exit a map, and is caused by a NaN in the globals; adding a simple NaN check before the G_STRING resolves it nicely. And as it only happens on exiting a map, it's safe to just swallow the error harmlessly.

I guess the root cause of this is different floating point exception setting defaults in the compiler (between MSVC 6 and MSVC 2008), or possibly removal of the ASM code. But it still feels good to have finally tracked it down and understood why it was happening.

6 comments:

=peg= said...

Nice! Also, 100 fps on marcher on intel crap, wow, just wow! :D

Nick said...

i'm a little irritated by the fps. on my laptop i'm getting constant 60fps. it hardly drops below that. shouldn't it be at 72fps?

MichealS said...

Are you using VSync?

mhquake said...

Yeah, sounds like vsync is on and it's locking framerates to your monitor's refresh rate. Options | Video Options | Vertical Sync and switch it to off.

Nick said...

ok getting constant 71fps now guess that counts as 72 ;-)
can't wait for the new version

mhquake said...

Yup, 71 is normal. The timer fix for newer PCs doesn't have enough resolution to give an even 72; believe me - the alternative is worse.