6 Replies
      Latest reply on Oct 31, 2019 8:49 AM by 3DWizard
      chunlong Level 1 Level 1 (0 points)

        I have created a separate thread for rendering task. And it is not vsynced which means the thread could generate frames multiple times within one vsync. Because it generates frames faster than GPU, [CAMetalLayer nextDrawable] would sometime wait a whole vsync time to return a valid drawable. But after a few good frames, [CAMetalLayer nextDrawable] begins to return nil. Is this bug of metal? Although the document says this is due to incorrect configuration of CAMetalLayer, I am sure my configuration is done correctly.