gltfjsx VS react-three-a11y

Hello! I loaded a model using https://gltf.pmnd.rs and it displays correctly, but there are weird gaps that you can see through on the edges. This is a Next.js project with ts. I'm using @react-three/fiber and @rect-three/drei to use three.js in react. I'll attach the file that creates this object, but if there's anything more you need, just ask me. Here's the file that contains the code of this object:

Then we need to generate a react component that will contain the markup of this model to add it to the scene. Let's use the official resource from the @react-three/fiber developers.

especially for what you describe above. it can lay out a glb model declaratively, the whole scene is yours to control. watch the first video here https://github.com/pmndrs/gltfjsx and then use that tool:

stuff like this doesn't have to be keyframed, you can just rotate model groups. im sure this will be overwhelming atm but if you have the time watch the video there https://github.com/pmndrs/gltfjsx models in threejs are blobs, they are not meant to do anything. people traverse them and create mutations. but that tool puts the entire model scene under your control, every node in its graph is declarative now, to my it dynamic is trivial at that point.

the second practically doesn't exist in vanilla three. a gltf is a blob that you throw into the scene. pair three with react and blender will be a lot more useful: https://github.com/pmndrs/gltfjsx (watch the first video there)

I want to implement this for a gltf model loaded as a gltfx. MeshWobbleMaterial is not getting qpplied. i don't know what to where to add the component either. i have attached the code below,

/* Auto-generated by: https://github.com/pmndrs/gltfjsx Command: npx [email protected] crystal_ball_test.glb Author: WarderiiK (https://sketchfab.com/WarderiiK) License: CC-BY-4.0 (http://creativecommons.org/licenses/by/4.0/) Source: https://sketchfab.com/3d-models/crystal-ball-test-fc727811052a4b2ba9ef2ffa327e8349 Title: Crystal Ball Test */ import React, { useRef } from 'react' import { useGLTF, useAnimations, MeshTransmissionMaterial } from '@react-three/drei' export default function Model(props) { const group = useRef() const { nodes, materials, animations } = useGLTF('/crystal_ball_test.glb') const { actions } = useAnimations(animations, group) return ( ) }

Have you compressed your models with https://gltf.pmnd.rs ? ( sorry this is unrelated to your post ) or you could use https://github.com/pmndrs/gltfjsx ( same thing but you use it like an npm package )

Thanks! Threlte is "just" offering a declarative way to express Three.js. If you know how the `` component and its props and event handlers work, you can use the Three.js documentation for everything else.

Apart from that with Threlte I personally practice documentation-driven-development, so ecosystem packages are exhaustively documented. If you're missing something, let us know via an issue[1] or on Discord[2].

Accessibility is a topic we didn't care enough yet to be perfectly honest. Accessibility doesn't stop at screen readers though, it's about contrast, size, colors, motion, reachability, and so much more that we cannot provide and are a consumer topic. Naturally WebGL apps suffer from being practically invisible to screenreaders. There are workarounds[3] but essentially this has to be solved by consumers of Threlte (devs) and hopefully by browser vendors at some point in the future.

[1] https://github.com/threlte/threlte/issues

[2] http://chat.threlte.xyz

[3] https://github.com/pmndrs/react-three-a11y

There is an accessibility library from drei: https://github.com/pmndrs/react-three-a11y

Caveat: Not the most accessible thing ever. The pmndrs crew made a tool that does this way more accessibly, this would be my production-grade recommendation: https://github.com/pmndrs/react-three-a11y

like /u/thesonglessbird said, it exists: https://github.com/pmndrs/react-three-a11y it covers screen readers, tabbing , focus indication, roles, and so on.

That’s a bit of a cop out - React Three Fiber renders to a canvas too (obviously) and there’s a bunch of accessibility stuff in its semi-official ecosystem https://github.com/pmndrs/react-three-a11y

♿ R3F A11y

To simulate the selected state you can try to use react-three-a11y. By wrapping our model with the component we will have access to hover, focus, and pressed state through useA11y() hook. We can try to display a SelectedMaterial based on the hover state for example.