# Composables Vue 3 [Composition API](https://vuejs.org/guide/extras/composition-api-faq.html#what-is-composition-api) allows you to create reusable logic that can be shared across components. It also allows you to create custom hooks that can be used in your components. **TresJS** takes huge advantage of this API to create a set of composable functions that can be used to create animations, interact with the scene and more. It also allows you to create more complex scenes that might not be possible using just the Vue Components (Textures, Loaders, etc.). The core of **TresJS** uses these composables internally, so you would be using the same API that the core uses. For instance, components that need to updated on the internal render loop use the `useRenderLoop` composable to register a callback that will be called every time the renderer updates the scene. ## useRenderLoop The `useRenderLoop` composable is the core of **TresJS** animations. It allows you to register a callback that will be called on native refresh rate. This is the most important composable in **TresJS**. ```ts const { onLoop, resume } = useRenderLoop() onLoop(({ delta, elapsed }) => { // I will run at every frame ~ 60FPS (depending of your monitor) }) ``` ::: warning Be mindfull of the performance implications of using this composable. It will run at every frame, so if you have a lot of logic in your callback, it might impact the performance of your app. Specially if you are updating reactive states or references. ::: The `onLoop` callback receives an object with the following properties based on the [THREE clock](https://threejs.org/docs/?q=clock#api/en/core/Clock): - `delta`: The delta time between the current and the last frame. This is the time in seconds since the last frame. - `elapsed`: The elapsed time since the start of the render loop. This composable is based on `useRafFn` from [vueuse](https://vueuse.org/core/useRafFn/). Thanks to [@wheatjs](https://github.com/orgs/Tresjs/people/wheatjs) for the amazing contribution. ### Before and after render You can also register a callback that will be called before and after the renderer updates the scene. This is useful if you add a profiler to measure the FPS for example. ```ts const { onBeforeLoop, onAfterLoop } = useRenderLoop() onBeforeLoop(({ delta, elapsed }) => { // I will run before the renderer updates the scene fps.begin() }) onAfterLoop(({ delta, elapsed }) => { // I will run after the renderer updates the scene fps.end() }) ``` ### Pause and resume You can pause and resume the render loop using the exposed `pause` and `resume` methods. ```ts const { pause, resume } = useRenderLoop() // Pause the render loop pause() // Resume the render loop resume() ``` Also you can get the active state of the render loop using the `isActive` property. ```ts const { resume, isActive } = useRenderLoop() console.log(isActive) // false resume() console.log(isActive) // true ``` ## useLoader The `useLoader` composable allows you to load assets using the [THREE.js loaders](https://threejs.org/docs/#manual/en/introduction/Loading-3D-models). It returns a promise with loaded asset. ```ts import { GLTFLoader } from 'three/examples/jsm/loaders/GLTFLoader' const { scene } = await useLoader(THREE.GLTFLoader, 'path/to/asset.gltf') ``` Since the `useLoader` composable returns a promise, you can use it with `async/await` or `then/catch`. If you are using it on a component make sure you wrap it with a `Suspense` component. See [Suspense](https://vuejs.org/guide/built-ins/suspense.html#suspense) for more information. ```vue ``` ## useTexture The `useTexture` composable allows you to load textures using the [THREE.js texture loader](https://threejs.org/docs/#api/en/loaders/TextureLoader). It returns a promise with the loaded texture(s). ```ts const texture = await useTexture(['path/to/texture.png']) ``` **useTexture** also accepts an object with the following properties: - `map`: a basic texture that is applied to the surface of an object - `displacementMap`: a texture that is used to add bumps or indentations to the object's surface - `normalMap`: a texture that is used to add surface detail to and variations in shading to the object - `roughnessMap`: a texture that is used to add roughness or a matte finish to the object's surface - `metalnessMap`: a texture that is used to add a metallic effect to the object's surface - `aoMap`: a texture that is used to add ambient occlusion (shading in areas where light is blocked by other objects) to the object. In that case it will return an object with the loaded textures. ```ts const { map, displacementMap, normalMap, roughnessMap, metalnessMap, aoMap } = await useTexture({ map: 'path/to/albedo.png', displacementMap: 'path/to/height.png', normalMap: 'path/to/normal.png', roughnessMap: 'path/to/roughness.png', metalnessMap: 'path/to/metalness.png', aoMap: 'path/to/ambien-occlusion.png', }) ``` Then you can bind the textures to the material. ```vue ``` Similar to above composable, the `useTexture` composable returns a promise, you can use it with `async/await` or `then/catch`. If you are using it on a component make sure you wrap it with a `Suspense` component. # useCatalogue The `useCatalogue` composable allows you to extend the internal catalogue of components. It returns a function that you can use to register new components. This is specially useful if you want to use objects that are not part of ThreeJS core like[OrbitControls](https://threejs.org/docs/#examples/en/controls/OrbitControls) or third party functionality, like physics. ```ts import { useCatalogue } from '@tresjs/core' import { OrbitControls } from 'three/examples/jsm/controls/OrbitControls' const { extend } = useCatalogue() extend({ OrbitControls }) ``` Then you can use the new component in your template. Notice that the new component is prefixed with `Tres` to avoid name collisions with native HTML elements, similar to the rest of the core components. ```vue ``` # useTres This composable aims to provide access to the state model which contains the default renderer, camera, scene, and other useful properties. It is still experimental and it is not recommended to use it in production because is highly like subject to change. ```ts const { state } = useTres() console.log(state.camera) // THREE.PerspectiveCamera console.log(state.renderer) // THREE.WebGLRenderer ``` Until this composable is stable, it is recommended to use the `provide/inject` API to acces the elements you need. These are the available keys: - `camera`: it returns the current active camera - `renderer`: it returns the current active renderer - `local-scene`: it returns the current active scene - `catalogue`: it returns the current catalogue of components - `extend` : it returns the `extend` function from the `useCatalogue` composable. Specially needed if you are a plugin author. - `aspect-ratio`: it returns the current aspect ratio of the canvas ```ts import { provide, inject } from 'vue' const camera = inject>('camera') const renderer = inject>('renderer') console.log(camera.value) // THREE.PerspectiveCamera console.log(renderer.value) // THREE.WebGLRenderer ```