When frame rate is low I can't see anything that is limiting the framerate

[forthtemple]

I am developing a windows game using three_js. When the framerate is low I dont see high GPU or CPU usage and the memory usage isn't high and disk usage is normal. I am not seeing anything that would be limiting the frame rate. I was wondering why I might be seeing this? Is it something to do with Angle?

[Knightro63]

Hi @forthtemple,

I have noticed the same issue recently. I am currently moving anlge from using native array to typed data, which might help. Also one thing you might be able to do is change in three_js_core file three_viewer.dart

      texture = await angle?.createTexture(      
        AngleOptions(
          width: width.toInt(), 
          height: height.toInt(), 
          dpr: _resolution!,
          alpha: settings.alpha,
          antialias: settings.antialias,
          customRenderer: !settings.useSourceTexture,
          useSurfaceProducer: false
        )
      );

This will use glreadpixels and not flutters generated opengl texture. I think the problem is that newer versions of flutter are struggling with opengl textures directly.

[forthtemple]

Thanks for looking into it. I tried changing useSurfaceProducer to false but didn't seem to effect anything. I used the latest code on github.

[Knightro63]

Hi @forthtemple,

Sorry for taking a long time to get back to you. Some new Authors have helped to update flutter_angle to fix some of the Windows with low memory skipping frames.

I have also updated three_js to remove Native arrays and use TypedList to fix some of the memory leaking.

Let me know if this has fixed the issues.

[forthtemple]

Thanks for looking into it. An issue I am having with the new version on windows I get the following error message:

INFO: GL error: HIGH: Framebuffer is incomplete.
INFO: GL error: HIGH: Draw framebuffer is incomplete
INFO: GL error: HIGH: Draw framebuffer is incomplete
INFO: GL error: HIGH: Draw framebuffer is incomplete

And I saw in the same issue in
#26
with the issue being having shadows turned on (ie enableShadowMap: true). Seemed to work with shadows turned off though had some flickering. Possibly the new version introduced the same shadow issue from last year.