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.",[2878,2881],{"name":2879,"color":2880},"investigation","D03599",{"name":2882,"color":2883},"waiting for author","B145BC",102,"XR","VR Style Camera (Aframe implementation or ArrayCamera/StereoCamera from three","2024-08-21T10:45:26Z","https://github.com/Tresjs/XR/issues/102",0.71546394,{"description":2891,"labels":2892,"number":2899,"owner":2868,"repository":2869,"state":2870,"title":2900,"updated_at":2901,"url":2902,"score":2903},"### Description\r\n\r\nAs a developer using TresJS, I want to have a `\u003CPortal>` component that can contain a separate `Scene` and `context`.\r\n\r\n### Suggested solution\r\n\r\nProvide a `\u003CPortal>` component similar to R3F.\r\n\r\n### Requirements\r\n\r\n- [ ] Add override-able pointer to `TresContext` (Also add as prop to TresCanvas: see #581 ); use vanilla `THREE.Vector2`, accept `Vector2` and `UsePointerOptions` as TresCanvas prop\r\n- [ ] Make these fields on `TresContext` swappable and (in some case injectable by the user): scene, camera, cameras, controls, raycaster, eventManager, sizes\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.",[2893,2896],{"name":2894,"color":2895},"p3-significant","2C78E3",{"name":2897,"color":2898},"v5","EFC959",789,"Portal","2025-02-06T09:59:01Z","https://github.com/Tresjs/tres/issues/789",0.7159893,{"description":2905,"labels":2906,"number":2913,"owner":2868,"repository":2869,"state":2870,"title":2914,"updated_at":2915,"url":2916,"score":2917},"## Expected\r\n\r\nIn this `\u003Ctemplate />` ...\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003CTresCanvas>\r\n \u003CTresMesh>\r\n ... \r\n \u003CMyMaterial :prop=\"myProp\" />\r\n \u003C/TresMesh>\r\n \u003C/TresCanvas>\r\n\u003C/template>\r\n```\r\n\r\n... if changing `:prop` changes the material `:key`:\r\n\r\n* the existing material should be removed from the parent.\r\n* the rerendered material should be attached to the parent.\r\n\r\n## Bug\r\n\r\n* The existing material is not removed from the parent.\r\n* The new material is not attached to the parent.\r\n\r\n### What happens instead\r\n\r\n* The existing material remains on the parent.\r\n* A new material is created.\r\n* The new material is not attached.\r\n\r\nChanging the `:prop` again leads to:\r\n\r\n* The new material is disposed.\r\n* Another new material is created.\r\n\r\n## Context\r\n\r\nWorking on updating [`MeshReflectionMaterial` from Cientos](https://github.com/Tresjs/cientos/tree/main/src/core/materials/meshReflectionMaterial). It's based on [this Drei component](https://github.com/pmndrs/drei/blob/master/src/core/MeshReflectorMaterial.tsx). \r\n\r\nBoth components use the `key` prop to force a rerender/recompile. [Drei](https://github.com/pmndrs/drei/blob/47d94d72f70ad23818b993f8b316c132ff04e146/src/core/MeshReflectorMaterial.tsx#L238) | [Cientos](https://github.com/Tresjs/cientos/blob/55ca2bfd4f078ec4633fab2dc40b146adbfac2fd/src/core/materials/meshReflectionMaterial/index.vue#L292)\r\n\r\nUsing the `key` to force rerendering/recompiling currently doesn't work in the Cientos component.\r\n\r\nRerendering/recompiling the material's shader is required here for full reactivity.\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/tresjs-basic-a7wxyh?file=src%2Fcomponents%2FTheExperience.vue\r\n\r\n### Steps to reproduce\r\n\r\nSee Stackblitz.\r\n\r\n### System Info\r\n\r\n```shell\r\nall platforms\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.",[2907,2910],{"name":2908,"color":2909},"pending-triage","97A4FE",{"name":2911,"color":2912},"p2-to-be-discussed","97C1B1",615,"Changing a `\u003CMaterial />`'s `key` prop doesn't attach new material, remove old one","2024-04-17T09:28:14Z","https://github.com/Tresjs/tres/issues/615",0.71804047,{"description":2919,"labels":2920,"number":2921,"owner":2868,"repository":2869,"state":2922,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### Describe the bug\n\nAs shown in the StackBlitz URL example, `onPointerLeave` was activating in version 3.9 and earlier. However, in version 4.0 and later, it is difficult to activate. How can I use `onPointerLeave`?\r\n\r\n```html\r\n \u003CTresMesh\r\n @pointer-enter=\"onPointerEnter\"\r\n @pointer-leave=\"onPointerLeave\"\r\n name=\"box\"\r\n >\r\n \u003CTresBoxGeometry />\r\n \u003CTresMeshBasicMaterial color=\"#006060\" />\r\n \u003C/TresMesh>\r\n```\r\nThis way of using it is not a good practice.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/tresjs-minimal-reproduction-kentgx?file=src%2Fcomponents%2FTheExperience.vue,src%2FApp.vue\n\n### Steps to reproduce\n\n_No response_\n\n### System Info\n\n_No response_\n\n### Used Package Manager\n\nyarn\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.",[],713,"closed","v4.0.1 The `onPointerLeave` function is not activating.","2024-06-06T14:33:34Z","https://github.com/Tresjs/tres/issues/713",0.7003944,{"description":2928,"labels":2929,"number":2939,"owner":2868,"repository":2940,"state":2922,"title":2941,"updated_at":2942,"url":2943,"score":2944},"### Describe the bug\r\n\r\nWhen using OrbitControls, the scene freezes unrecoverably.\r\n\r\n### Reproduction\r\n\r\nhttps://tresjs.org/guide/\r\n\r\n### Steps to reproduce\r\n\r\ndo this:\r\n\r\n\r\n\r\n### System Info\r\n\r\n_No response_\r\n\r\n### Used Package Manager\r\n\r\npnpm\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/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.\r\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[2930,2933,2936],{"name":2931,"color":2932},"bug","d73a4a",{"name":2934,"color":2935},"good first issue","7057ff",{"name":2937,"color":2938},"help wanted","008672",100,"cientos","OrbitControls fail on touch devices","2023-06-27T15:43:33Z","https://github.com/Tresjs/cientos/issues/100",0.70215255,{"description":2946,"labels":2947,"number":2948,"owner":2868,"repository":2869,"state":2922,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Description\r\n\r\nI'm using a v-for to instantiate some TresMeshes (as seen in some of the examples), but I need the v-for to dynamically update, and that doesn't seem to work. Any ideas on how to dynamically update a v-for with tres components?\r\n\r\n### Suggested solution\r\n\r\nNot sure if this is a module thing, but maybe add a v-for to the TresGroup component?\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\nTo clarify, the array being used by the v-for: when it changes, the meshes instantiated by the v-for do not update.\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.",[],413,"v-for please","2023-10-06T22:05:25Z","https://github.com/Tresjs/tres/issues/413",0.70755327,{"description":2954,"labels":2955,"number":2961,"owner":2868,"repository":2869,"state":2922,"title":2962,"updated_at":2963,"url":2964,"score":2965},"**Is your feature request related to a problem? Please describe.**\r\nThere is no type definition for primitive\r\n\r\n",[2956,2957,2958],{"name":2934,"color":2935},{"name":2937,"color":2938},{"name":2959,"color":2960},"dx","1576AD",255,"Primitive type definition","2023-05-21T09:05:02Z","https://github.com/Tresjs/tres/issues/255",0.71062344,{"description":2967,"labels":2968,"number":2973,"owner":2868,"repository":2869,"state":2922,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### 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.",[2969,2972],{"name":2970,"color":2971},"question","d876e3",{"name":2882,"color":2883},310,"Black Canvas in Firefox","2023-06-20T07:13:04Z","https://github.com/Tresjs/tres/issues/310",0.71425366,{"description":2979,"labels":2980,"number":2982,"owner":2868,"repository":2940,"state":2922,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### 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.",[2981],{"name":2934,"color":2935},83,"Update all components to use prop deconstruction","2023-07-07T15:21:52Z","https://github.com/Tresjs/cientos/issues/83",0.7152914,["Reactive",2988],{},["Set"],["ShallowReactive",2991],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ftktnTAFINXGiwz6CL2ft-Sr_HSPZ8sRZHsAU_l0LoiQ":-1},"/Tresjs/nuxt/97"]