` and I don't want to force users to wrap the component in a `\u003CSuspense />`.\r\n\r\nI looked for established patterns and found that `\u003CSmoke />` loads textures, but requires `\u003CSuspense />`. I think we can improve the DX by removing that requirement for users *and* providing a standard-ish way for components to avoid `await`ing.\r\n\r\n### Validations\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/cientos/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/cientos/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://cientos.tresjs.org/guide).\r\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/cientos/issues) that reports the same bug to avoid creating a duplicate.",[2867,2870,2873],{"name":2868,"color":2869},"good first issue","7057ff",{"name":2871,"color":2872},"help wanted","008672",{"name":2874,"color":2875},"p3-significant","2C78E3",264,"cientos","Components with textures shouldn't require `\u003CSuspense>`","2024-11-25T09:29:04Z","https://github.com/Tresjs/cientos/issues/264",0.6991026,{"description":2883,"labels":2884,"number":2885,"owner":2857,"repository":2886,"state":2859,"title":2887,"updated_at":2888,"url":2889,"score":2890},"## Bug description\r\n\r\nAll controls created using `useControls` are added to all instances of `\u003CTresLeches />` even if they're in separate files.\r\n\r\n## Expected behavior\r\n\r\nAllow multiple, separate instances of Leches. Don't share state across multiple, separate files.\r\n\r\n## Reproduction\r\n[StackBlitz](https://stackblitz.com/edit/tresjs-basic-jmjdqy?file=src%2Fcomponents%2FTheExperience.vue)\r\n\r\n## Solution?\r\n\r\nMaybe create and return a unique controls instance from `useControls` that closes over the current controls state.\r\n\r\n```\r\nconst controls = useControls({\r\n wireframe: false,\r\n})\r\n\r\ncontrols.useControls( /* ... add more controls to this instance */ )\r\n```\r\n\r\nThen use like\r\n\r\n```\r\n\u003CTresLeches :controls=\"controls\" />\r\n```\r\n\r\n## Screenshot\r\n\r\n\u003Cimg width=\"567\" alt=\"Screenshot 2024-02-23 at 19 56 28\" src=\"https://github.com/Tresjs/leches/assets/20469369/44cef606-cd01-49b4-a8d9-9dfdd3d0566c\">\r\n\r\n\r\n## Context\r\n\r\nWe use Leches for Cientos' docs and often have multiple separate examples of functionality in a given docs page. But we can't have multiple Leches menus on a given page without running into this bug.\r\n",[],98,"leches","Leches shares `useControls`; can't have multiple, distinct instances","2024-02-23T19:02:27Z","https://github.com/Tresjs/leches/issues/98",0.6996149,{"description":2892,"labels":2893,"number":2897,"owner":2857,"repository":2858,"state":2898,"title":2899,"updated_at":2900,"url":2901,"score":2902},"## Problem\r\n\r\nThe StackBlitz template for bug reproductions contains several redundant or extraneous elements. \r\n\r\n* This costs conscientious developers time, as they have to remove many unneeded elements from their bug reports.\r\n* This costs Tres devs time, reading through non-minimal reproductions. \r\n\r\nAs a Tres developer, in order to encourage and facilitate minimal bug reproductions, I would like to remove extra elements from the StackBlitz Bug reproduction starter template. \r\n\r\n## Suggested Solution\r\n\r\n* Remove the `src/components` folder.\r\n* Replace the code in `./src/App.vue` with the following:\r\n\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nimport { TresCanvas } from '@tresjs/core';\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CTresCanvas>\r\n \u003CTresMesh>\r\n \u003CTresBoxGeometry />\r\n \u003CTresMeshNormalMaterial />\r\n \u003C/TresMesh>\r\n \u003C/TresCanvas>\r\n\u003C/template>\r\n```\r\n\r\nThat makes this the starter template:\r\n\r\n\u003Cimg width=\"1334\" alt=\"Screenshot 2024-04-28 at 01 55 13\" src=\"https://github.com/Tresjs/tres/assets/20469369/237c9649-7794-4fe4-9c8f-0f749787168a\">\r\n\r\n### Alternative\r\n\r\nKeep as is.\r\n\r\n### Additional context\r\n\r\nFor comparison, here's the current `src/components/TheExperience.vue`. \r\n\r\nIt contains:\r\n\r\n* unused imports – `extend`, `reactive`\r\n* unnecessary configuration – `const gl = { ... }`\r\n* components that have no visual effect – `\u003CContactShadows />`, `\u003CTresDirectionalLight />`\r\n* redundant args – `\u003CTresBoxGeometry :args=\"[1, 1, 1]\" />`\r\n\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nimport { extend } from '@tresjs/core';\r\n\r\nimport { reactive } from 'vue';\r\nimport { BasicShadowMap, SRGBColorSpace, NoToneMapping } from 'three';\r\nimport { TresCanvas } from '@tresjs/core';\r\nimport { OrbitControls, ContactShadows } from '@tresjs/cientos';\r\n\r\nconst gl = {\r\n clearColor: '#82DBC5',\r\n shadows: true,\r\n alpha: false,\r\n shadowMapType: BasicShadowMap,\r\n outputColorSpace: SRGBColorSpace,\r\n toneMapping: NoToneMapping,\r\n};\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CTresCanvas v-bind=\"gl\">\r\n \u003CTresPerspectiveCamera :position=\"[9, 9, 9]\" />\r\n \u003COrbitControls />\r\n \u003CTresMesh>\r\n \u003CTresBoxGeometry :args=\"[1, 1, 1]\" />\r\n \u003CTresMeshNormalMaterial />\r\n \u003C/TresMesh>\r\n \u003CContactShadows />\r\n \u003CTresDirectionalLight :position=\"[0, 2, 4]\" :intensity=\"1.2\" cast-shadow />\r\n \u003C/TresCanvas>\r\n\u003C/template>\r\n\r\n```\r\n\r\n### Validations\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://tresjs.org/guide).\r\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/tres/issues) that reports the same bug to avoid creating a duplicate.",[2894],{"name":2895,"color":2896},"p1-chore","BFD4F2",669,"closed","Remove extraneous elements from StackBlitz Bug reproduction starter template","2024-04-30T15:03:58Z","https://github.com/Tresjs/tres/issues/669",0.6114765,{"description":2904,"labels":2905,"number":2909,"owner":2857,"repository":2858,"state":2898,"title":2910,"updated_at":2911,"url":2912,"score":2913},"**Describe the bug**\r\nWhen I use such as `:position-y` to set props, it not works. `position-y` will be transformed to `positionY`.\r\n\r\n**Reproduction**\r\n\r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. set vector props just like v1 \r\n2. see the object properties\r\n\r\n**Expected behavior**\r\nvector props set correctly\r\n\r\n**Screenshots**\r\n\r\n\r\n\r\n**System Info**\r\n\r\n\r\n\r\n**Additional context**\r\n \r\n",[2906],{"name":2907,"color":2908},"bug","d73a4a",198,"vector props can't set correctly","2023-04-12T17:58:08Z","https://github.com/Tresjs/tres/issues/198",0.61310935,{"description":2915,"labels":2916,"number":2917,"owner":2857,"repository":2877,"state":2898,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Describe the bug\n\nAfter setting up a Nuxt 3 project, installing the tres.js package, and adding the @tresjs/cientos package, I noticed that certain functionalities of @tresjs/cientos components were not working as expected. To address this, I made modifications to my nuxt.config.ts file as follows:\r\n```\r\nexport default defineNuxtConfig({\r\n modules: [\"@tresjs/nuxt\"],\r\n build: {\r\n transpile: ['@tresjs/cientos'],\r\n },\r\n})\r\n```\r\nDuring the development process, everything worked smoothly. \r\n\r\nHowever, upon executing the npm run build command, \r\nI observed that the auto-rotate feature of OrbitControls, MouseParallax component, Levioso component, animations within useGLTF, and the Html component were no longer functioning. \r\nImportantly, there were no error messages or warnings in the browser console.\r\n\r\nI have attempted to modify the project by setting ssr: false and removing any @tresjs/cientos-related configurations from nuxt.config.ts before recompiling. However, the issue persists regardless of whether I use npm run generate or npm run build.\r\n\r\nI kindly request assistance in resolving this issue. Your guidance on how to address or workaround this problem would be greatly appreciated.\r\n\r\nThank you for your time and attention to this matter.\n\n### Reproduction\n\nhttps://github.com/WangShuan/nuxt-tres\n\n### Steps to reproduce\n\n1. Run the following commands:\r\n```\r\ngit clone https://github.com/WangShuan/nuxt-tres\r\ncd nuxt-tres\r\nnpm i\r\nnpm run dev\r\n```\r\n2. Open http://localhost:3000/ in your browser and observe the results.\r\n3. Terminate the development server (Ctrl+C) and build the project by `npm run build`\r\n4. Run the production build by `node .output/server/index.mjs`\r\n5. Open http://localhost:3000/ in your browser and observe the discrepancy in functionality compared to the development build.\n\n### System Info\n\n_No response_\n\n### Used Package Manager\n\nnpm\n\n### Code of Conduct\n\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/cientos/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/cientos/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://cientos.tresjs.org/guide).\n- [X] Check that there isn't [already an issue](https://github.com/Tresjs/cientos/issues) that reports the same bug to avoid creating a duplicate.\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[],316,"@tresjs/cientos Components Not Functioning Properly After Nuxt 3 Build","2024-01-03T14:19:14Z","https://github.com/Tresjs/cientos/issues/316",0.63613445,{"description":2923,"labels":2924,"number":2931,"owner":2857,"repository":2858,"state":2898,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Describe the bug\n\nIt seems like Tres.js is no longer working in Firefox. Even on your official documentation all examles render just a black canvas.\r\nI would really like to use Tres.js in projects of my company, but I am unable to do this if Firefox is not supported or working :(\n\n### Reproduction\n\nhttps://tresjs.org/guide/\n\n### Steps to reproduce\n\nThe first and all other examples of this page.\n\n### System Info\n\n```shell\nWindows 10\r\nFirerfiox version 114.0.1 (64-Bit)\n```\n\n\n### Used Package Manager\n\nnpm\n\n### Code of Conduct\n\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://tresjs.org/guide).\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/tres/issues) that reports the same bug to avoid creating a duplicate.\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[2925,2928],{"name":2926,"color":2927},"question","d876e3",{"name":2929,"color":2930},"waiting for author","B145BC",310,"Black Canvas in Firefox","2023-06-20T07:13:04Z","https://github.com/Tresjs/tres/issues/310",0.6418157,{"description":2937,"labels":2938,"number":2939,"owner":2857,"repository":2877,"state":2898,"title":2940,"updated_at":2941,"url":2942,"score":2943},"**Is your feature request related to a problem? Please describe.**\r\nContinuing with the controls abstraction, will be useful to add MapControls to cientos catalog\r\n\r\n**Describe the solution you'd like**\r\n\u003CMapControls \r\nscreen-space-panning\r\n />\r\n\r\n**Suggested solution**\r\nSimilar to other controls already implemented\r\n\r\n",[],52,"MapControls abstraction","2023-05-03T17:42:07Z","https://github.com/Tresjs/cientos/issues/52",0.64561486,{"description":2945,"labels":2946,"number":2939,"owner":2857,"repository":2947,"state":2898,"title":2948,"updated_at":2949,"url":2950,"score":2943},"### Describe the bug\r\n\r\nI am trying to add \u003COrbitControls /> and importing it by \"import { OrbitControls } from '@tresjs/cientos';\"\r\nI am getting the following error\r\n`\r\nError: Build failed with 1 error:\r\nnode_modules/@tresjs/cientos/dist/trescientos.js:14:27: ERROR: Could not resolve \"tweakpane\"\r\n`\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/tresjs-basic-fmxtip?file=package.json\r\n\r\n### Steps to reproduce\r\n\r\nrun `npm install @tresjs/cientos @tresjs/post-processing` then `npm run dev`\r\nin index.vue \r\n`import { OrbitControls } from '@tresjs/cientos';`\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 14.0\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 140.11 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 18.15.0 - /usr/local/bin/node\r\n npm: 9.5.1 - /opt/homebrew/bin/npm\r\n Watchman: 2023.07.17.00 - /opt/homebrew/bin/watchman\r\n Browsers:\r\n Brave Browser: 118.1.59.117\r\n Chrome: 117.0.5938.149\r\n Safari: 17.0\r\n```\r\n\r\n\r\n### Used Package Manager\r\n\r\nnpm\r\n\r\n### Code of Conduct\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://tresjs.org/guide).\r\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/tres/issues) that reports the same bug to avoid creating a duplicate.\r\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[],"nuxt","Cannot find package 'tweakpane'","2023-10-15T08:50:55Z","https://github.com/Tresjs/nuxt/issues/52",{"description":2952,"labels":2953,"number":2955,"owner":2857,"repository":2877,"state":2898,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Description\r\n\r\nVue 3.3.4 added an experimental feature called propsDeconstruct allowing us to dispense `withDefaults` in favor of a more natural deconstruction that keeps the reactivity.\r\n\r\n```\r\nconst { args = [1, 1, 1], color = '0xffffff' } = defineProps\u003C{\r\n args?: ConstructorParameters\u003Ctypeof BoxGeometry>\r\n color?: TresColor\r\n}>()\r\n```\r\n\r\n### Suggested solution\r\n\r\nAs of now, the following components has been updated, we need to update the rest\r\n\r\n- [x] All shapes\r\n- [ ] Smoke\r\n- [ ] Stars\r\n- [ ] Levioso\r\n- [ ] Contact Shadows\r\n- [x] Transform Controls\r\n- [x] Orbit Controls\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/cientos/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/cientos/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://cientos.tresjs.org/guide).\r\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/cientos/issues) that reports the same bug to avoid creating a duplicate.",[2954],{"name":2868,"color":2869},83,"Update all components to use prop deconstruction","2023-07-07T15:21:52Z","https://github.com/Tresjs/cientos/issues/83",0.6545691,["Reactive",2961],{},["Set"],["ShallowReactive",2964],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fVb8Ys4gPvqs31Tf74UwC6hdnqLAj2Xl8H1N6viulDYw":-1},"/Tresjs/tres/631"]