3 ms·

How do you read this thing? All I see is "React Three Fiber". It put my laptop on Takeoff mode (fans full speed!) with Firefox.

• westoncb 8y ago
  Clink the link to their Github page in the upper left corner.
  • omeid2 8y ago
    Cool, strange you would expect the source would on Github and website is the reference? what do I know. None of the demos work on Firefox.
    • tazard 8y ago
      They work perfectly fine on Firefox for Android v65.0.1
    • mlsarecmg 8y ago
      I just started a week ago, didn’t polyfill the demos, but will do it when i get around it, nothing in there that wouldn’t work in FF. Would be super happy for GH issues (for instance error logs).
• outworlder 8y ago
  > It put my laptop on Takeoff mode (fan's full speed!) with Firefox. This is why all this movement to rebuilding a browser in browser is ineffective. Non sequitur. Your computer is doing more processing. There's WebGL, which will engage your graphics card. If it is on your CPU, the CPU will consume more power. Depending on your laptop, you could have a discrete graphics card, which will be switched to and consume more power. There are animations, etc. It is not only because of React. In fact, by avoiding unnecessary DOM changes, it's probably an advantage (although this would have to be measured). Unless you are telling us that you were playing fortnite or something and your fans didn't spin up, but this thing caused them to spin up.
  • omeid2 8y ago
    You missed the point that it doesn't work at all, so it is obviously broken in someway in Firefox. I run multiple VMs and do 3d work (in fact, mostly direct opengl stuff) on my laptop and it hardly ever goes to takeoff mode with just some simple rendering.
    • nailer 8y ago
      It's broken in Chrome too - there's no content asides from 'Reach three fibre' and the links. I would have expected at least a description to exist on the page.
      • onion2k 8y ago
        I would have expected at least a description to exist on the page. It's a work-in-progress demo of react-three-fiber. There's a good explanation of what it is on the Github page - https://github.com/drcmda/react-three-fiber https://github.com/drcmda/react-three-fiber
      • mlsarecmg 8y ago
        I ran it both in Chrome and Firefox, seems to be working. Could i bother you for error logs?
        • shakna 8y ago
          Well, it appears broken for me... But I don't have any errors in the logs. Firefox 65.0.1 (64bit), Linux (5.0.0). There are a couple warnings about a particular extension: > warning: extension `GL_ARB_gpu_shader5' unsupported in fragment shader The rest just appears to be successful parsing messages. (But it worked really well in Konqueror & Chromium, so that's something.)
          • mlsarecmg 8y ago
            I googled that, looks like an issue in FF: https://github.com/mrdoob/three.js/issues/9716 https://github.com/mrdoob/three.js/issues/9716 Basically i just channel through regular three without creating much of a dependency. If it doesn't work in react-three-fiber, then i doesn't work in threee-js. But they're so big that usually these webGL bugs are either fixed quickly by them, if it's their fault, or they're filling vendor issues.