\n \u003CVisuTrackBallControls />\n \u003C/TresPerspectiveCamera>\n \u003C/TresCanvas>\n`\n\n[VisuTrackBallControls.vue.txt](https://github.com/user-attachments/files/18799562/VisuTrackBallControls.vue.txt)\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/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.",[],595,"Tresjs","cientos","open","Add TrackballControls to Cientos","2025-02-14T13:18:40Z","https://github.com/Tresjs/cientos/issues/595",0.71604,{"description":3029,"labels":3030,"number":3040,"owner":3021,"repository":3041,"state":3023,"title":3042,"updated_at":3043,"url":3044,"score":3045},"### Description\n\nWebGPU [Three.js r171](https://github.com/mrdoob/three.js/releases) has been released and it’s a major milestone for WebGPU integration with third-party libraries such as React Three Fiber and bundlers like Vite or Next.js. We can now do this with zero configuration:\r\n\r\nThree.js Vanilla Three.js\r\n\r\n```ts\r\nimport * as THREE from 'three'\r\nimport { WebGPURenderer } from 'three/webgpu'\r\n \r\nconst renderer = new WebGPURenderer()\r\n```\r\n\r\nR3F\r\n\r\n```ts\r\nimport { Canvas } from '@react-three/fiber'\r\nimport { WebGPURenderer } from 'three/webgpu'\r\n \r\n\u003CCanvas gl={canvas => new WebGPURenderer({ canvas })}>\r\n```\n\n### Suggested solution\n\nEnable a `renderer` prop to override the renderer, restricted to canvas-based WebGL/WebGPU renderers.\r\n\r\n```vue\r\n\u003Cscript setup>\r\nimport { WebGPURenderer } from 'three/webgpu'\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CTresCanvas :renderer=\"WebGPURenderer\" />\r\n\u003C/template>\r\n```\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.",[3031,3034,3037],{"name":3032,"color":3033},"feature","c2e0c6",{"name":3035,"color":3036},"p3-significant","2C78E3",{"name":3038,"color":3039},"v5","EFC959",883,"tres","WebGPU support","2025-02-06T09:35:42Z","https://github.com/Tresjs/tres/issues/883",0.7412092,{"description":3047,"labels":3048,"number":3058,"owner":3021,"repository":3059,"state":3023,"title":3060,"updated_at":3061,"url":3062,"score":3063},"### Description\n\nThe current implementation is different from R3F, as you can see, the model is treat as a group (I personally prefer this approach) is best performance and cover most of the cases, BUT, not all for some specific cases maybe this is not a viable solution.\r\n\r\n\r\n\r\nR3F handling the models in which each geometry has a different RigidBody/Collider:\r\n\r\n\r\n\r\n\r\nI don't know if this will create future problems for uses cases or the people can workaround them. I don't know if this makes joints cases when models more difficult.\n\n### Suggested solution\n\nProper discussion and research\n\n### Alternative\n\nJust by the record, I like the current approach (but maybe I'm thinking in just low poly games)\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.",[3049,3052,3055],{"name":3050,"color":3051},"help wanted","008672",{"name":3053,"color":3054},"investigation","D03599",{"name":3056,"color":3057},"p2-to-be-discussed","97C1B1",127,"rapier","Handling models? ","2024-09-17T10:20:52Z","https://github.com/Tresjs/rapier/issues/127",0.7548936,{"description":3065,"labels":3066,"number":3070,"owner":3021,"repository":3071,"state":3023,"title":3072,"updated_at":3073,"url":3074,"score":3075},"Inspiration \r\n\r\nhttps://codepen.io/prisoner849/pen/poNXPyv\r\n\r\n\r\n",[3067],{"name":3068,"color":3069},"demo","CAC7AC",84,"lab","Light Bloom example","2023-12-15T13:49:28Z","https://github.com/Tresjs/lab/issues/84",0.7551987,{"description":3077,"labels":3078,"number":3079,"owner":3021,"repository":3041,"state":3023,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Describe the bug\n\nRan into this issue when trying to integrate TresJS in my Astro project. To verify that it wasn't me doing something stupid, I switched to Alvaro's [tres-astro repository](https://github.com/alvarosabu/tres-astro) from the \"How to add 3D to Astro using TresJS\" video. I'm running into the same warning there. I also upgraded to the latest astro in the tres-astro repository, but still seeing the same error. As far as I can tell, the 3D model does show up. \r\n\r\nRemoving the TheExperience component and just trying to use TresCanvas also triggers the same warning. \r\n\r\n```\r\n(index):224 [Vue warn]: onUnmounted is called when there is no active component instance to be associated with. \r\nLifecycle injection APIs can only be used during execution of setup(). \r\nIf you are using async setup(), make sure to register lifecycle hooks before the first await statement.\r\n```\r\n\r\nCall Stack as shown in Edge \r\n| Method | | File|\r\n| --- | --- | --- |\r\n| warn$1 | @ | runtime-core.esm-bundler.js:51|\r\n| injectHook | @ | runtime-core.esm-bundler.js:2808|\r\n| (anonymous) | @ | runtime-core.esm-bundler.js:2815|\r\n| yr | @ | tres.js:831|\r\n| _r | @ | tres.js:889|\r\n| (anonymous) | @ | tres.js:1058|\r\n| (anonymous) | @ | index.mjs:71|\r\n| trigger | @ | index.mjs:71|\r\n| c | @ | tres.js:944|\r\n| setTimeout | | |\r\n| c | @ | tres.js:944|\r\n| wr | @ | tres.js:949|\r\n| yt | @ | tres.js:972|\r\n| br | @ | tres.js:1056|\r\n| (anonymous) | @ | tres.js:1638|\r\n| (anonymous) | @ | runtime-core.esm-bundler.js:2815|\r\n| callWithErrorHandling | @ | runtime-core.esm-bundler.js:199|\r\n| callWithAsyncErrorHandling | @ | runtime-core.esm-bundler.js:206|\r\n| hook.__weh.hook.__weh | @ | runtime-core.esm-bundler.js:2795|\r\n| flushPostFlushCbs | @ | runtime-core.esm-bundler.js:385|\r\n| hydrate2 | @ | runtime-core.esm-bundler.js:1675|\r\n| mount | @ | runtime-core.esm-bundler.js:3939|\r\n| app.mount | @ | runtime-dom.esm-bundler.js:1786|\r\n| (anonymous) | @ | client.js:45|\r\n| await in (anonymous) | | |\r\n| (anonymous) | @ | (index):224|\r\n| e | @ | (index):224|\r\n| await in e | | |\r\n| start | @ | (index):224|\r\n| childrenConnectedCallback | @ | (index):224|\r\n| await in childrenConnectedCallback | | |\r\n| e | @ | (index):224|\r\n| (anonymous) | @ | (index):224|\n\n### Reproduction\n\nhttps://github.com/alvarosabu/tres-astro\n\n### Steps to reproduce\n\nClone the repository \r\nrm the package-lock.json file \r\nnpm install\r\nnpm run dev\n\n### System Info\n\n```shell\nnpx envinfo --system --npmPackages '{vite,@tresjs/*,three,vue,@astrojs/*}' --binaries\r\n --browsers --npmGlobalPackages '{astro}'\r\n\r\n System:\r\n OS: Windows 11 10.0.22631\r\n CPU: (28) x64 Intel(R) Core(TM) i7-14700K\r\n Memory: 40.84 GB / 63.77 GB\r\n Binaries:\r\n Node: 20.11.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - C:\\Program Files (x86)\\Yarn\\bin\\yarn.CMD\r\n npm: 10.4.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Chromium (127.0.2651.74)\r\n Internet Explorer: 11.0.22621.3527\r\n npmPackages:\r\n @astrojs/mdx: ^3.1.4 => 3.1.9\r\n @astrojs/rss: ^4.0.7 => 4.0.10\r\n @astrojs/sitemap: ^3.1.6 => 3.2.1\r\n @astrojs/vue: ^4.5.0 => 4.5.3\r\n @tresjs/cientos: ^4.0.0 => 4.0.3\r\n @tresjs/core: ^4.2.7 => 4.3.1\r\n three: ^0.167.1 => 0.167.1\r\n vue: ^3.4.38 => 3.5.13\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.",[],886,"Using TresJS with Astro : [Vue warn]: onUnmounted is called when there is no active component instance to be associated with...","2024-12-20T10:08:26Z","https://github.com/Tresjs/tres/issues/886",0.75885826,{"description":3085,"labels":3086,"number":3087,"owner":3021,"repository":3022,"state":3023,"title":3088,"updated_at":3089,"url":3090,"score":3091},"### Describe the bug\n\nI am using `\u003CHtml>` to wrap elements containing template refs, but these refs are not correctly initialized. As a result, the references to the slotted elements are inaccessible within the component's lifecycle.\n\nPerhaps related to issues: [464](https://github.com/Tresjs/tres/issues/464) — [312](https://github.com/Tresjs/tres/issues/312)\n\n### Reproduction\n\nhttps://play.tresjs.org/#eNqdVW1v2zYQ/iucgiEuJkuykxSb5xSZ3XbtsKxBG2Afqn5gpIvFhCIJkvLLAv/3HSnLlpLWdWoLhnkvzz13vDs9BNcazB9KRfMKglEwNplmyhIDtlKEUzE7TwNr0uBVKlippLbkgWi4DYkUl7ISFvKQLKjNCrImt1qW5BiBjn9vWbsAUyrm1GxNLizK7kycSd21/aBvmJ1KYbXkJiTvbMmfOjEQVhrnl4pMCmOJoprONFUf4ZacO3o9UXH+whlsafZ6L8j5K/KQCkKcl+QQcTnrHZe1/jhsw0RzyitAhLVH8Rn2WvqQfAvOm+4BG8d1ibGgeLBQKk4t4ImQcatUCyZyuegb9h+QjAPV/UxyqfE2jn4dvp5Mz/yVEPx4ryvQRkFm2RymtARNyUhJwyyTAl0+/xYS93xJAxI3bp1a78QO7RJM0QXoD0OCT+IQRlpa2iiSkFxSW0RX72vtBqZJRgr4E2QJVq/IiOqZcT6DkAyis5CctPm0Ql9LvDUsimaUY3Efpb2jGjcO+7kjRfe4YBk1tm8KiqXthp3I5Vd4OpLNz7O4nr513x/gijV2pX5ayU+qAL2r5cFM3k4mycmkwx19/GBlOEegW2JUKDc96NfqXmTyDjiX5F+pef7TOFZtpNhB7U3yNdOuMaWg/G82K+yTy8F8T31fMeQjULVCxSAadu9rk0Adox4SFIzj1gTh0dgVd38LZBWm4kbmq3pGS7xUJkYkwbVBcDjznIlZcyzAERuRQZL87AULlttie16n4ogqVQN9x5aQG5rdzzQulbwe2RE5ShIXB2Fw+D3BIAzqndcvqYrujBS4ez18ulHgyh3VAZ2svTCdIg0Ka5UZxXGWC/TPgbO5jgTYWKgybptfnEbDaBjnzNjYidE6DbA0j4Drpfoc7NoD4ZMo6QtY2miwi7LRdoPZBdB7RcUhKWxtfYAGuRFGJXM+bexCw0G4zu4CEV8i7fgXMGW7GvjuqgwcXOaW+cUgic4QEdc2LKOyW+SNHTayhvwZwLXDPmg07OdQsgNAG1OX/Gn0Mubspg3pELFD19ia1uAb7ZbNHjVmJkvFOOgPyg1vt0EpLojFX15mdQVbflkB2f1X5HdmWVO+wmYBPcdy764SRxVsrX7z6R/srJaylHnFN5fzDeVHwLdx5TjWZhMcRaTdsvNs3/s5wy1wbd4s/eLZJNUhalcKvPRzs/S2vVYLvvjCeXt/HdM9VdpldhKdbAu+/h+NgxeG\n\n### Steps to reproduce\n\n1. Use the `\u003CHtml>` component to wrap elements containing template refs.\n2. Observe that these refs are not initialized (console.log inside onMounted shows them as undefined).\n3. Any logic relying on these refs does not work as expected.\n\n```vue\n\u003Ctemplate>\n \u003CHtml>\n \u003Cdiv ref=\"container\">Some Content\u003C/div>\n \u003C/Html>\n\u003C/template>\n\n\u003Cscript setup>\nimport { Html } from '@tresjs/cientos'\nimport { ref, onMounted, watch } from 'vue';\n\nconst container = ref(null);\n\nonMounted(() => {\n console.log(container.value); // Expected: DOM Element | Actual: null\n});\n\nwatch(container, () => {\n console.log('watch', container.value); // Expected: DOM Element | Actual: The log never appears\n})\n\u003C/script>\n```\n\n### Summary of Solutions\n\nParent refs don't get assigned when using `createVNode()` and `render()` because the content ends up outside the parent's render tree. Here's a quick breakdown:\n\n#### What Doesn't Work\n- **Direct `\u003CTeleport>`** \n The custom TresJS renderer can't find the target in the standard DOM.\n\n- **Manual `createVNode()` + `render()`** \n This creates a new root outside the parent's render tree, so refs declared in the template aren't assigned.\n\n#### What Might Work ?\n- **Global Store (Pinia/Vuex)** \n You could set up a tunnel to share content via a global store, but that adds an external dependency we’d rather avoid.\n\n- **Tunnel via Provide/Inject (In/Out)** \n Use provide/inject to share a reactive state (like an array of VNodes) between an \"In\" component (capturing the content) and an \"Out\" component (rendering it in the standard DOM). This should preserve reactivity and proper ref assignment without extra dependencies. This [message](https://github.com/Tresjs/tres/issues/312#issuecomment-2302950778) in [issue 312](https://github.com/Tresjs/tres/issues/312) talked about this method. \n\n\n### System Info\n\n```shell\nSystem:\n OS: macOS 15.1.1\n CPU: (14) arm64 Apple M4 Pro\n Memory: 116.89 MB / 24.00 GB\n Shell: 5.9 - /bin/zsh\n Binaries:\n Node: 22.11.0 - ~/.nvm/versions/node/v22.11.0/bin/node\n npm: 11.0.0 - ~/.nvm/versions/node/v22.11.0/bin/npm\n pnpm: 9.14.4 - ~/.nvm/versions/node/v22.11.0/bin/pnpm\n Browsers:\n Chrome: 133.0.6943.55\n Safari: 18.1.1\n```\n\n### Used Package Manager\n\npnpm\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.",[],596,"Template refs inside `\u003CHtml>` component are not working","2025-02-17T20:39:49Z","https://github.com/Tresjs/cientos/issues/596",0.7590431,{"description":3093,"labels":3094,"number":3101,"owner":3021,"repository":3041,"state":3023,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Describe the bug\r\n\r\nDue to the debounced ref introduced in #512, the canvas only renders once the resize animation has finished.\r\n\r\nHow it's supposed to work\r\n\r\n\r\nIt can be fixed by moving renderer size update and the camera projection matrix update to before rendering or using useFps composable from vueuse to dynamically calculate debounceTime\r\n\r\n### Reproduction\r\n\r\nMonitor with refresh rate above 100 hz needed\r\n\r\nhttps://stackblitz.com/edit/stackblitz-starters-jtmew9?file=src%2FApp.vue\r\n### Steps to reproduce\r\n\r\nHave container of TresCanvas resize continuously. \r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)\r\n CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor\r\n Memory: 12.28 GB / 15.58 GB\r\n Container: Yes\r\n Shell: 5.8.1 - /usr/bin/zsh\r\n Binaries:\r\n Node: 22.8.0 - ~/.asdf/installs/nodejs/22.8.0/bin/node\r\n npm: 10.8.2 - ~/.asdf/plugins/nodejs/shims/npm\r\n pnpm: 9.9.0 - ~/.local/share/pnpm/pnpm\r\n npmPackages:\r\n @tresjs/cientos: ^4.0.2 => 4.0.2 \r\n @tresjs/nuxt: ^3.0.7 => 3.0.7\r\n```\r\n\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/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.",[3095,3098],{"name":3096,"color":3097},"bug","d73a4a",{"name":3099,"color":3100},"p3-minor-bug","F28C37",848,"Render issue with continuous resize animation","2024-10-18T20:46:48Z","https://github.com/Tresjs/tres/issues/848",0.75959635,{"description":3107,"labels":3108,"number":3118,"owner":3021,"repository":3041,"state":3023,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Describe the bug\n\nI tried writing this code in `tresjs v 4.0.2`\r\n```vue \u003CTresGroup>\r\n \u003CTresPerspectiveCamera :position=\"[5, 5, 5]\" />\r\n \u003COrbitControls />\r\n \u003CTresAmbientLight :intensity=\"0.5\" color=\"red\" />\r\n \u003CTresMesh ref=\"boxRef\" :position=\"[0, 2, 0]\">\r\n \u003CTresBoxGeometry :args=\"[1, 1, 1]\" />\r\n \u003CTresMeshNormalMaterial />\r\n \u003C/TresMesh>\r\n \u003CTresDirectionalLight :position=\"[0, 2, 4]\" :intensity=\"1\" cast-shadow />\r\n \u003CTresAxesHelper />\r\n \u003CTresGridHelper :args=\"[10, 10, 0x444444, 'teal']\" />\r\n \u003C/TresGroup>\r\n````\r\nThen I got this\r\n\r\n\r\n**However, it can run correctly in `v3.9.0`**\r\n\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/hexianWeb/starter\n\n### Steps to reproduce\n\n_No response_\n\n### System Info\n\n_No response_\n\n### Used Package Manager\n\npnpm\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.",[3109,3112,3115],{"name":3110,"color":3111},"question","d876e3",{"name":3113,"color":3114},"waiting for author","B145BC",{"name":3116,"color":3117},"p2-edge-case","ABCC40",727,"`Camera` wrapped by `TresGroup` cannot be used properly after `version 4.0`","2024-06-15T11:45:11Z","https://github.com/Tresjs/tres/issues/727",0.762317,{"description":3124,"labels":3125,"number":3126,"owner":3021,"repository":3041,"state":3023,"title":3127,"updated_at":3128,"url":3129,"score":3130},"### Describe the bug\n\ni have made a clean nuxt 3.15.4 installation, with three.js 0.174.0, @tresjs/core 4.3.3 and @tresjs/nuxt 3.0.8, in firefox.\nin the console, i have these warnings:\n```\nMouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. [tres.js:695:6](http://localhost:3000/_nuxt/node_modules/@tresjs/core/dist/tres.js)\nMouseEvent.mozInputSource is deprecated. Use PointerEvent.pointerType instead. [tres.js:695:6](http://localhost:3000/_nuxt/node_modules/@tresjs/core/dist/tres.js)\n```\nthis probably suggests that tresjs uses older browser mouse events. i have opened the same nuxt instance in chrome and it didnt give any warnings, so this is definitely an firefox-only issue.\n\nuser agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:135.0) Gecko/20100101 Firefox/135.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/tresjs-minimal-reproduction\n\n### Steps to reproduce\n\nstackblitz should run in firefox browser, on chrome this warning doesnt exist\n\n### System Info\n\n```shell\nSystem:\n OS: Windows 11 10.0.26100\n CPU: (12) x64 AMD Ryzen 5 7535HS with Radeon Graphics\n Memory: 4.49 GB / 23.32 GB\n Binaries:\n Node: 23.6.1 - C:\\nvm4w\\nodejs\\node.EXE\n npm: 10.9.2 - C:\\nvm4w\\nodejs\\npm.CMD\n pnpm: 10.2.0 - C:\\nvm4w\\nodejs\\pnpm.CMD\n Browsers:\n Edge: Chromium (132.0.2957.140)\n Internet Explorer: 11.0.26100.1882\n npmPackages:\n @tresjs/core: ^4.3.3 => 4.3.3\n @tresjs/nuxt: ^3.0.8 => 3.0.8\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.",[],952,"Firefox warning: \"MouseEvent.mozPressure\" and \"MouseEvent.mozInputSource\" are deprecated","2025-03-02T20:32:14Z","https://github.com/Tresjs/tres/issues/952",0.7680384,{"description":3132,"labels":3133,"number":3136,"owner":3021,"repository":3041,"state":3023,"title":3137,"updated_at":3138,"url":3139,"score":3140},"### 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.",[3134,3135],{"name":3035,"color":3036},{"name":3038,"color":3039},789,"Portal","2025-02-06T09:59:01Z","https://github.com/Tresjs/tres/issues/789",0.768934,["Reactive",3142],{},["Set"],["ShallowReactive",3145],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f14W_K2288tlOsW5MdJAzTVYSzEDAE8WRwDgb-1SQZIs":-1},"/Tresjs/tres/450"]