This is my first xcrete after the platform name change, how exciting. So glad to be xcreting on here now, be sure to follow me for more fascinating xcretions.
Hey @FirefoxSupport folks: FF99 (and 100beta) have breaking perspective/transform-style/scaling issues. Here's Chrome, Safari, Edge and Firefox all with the same HTML. Breaks the three.js CSS3dRenderer. Guess which one is FF :(
So now that developers everywhere are making their own versions of a Metaverse, and we're going to have mega Metaverse compatibility fragmentation... What's the plural of Metaverse?
@prestopasto@dceddia@DavidKPiano Yeah, when figuring out where my precious 16ms were going, I was seeing the scheduling component of XState popping up, sometimes taking up to 6ms. Even though I'm doing no scheduling!
@DavidKPiano@dceddia Each frame three.js raycasts the current mouse/touch position to all the 3D geometry, then xState figures out what was intersected, and what to do with that intersection/movement.
@DavidKPiano@dceddia Looking forward to v5! I'm slowly replacing a metric shit ton of MobX variables with State machines in @SeekBeak. Where I was taking a hit was doing onDrag hover/bounds checking with node handles to create/update polygon Hotspot Shapes.
@dceddia@DavidKPiano Great article Dave! I recently 'downgraded' some of my XState machines to XState/FSM. Needed a speed boost as they were doing 60fps animation work. Normal XState was sucking up too many ms. Also debating on Robot, so this is a good resource!
Funny how many correlations there are between creative industries. For WebDev, Safari is the equivalent of the audio engineering NS-10s. If you can get it working there, it'll work everywhere. *Except IE of course.