Irrlicht Engine

If you are running in full screen mode and you have vsync enabled then the maximum frame rate will be the frame rate of your monitor.

To test it, simply change your monitor refresh rate and re-run the application.

Okay I have been tracking down the problem in a debug build of irrlicht and it does look like it is an animated mesh scene node problem.

When I removed the Animation Set { } section from .X files, the frame rate increased significantly back to where it should be. I have not been animating the ...

Thanks for the prompt reply Hybrid,

I am also suspecting it is the animated meshes. I also did the plain vanilla out-of-the-box comparisons between 1.2 and 1.3 and for me the collision example was:

1.3 = 207 fps and
1.2 = 338 fps.

The lighting did look a little different though (I'm not sure if ...

Hi there,

I have been using Irrlicht for a number of projects for over a year, but since I upgraded to 1.3 in the last couple of days I have noticed a significant slowdown in performance (fps) down to about a 1/3 of what 1.2 achieved. I am only testing in DX9.

I have tried everything I could think ...

I have seen this happen in Irrlicht. If you are loading a .X file, with animations, and the loader cannot find a texture (perhaps the path to the texture in the .X file is invalid) then the model loads fine, but does not animate.

When I had this happen as soon as I fixed the path to the texture in ...

ooops just found it, never mind.
It was the:

AnimXNormals.patchCXAnimationPlayer normals fix by yin nadie.

under IrrlichtNX(++) patches

steveth45,

Do you know/remember which patch it was on the http://parsys.informatik.uni-oldenburg. ... /irrlicht/

web page that fixed the normals not getting transformed with the animated joints? I looked through the list but it wasn't obvious.