and \u003CTresStereoCamera /> but nothing works. I either get a blank black screen or a bluescreen with a line through it (when using the default example from the TresJS starter repo)\r\n\r\nThis is after being able to use \u003CTresPerspectiveCamera /> without any issues and just swapping out the camera used. Would appreciate any ideas or info how to implement this thanks.\n\n### Suggested solution\n\nImplement Array or StereoCamera as Tres JS native component preconfigured to work with VR.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\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.",[2867,2870],{"name":2868,"color":2869},"investigation","D03599",{"name":2871,"color":2872},"waiting for author","B145BC",102,"Tresjs","XR","open","VR Style Camera (Aframe implementation or ArrayCamera/StereoCamera from three","2024-08-21T10:45:26Z","https://github.com/Tresjs/XR/issues/102",0.7148303,{"description":2882,"labels":2883,"number":2884,"owner":2874,"repository":2885,"state":2876,"title":2886,"updated_at":2887,"url":2888,"score":2889},"### Describe the bug\n\n\u003CTresCanvas v-bind=\"canvasConfig\" ref=\"TresCanvasRef\">\r\n \u003Ctemplate v-for=\"(item,i) in lightSetting\">\r\n \u003Ccomponent ref=\"lightRef\" :is=\"item.type\" v-light-helper v-bind=\"item.config\" />\r\n \u003C/template>\r\n\u003C/TresCanvas>\r\n\u003Cscript>\r\nconst options = [ {\r\n label: '平行光',\r\n value: 'TresDirectionalLight',\r\n },\r\n {\r\n label: '点光源',\r\n value: 'TresPointLight',\r\n },\r\n {\r\n label: '聚光灯',\r\n value: 'TresSpotLight',\r\n },\r\n {\r\n label: '半球光',\r\n value: 'TresHemisphereLight',\r\n }]\r\n const lightSetting = ref([{\r\n type: 'TresDirectionalLight',\r\n config: {\r\n position: [5, 5, 5],\r\n targets: [0, 0, 0],\r\n color: '#ffffff',\r\n intensity: 1,\r\n castShadow: false\r\n }\r\n }\r\n ])\r\n\u003C/script>\r\n当我改变 type 值的时候就报错 Cannot read properties of null (reading 'children'),不加 v-light-helper的时候正常不会报错。\n\n### Reproduction\n\n还未上线\n\n### Steps to reproduce\n\n\u003CTresCanvas v-bind=\"canvasConfig\" ref=\"TresCanvasRef\">\r\n \u003Ctemplate v-for=\"(item,i) in lightSetting\">\r\n \u003Ccomponent ref=\"lightRef\" :is=\"item.type\" v-light-helper v-bind=\"item.config\" />\r\n \u003C/template>\r\n\u003C/TresCanvas>\r\n\u003Cscript>\r\nconst options = [ {\r\n label: '平行光',\r\n value: 'TresDirectionalLight',\r\n },\r\n {\r\n label: '点光源',\r\n value: 'TresPointLight',\r\n },\r\n {\r\n label: '聚光灯',\r\n value: 'TresSpotLight',\r\n },\r\n {\r\n label: '半球光',\r\n value: 'TresHemisphereLight',\r\n }]\r\n const lightSetting = ref([{\r\n type: 'TresDirectionalLight',\r\n config: {\r\n position: [5, 5, 5],\r\n targets: [0, 0, 0],\r\n color: '#ffffff',\r\n intensity: 1,\r\n castShadow: false\r\n }\r\n }\r\n ])\r\n\u003C/script>\r\n当我改变 type 值的时候就报错 Cannot read properties of null (reading 'children'),不加 v-light-helper的时候正常不会报错。\n\n### System Info\n\n```shell\nCannot read properties of null (reading 'children')\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.",[],871,"tres"," Cannot read properties of null (reading 'children')","2024-11-13T01:30:10Z","https://github.com/Tresjs/tres/issues/871",0.7525581,{"description":2891,"labels":2892,"number":2905,"owner":2874,"repository":2906,"state":2907,"title":2908,"updated_at":2909,"url":2910,"score":2911},"### Description\n\nAs a developer using tres-rapier I would like to have an option to create colliders by hand\n\n### Suggested solution\n\nResearch required but, could be something like:\r\n\r\n```\r\n \u003CRigidBody position={[0, 10, 0]}>\r\n \u003CSphere />\r\n \u003CBallCollider args=\"[0.5]\" />\r\n \u003CBallCollider args=\"[0.5]\" position=\"[1, 0, 0]\" />\r\n \u003C/RigidBody>\r\n```\r\nAs base:\r\nhttps://github.com/pmndrs/react-three-rapier?tab=readme-ov-file#collider-components\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/rapier/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/rapier/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://rapier.tresjs.org/guide).\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/rapier/issues) that reports the same bug to avoid creating a duplicate.",[2893,2896,2899,2902],{"name":2894,"color":2895},"help wanted","008672",{"name":2897,"color":2898},"feature","c2e0c6",{"name":2900,"color":2901},"p3-significant","2C78E3",{"name":2903,"color":2904},"PR welcome","2D76B0",103,"rapier","closed","Colliders","2024-09-17T13:12:32Z","https://github.com/Tresjs/rapier/issues/103",0.4578309,{"description":2913,"labels":2914,"number":2918,"owner":2874,"repository":2919,"state":2907,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### 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.",[2915],{"name":2916,"color":2917},"good first issue","7057ff",83,"cientos","Update all components to use prop deconstruction","2023-07-07T15:21:52Z","https://github.com/Tresjs/cientos/issues/83",0.6861123,{"description":2925,"labels":2926,"number":2918,"owner":2874,"repository":2930,"state":2907,"title":2931,"updated_at":2932,"url":2933,"score":2923},"### Describe the bug\r\n\r\nSSR version of TresCanvas is broken when the project is using `npm` as the package manager.\r\n\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-hzbvpr?file=nuxt.config.ts\r\n\r\n### Steps to reproduce\r\n\r\n1. Run `npm install` and `npm run dev`\r\n2. Click on `/page1` link\r\n3. Check console warning. \r\n\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 14.2.1\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 89.14 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 18.14.1 - ~/.nvm/versions/node/v18.14.1/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.3.1 - ~/.nvm/versions/node/v18.14.1/bin/npm\r\n Browsers:\r\n Brave Browser: 120.1.61.116\r\n Chrome: 121.0.6167.85\r\n Firefox: 121.0.1\r\n Safari: 17.2.1\r\n npmPackages:\r\n @tresjs/cientos: ^3.7.0 => 3.7.0 \r\n @tresjs/nuxt: ^2.1.0 => 2.1.0 \r\n nuxt: ^3.10.0 => 3.10.0 \r\n vite-plugin-glsl: ^1.2.1 => 1.2.1 \r\n vue: ^3.4.15 => 3.4.15 \r\n vue-router: ^4.2.5 => 4.2.5\r\n```\r\n\r\n### Used Package Manager\r\n\r\nnpm, pnpm\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.",[2927],{"name":2928,"color":2929},"bug","d73a4a","nuxt","TresCanvas component is missing template or render function after 3.10.0","2024-02-07T17:58:20Z","https://github.com/Tresjs/nuxt/issues/83",{"description":2935,"labels":2936,"number":2938,"owner":2874,"repository":2885,"state":2907,"title":2939,"updated_at":2940,"url":2941,"score":2942},"**Describe the bug**\r\nPierced props don't seem to work with `a-scale` props\r\n\r\n```vue\r\n \u003CTresBufferGeometry :position=\"[positionArray, 3]\" :a-scale=\"[scaleArray, 1]\" />\r\n```\r\n\r\n```\r\ntres.js:332 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'scale')\r\n at tres.js:332:32\r\n at Array.reduce (\u003Canonymous>)\r\n at patchProp (tres.js:332:15)\r\n at mountElement (runtime-core.esm-bundler.js:5224:21)\r\n at processElement (runtime-core.esm-bundler.js:5196:13)\r\n at patch (runtime-core.esm-bundler.js:5116:21)\r\n at mountChildren (runtime-core.esm-bundler.js:5303:13)\r\n at mountElement (runtime-core.esm-bundler.js:5213:13)\r\n at processElement (runtime-core.esm-bundler.js:5196:13)\r\n at patch (runtime-core.esm-bundler.js:5116:21)\r\n```\r\n\r\n**Expected behavior**\r\nProp `a-scale` shouldn't separate\r\n\r\n**Screenshots**\r\nIf applicable, add screenshots to help explain your problem.\r\n\r\n**System Info**\r\nOutput of `npx envinfo --system --npmPackages '{vite,@tresjs/*, three, vue}' --binaries --browsers` \r\n\r\n```\r\n System:\r\n OS: Linux 5.0 undefined\r\n CPU: (5) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 0 Bytes / 0 Bytes\r\n Shell: 1.0 - /bin/jsh\r\n Binaries:\r\n Node: 16.14.2 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 7.17.0 - /usr/local/bin/npm\r\n npmPackages:\r\n @tresjs/cientos: ^2.0.0-alpha.0 => 2.0.0-alpha.1 \r\n @tresjs/core: ^2.0.0-alpha.0 => 2.0.0-alpha.1 \r\n vite: ^3.2.4 => 3.2.5 \r\n```\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2937],{"name":2928,"color":2929},164,"[v2] - BufferGeometry: Cannot read properties of undefined (reading 'scale')","2023-03-23T18:22:30Z","https://github.com/Tresjs/tres/issues/164",0.7218259,{"description":2944,"labels":2945,"number":2948,"owner":2874,"repository":2885,"state":2907,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Describe the bug\n\n\"Hello, I have two questions:\r\n\r\n1.In the custom rendering, it seems that Vue's unmount hooks, 'onUnmounted' and 'onBeforeUnmount', are not working. I'm using 'onLoop', and when I navigate to another page and then return, it creates a new 'onLoop' which runs alongside the previous one, including the 'onLoop' inside 'useFBO'. Currently, I can only unmount them by using 'onLoop.off' at the root canvas component.\r\n2.I am using version 3.5.1, and I've noticed significant frame drops with touch and other events. I'm not sure if this has been optimized in newer versions.\r\n3.I encounter a problem when using 'Tres' on two different pages. When I navigate from page 1 with 'tres' to page 2 with 'tres', nothing is displayed. However, if I go from page 1 with 'tres' to page 3 without 'tres', and then to page 2 with 'tres', this problem does not occur.\"\r\n\n\n### Reproduction\n\nhttps://github.com/zhangyijie0214/nuxt-tres-test\n\n### Steps to reproduce\n\nnpm install\r\nnpm run dev\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/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.",[2946,2947],{"name":2928,"color":2929},{"name":2871,"color":2872},475,"Routing Jump - Problem Occurring","2024-02-18T01:59:58Z","https://github.com/Tresjs/tres/issues/475",0.7272495,{"description":2954,"labels":2955,"number":2965,"owner":2874,"repository":2885,"state":2907,"title":2966,"updated_at":2967,"url":2968,"score":2969},"Sometimes previews fail for example with StackBlitz on mobile. \r\n\r\nBut we can use [vitepress-plugin-sandpack](https://github.com/jerrywu001/vitepress-plugin-sandpack) instead. It's a [vitepress plugin](https://vitepress-sandbox.js-bridge.com/get-started/introduction.html), and the syntax is concise, use the MD syntax directly.\r\n\r\n**Setup Steps**\r\nhttps://vitepress-sandbox.js-bridge.com/custom-usage/custom.html\r\n\r\n_**and also support**_ [Use snippets](https://vitepress-sandbox.js-bridge.com/basic-usage/snippets.html)\r\n\r\n**Online demo**:\r\nhttps://vitepress-sandbox.js-bridge.com/vite-templates/vite-vue-ts.html\r\n\r\n\r\n\r\n",[2956,2959,2962],{"name":2957,"color":2958},"docs","0075ca",{"name":2960,"color":2961},"dx","1576AD",{"name":2963,"color":2964},"examples","8F2282",261,"May be we could use vitepress-plugin-sandpack instead","2023-12-13T09:18:46Z","https://github.com/Tresjs/tres/issues/261",0.7368067,{"description":2971,"labels":2972,"number":2979,"owner":2874,"repository":2885,"state":2907,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Description\r\n\r\nAs a maintainer of TresJS, I would like to be able to filter devtools cb events by type from dev tools solutions, having a more structured object than just sending the tres state ctx.\r\n\r\nAtm we send the state on `useTresContextProvider` like this:\r\n\r\n```ts\r\nwindow.__TRES__DEVTOOLS__.cb(state)\r\n```\r\n\r\nAlso, I would like to have an API to send actions from the devtools (for example edit properties of objects from the devtools https://github.com/Tresjs/nuxt/issues/73) \r\n\r\n### Suggested solution\r\n\r\nEvents are sent to de `devtools.cb` with the following structure:\r\n\r\n- **type**: string identification of the type of event to be able to filter on the devtools\r\n- **payload**: container for the data to be sent\r\n- **timestamp**: `performance.now` for tracking\r\n\r\n```ts\r\nconst event = {\r\n type: 'tres:ctx',\r\n payload: {\r\n scene,\r\n renderer,\r\n ....\r\n },\r\n timestamp: `performance.now()`\r\n }\r\nwindow.__TRES__DEVTOOLS__.cb(event)\r\n```\r\n\r\nFor the actions we could register an action hook on the core like this\r\n\r\n```ts\r\nwindow.__TRES__DEVTOOLS__.action = (event) => {\r\n if(event.type === 'tres:edit') {\r\n // logic for modifying the scene graph children\r\n }\r\n}\r\n```\r\n\r\nthen from the devtools\r\n\r\n```ts\r\nwindow.__TRES__DEVTOOLS__.action(\r\n {\r\n type: 'tres:edit'\r\n payload: {\r\n object: //obj uuid\r\n property: 'position.x'\r\n value: 2\r\n }\r\n }\r\n)\r\n```\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/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.",[2973,2976],{"name":2974,"color":2975},"v4","7980EA",{"name":2977,"color":2978},"devtools","0AD07B",478,"Devtools events structure and API","2024-05-30T06:42:17Z","https://github.com/Tresjs/tres/issues/478",0.7410519,{"description":2985,"labels":2986,"number":2987,"owner":2874,"repository":2919,"state":2907,"title":2988,"updated_at":2989,"url":2990,"score":2991},"### Describe the bug\r\n\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nimport { TresCanvas } from '@tresjs/core'\r\nimport { OrbitControls, Sky } from '@tresjs/cientos'\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CTresCanvas :tone-mapping-exposure=\"0.25\">\r\n \u003CTresPerspectiveCamera :position=\"[0, 0, 2000]\" />\r\n \u003CSky />\r\n \u003COrbitControls\r\n :enable-pan=\"false\"\r\n :enable-zoom=\"false\"\r\n />\r\n \u003C/TresCanvas>\r\n\u003C/template>\r\n\r\n\r\n### Reproduction\r\n\r\nno\r\n\r\n### Steps to reproduce\r\n\r\n_No response_\r\n\r\n### System Info\r\n\r\n_No response_\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.",[],451,"\u003CSky /> can not utilize","2024-09-03T12:59:10Z","https://github.com/Tresjs/cientos/issues/451",0.74167585,["Reactive",2993],{},["Set"],["ShallowReactive",2996],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fYJ0iiFNoTvgkGb2HtUN_iiKRSjdVpXXkAZJj0JhqUBM":-1},"/Tresjs/post-processing/103"]