Module Use Error: "No frames detected. Try moving the camera or implementing requestAnimationFrame."
See original GitHub issueI am trying to use the spectorjs
module.
const s = new SPECTOR.Spector();
s.displayUI();
This renders the Spector UI:
When I try to record I get the error.
No frames detected. Try moving the camera or implementing requestAnimationFrame.
I definitely have requestAnimation frame running. The UI detects multiple canvas’s on the page. One of them being the correct webgl canvas.
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
three.js - Angular component with requestAnimationFrame issue
Im using the stats-js lib to detect frame rate, normally its around 40fps, but it adds up to 120-220fps or more. My computer...
Read more >JavaScript rAF in a nutshell (requestAnimationFrame) - Medium
That means, the element has to move in roughly about (1000 ms /60 frames) = 16.7 ms . Let's move our DOM element...
Read more >Window.requestAnimationFrame() - Web APIs | MDN
The window.requestAnimationFrame() method tells the browser that you wish to perform an animation and requests that the browser calls a ...
Read more >#SpectorJS - Twitter Search / Twitter
I keep getting, "No frames detected. Try moving the camera or implementing requestAnimationFrame." 2.
Read more >Face Detection and Censorship - Beginner JavaScript - Wes Bos
We are going to build a face detection that will detect and blur your face from a video ... What is probably easier...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t want to clutter this issue, but @pasu please make an issue here https://github.com/Esri/cim-symbol-builder-js for your issue. The ArcGIS team is going to be looking at the original issue raised here, so thank you very much @JannikGM for help narrowing it down. Our WebGL devs will take a closer look. Thanks!
Done, this would make those calls safer: https://github.com/BabylonJS/Spector.js/commit/708f1f7063b240a8f0bd4f31ea281ef91bc88073