\r\n \r\n \u003CTeleport to=\"body\">\r\n \u003Cbutton @click=\"isVisible.value = false\">Hide GLTF\u003C/button>\r\n \u003C/Teleport>\r\n\u003C/template>\r\n```\r\n\r\n### Suggested solution\r\n\r\nEnable usage of portal-vue and/or Teleport. I have tried both, but they both throw different kinds of error:\r\n- portal-vue: \"[portal-vue]: Necessary Injection not found. Make sur you installed the plugin properly.\"\r\n- Teleport: \"Failed to locate Teleport target with selector \"body\" […]\"\r\n\r\nI suspect both errors are caused by the usage of a custom-renderer thus portal-vue/Teleport simply can't access their targets. It's a wild guess, but when moving everything outside of the `\u003CTresCanvas>` context it works just fine.\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\nI guess https://github.com/Tresjs/tres/issues/312 is somewhat of a similar topic\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.",[2870,2873],{"name":2871,"color":2872},"help wanted","008672",{"name":2874,"color":2875},"investigation","D03599",464,"tres","Enable usage of \u003CTeleport>","2024-03-28T11:19:20Z","https://github.com/Tresjs/tres/issues/464",0.7297096,{"description":2883,"labels":2884,"number":2894,"owner":2860,"repository":2877,"state":2862,"title":2895,"updated_at":2896,"url":2897,"score":2898},"### 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.",[2885,2888,2891],{"name":2886,"color":2887},"question","d876e3",{"name":2889,"color":2890},"waiting for author","B145BC",{"name":2892,"color":2893},"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.73041445,{"description":2900,"labels":2901,"number":2908,"owner":2860,"repository":2861,"state":2862,"title":2909,"updated_at":2910,"url":2911,"score":2912},"### Description\n\nAs a developer using TresJS, I would like an equivalent of Three.js's `instancedMesh` to improve performance.\r\n\r\n\n\n### Suggested solution\n\n[Drei's `\u003CInstances />`](https://github.com/pmndrs/drei/blob/514be0d1ff88b43c07cf246da9dca3517ea14d9a/src/core/Instances.tsx#L22)\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.",[2902,2905],{"name":2903,"color":2904},"feature","c2e0c6",{"name":2906,"color":2907},"p2-nice-to-have","D4C5F9",342,"Equivalent of Three.js's `InstancedMesh`","2024-04-02T09:44:50Z","https://github.com/Tresjs/cientos/issues/342",0.7366616,{"description":2914,"labels":2915,"number":2922,"owner":2860,"repository":2877,"state":2862,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### Description\n\nDocs need a little bit of caring for v4\r\nSame for playgrounds\n\n### Suggested solution\n\n- [ ] Remove playground section on https://docs.tresjs.org/guide/#playground\r\n- [x] Remove basic demos from playground https://playground.tresjs.org/\r\n- [ ] Move Events demo from playground to docs (use sandbox)\r\n- [ ] Change naming sandbox to playground\r\n- [ ] Playground is gonna be Showcase/MadeWithTres\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.",[2916,2919],{"name":2917,"color":2918},"docs","0075ca",{"name":2920,"color":2921},"v4","7980EA",494,"Improvements Docs","2024-03-28T11:19:18Z","https://github.com/Tresjs/tres/issues/494",0.7417211,{"description":2928,"labels":2929,"number":2930,"owner":2860,"repository":2861,"state":2862,"title":2931,"updated_at":2932,"url":2933,"score":2934},"### Describe the bug\n\nI've been using the `GLTFModel` component to load my models.\nUnfortunately, I can't programmatically modify or even access them.\nThe documentation provides this example:\n``` \n\u003Cscript setup lang=\"ts\">\nimport { GLTFModel, OrbitControls } from '@tresjs/cientos'\n\nconst modelRef = shallowRef\u003CTHREE.Object3D>()\n\nwatch(modelRef, (model) => {\n // Do something with the model\n model.position.set(0, 0, 0)\n})\n\u003C/script>\n``` \nUnfortunately, the object I receive in return is not a 3D Model. I don't even know what it is.\nIt looks like a `ref` without a `.value`, and I can't access any value.\n\nIt's something like this:\n```\n{\n \"dep\": {\n \"version\": 1,\n \"sc\": 0\n },\n \"__v_isRef\": true,\n \"__v_isShallow\": false,\n \"_rawValue\": {\n \"instance\": {\n \"metadata\": {\n \"version\": 4.6,\n \"type\": \"Object\",\n \"generator\": \"Object3D.toJSON\"\n },\n \"geometries\": [\n```\nI found a better approach, but unfortunately, it produces the same results. Instead of using `watch`, I’m now using the `@resolve` event from `Suspense`, which wraps the `GLTFModel`.\n\nHow can we programmatically modify the object when using the `GLTFModel` component?\n\n### Reproduction\n\nhttps://stackblitz.com/edit/tresjs-basic-tktzn1zk?file=src%2Fcomponents%2FTheExperience.vue\n\n### Steps to reproduce\n\n1. Wait to load up\n2. Check the console logs\n\n### System Info\n\n```shell\nSystem:\n OS: Windows 11 10.0.26100\n CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H\n Memory: 2.57 GB / 15.68 GB\n Binaries:\n Node: 18.20.4 - C:\\Program Files\\nodejs\\node.EXE\n npm: 10.7.0 - C:\\Program Files\\nodejs\\npm.CMD\n Browsers:\n Edge: Chromium (132.0.2957.127)\n Internet Explorer: 11.0.26100.1882\n npmPackages:\n @tresjs/cientos: ^4.1.0 => 4.1.0\n @tresjs/core: ^4.3.2 => 4.3.2\n vite: ^6.0.11 => 6.0.11\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/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.",[],594,"Cant reach the model with `GLTFModel`","2025-03-05T12:22:33Z","https://github.com/Tresjs/cientos/issues/594",0.7486786,{"description":2936,"labels":2937,"number":2941,"owner":2860,"repository":2942,"state":2862,"title":2943,"updated_at":2944,"url":2945,"score":2946},"**Is your feature request related to a problem? Please describe.**\nI find that this example: https://lab.openbloc.fr/droneWorld and his code it's possible to add that to Tres.js?\nI'm not good with PP but would be poerfect for more realistic scenes like my FPS-controls \n\n**Describe the solution you'd like**\nAt the time we move the camera the scene get blur (similar to old cameras or ray casting effects)\n\n**Suggested solution**\nhttps://github.com/blaze33/droneWorld/blob/master/src/postprocessing/MotionBlur.js\n",[2938],{"name":2939,"color":2940},"enhancement","a2eeef",191,"post-processing","It's possible to add a motion blur effect?","2025-03-15T11:51:23Z","https://github.com/Tresjs/post-processing/issues/191",0.753758,{"description":2948,"labels":2949,"number":2950,"owner":2860,"repository":2877,"state":2862,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Description\n\nThis allows to prevent bubbling the events to the dom by using `event.sourceEvent.preventDefault();`\n\n### Suggested solution\n\nAdd event capture true by default, or allow us to add parameters to the listeners: `@click.stop`, `@click.passive`, `@click.capture`, ...\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.",[],939,"Add event capture true by default","2025-02-22T10:19:27Z","https://github.com/Tresjs/tres/issues/939",0.7555059,{"description":2956,"labels":2957,"number":2961,"owner":2860,"repository":2861,"state":2862,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Describe the bug\r\n\r\nFollowing a link with a named anchor to a page including `ScrollControls` does not scroll the resulting page to the anchor.\r\n\r\nE.g., where `http://example.org` is a page including `ScrollControls`, from a new tab, pasting `http://example.org#features` into the address bar and pressing `Return` will load the page, but the page will not be scrolled to the `features` anchor.\r\n\r\n#### Behavior\r\n\r\nOn page load, the page is not scrolled to the named anchor. (offset y = 0)\r\n\r\n#### Expected behavior\r\n\r\nOn page load, the page should be scrolled to the named anchor.\r\n\r\n\r\n### Reproduction\r\n\r\nNo StackBlitz provided. It doesn't appear that the bug is reproducible on StackBlitz' window-in-window setup.\r\n\r\n### Steps to reproduce\r\n\r\n#### Example markup\r\n\r\n```\r\n\u003Ca href=\"#two\">Jump to section 2\u003C/a>\r\n\u003Csection>\u003Ch1>Section 1\u003C/h1>\u003C/section>\r\n\u003Csection>\u003Ch2 id=\"#two\">Section 2\u003C/h2>\u003C/section>\r\n```\r\n\r\n1. In the text editor, insert the example markup into the playground/src/pages/controls/ScrollControlsDemo.vue and save.\r\n2. On the command line, start the playground with `pnpm run playground` if not already running.\r\n3. In the browser, open a new, blank tab.\r\n4. In the browser, paste `http://localhost:5173/controls/scroll-controls#two` in the address bar and hit `Enter`.\r\n\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\r\n Memory: 77.72 MB / 8.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.8.1 - /opt/homebrew/bin/node\r\n npm: 10.1.0 - /opt/homebrew/bin/npm\r\n pnpm: 8.6.5 - /opt/homebrew/bin/pnpm\r\n Browsers:\r\n Chrome: 119.0.6045.199\r\n Safari: 17.0\r\n npmPackages:\r\n @tresjs/core: 3.5.0 => 3.5.0 \r\n @tresjs/eslint-config-vue: ^0.2.1 => 0.2.1 \r\n vite: ^4.5.0 => 5.0.4 \r\n\r\nTested in Chrome, FF, Safari on Mac.\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/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.\r\n\r\nRelated: https://github.com/Tresjs/cientos/pull/288#issuecomment-1838828275",[2958],{"name":2959,"color":2960},"bug","d73a4a",301,"ScrollControls: external links to named anchors don't scroll the page","2024-10-25T08:05:04Z","https://github.com/Tresjs/cientos/issues/301",0.75556606,{"description":2967,"labels":2968,"number":2974,"owner":2860,"repository":2861,"state":2975,"title":2976,"updated_at":2977,"url":2978,"score":2979},"### Description\n\nAs a developer of Tres/Cientos, I would like reorganizations to be simpler.\r\n\r\nMoving a component from one category to another requires a lot of changes (12) to the codebase:\r\n\r\n\u003Cimg width=\"235\" alt=\"Screenshot 2024-04-10 at 18 19 42\" src=\"https://github.com/Tresjs/cientos/assets/20469369/d40dcd09-e622-4ec1-bb08-457b2cf8788a\">\n\n### Suggested solution\n\n## Flatten the file structure\r\n\r\n* Move all components from `/src/core` and `/src/componsables` to `/src`\r\n* Move all components from `/playground/pages/*` to `/playground/pages`\r\n* Move all .md files from `/docs/guide/*` to `/docs/guide`\r\n* Update `index.ts` etc. to reflect the changes\r\n\r\n## Maintain the views/routes\r\n\r\nThe views/routes in the docs and playground would remain unchanged for the user.\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.",[2969,2971],{"name":2874,"color":2970},"D0359D",{"name":2972,"color":2973},"p1-chore","BFD4F2",381,"closed","Reorganize: keep views/routes, flatten file structure?","2024-04-16T15:36:57Z","https://github.com/Tresjs/cientos/issues/381",0.71321356,["Reactive",2981],{},["Set"],["ShallowReactive",2984],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ftbwDczlfxzmf_-mFgIBj21rvmZf5qaWZVtYHNtiWrxk":-1},"/Tresjs/lab/214"]