\r\n \u003CTresMeshNormalMaterial />\r\n \u003CHtml\r\n center\r\n transform\r\n :distance-factor=\"4\"\r\n :position=\"[0, 0, 0.65]\"\r\n :scale=\"[0.75, 0.75, 0.75]\"\r\n >\r\n \u003Cdiv>\r\n \u003Cp>This should not scroll\u003C/p>\r\n \u003C/div>\r\n \u003C/Html>\r\n \u003C/TresMesh>\r\n```\r\nI expect the first element to scroll, and the second to stay.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)\r\n CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz\r\n Memory: 3.82 GB / 11.69 GB\r\n Container: Yes\r\n Shell: 3.6.1 - /usr/bin/fish\r\n Binaries:\r\n Node: 21.5.0 - ~/.local/share/nvm/v21.5.0/bin/node\r\n Yarn: 1.22.19 - /usr/bin/yarn\r\n npm: 10.2.4 - ~/.local/share/nvm/v21.5.0/bin/npm\r\n pnpm: 8.14.1 - ~/.local/share/pnpm/pnpm\r\n bun: 1.0.7 - ~/.bun/bin/bun\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.",[2890,2893],{"name":2891,"color":2892},"pending-triage","97A4FE",{"name":2894,"color":2895},"waiting for author","B145BC",507,"tres","Native html scroll and @tresjs/cientos Html component behaviour","2024-03-30T15:37:07Z","https://github.com/Tresjs/tres/issues/507",0.76739377,{"description":2903,"labels":2904,"number":2870,"owner":2871,"repository":2911,"state":2912,"title":2913,"updated_at":2914,"url":2915,"score":2877},"### Description\n\nI would like to have some demos in this repo, applying basic forces \n\n### Suggested solution\n\n_No response_\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.",[2905,2908],{"name":2906,"color":2907},"good first issue","7057ff",{"name":2909,"color":2910},"feature","c2e0c6","rapier","closed","Demos: apply forces","2024-09-12T13:49:59Z","https://github.com/Tresjs/rapier/issues/104",{"description":2917,"labels":2918,"number":2923,"owner":2871,"repository":2897,"state":2912,"title":2924,"updated_at":2925,"url":2926,"score":2927},"**Describe the bug**\r\nSince we are using a Custom Renderer, the main instances of Vue don't recognize the Tres components and throw these annoying warnings that will confuse users.\r\n\r\nOne way around this is to add this to the `vite.config.ts`:\r\n\r\n```\r\nplugins: [vue({\r\n template: {\r\n compilerOptions: {\r\n isCustomElement: tag => tag.startsWith('Tres') && tag !== 'TresCanvas',\r\n },\r\n },\r\n })],\r\n```\r\nBut that's not ideal.\r\n\r\n**Expected behavior**\r\nNo warnings\r\n\r\n**Screenshots**\r\n\u003Cimg width=\"803\" alt=\"Screenshot 2023-03-23 at 06 15 08\" src=\"https://user-images.githubusercontent.com/4699008/227110134-44644ecb-367b-4fe4-b071-8e3b645611ce.png\">\r\n\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**Additional context**\r\nAdd any other context about the problem here.\r\n",[2919,2922],{"name":2920,"color":2921},"bug","d73a4a",{"name":2891,"color":2892},162,"[v2] - Failed to resolve component warnings","2023-11-23T18:35:20Z","https://github.com/Tresjs/tres/issues/162",0.73486257,{"description":2929,"labels":2930,"number":2938,"owner":2871,"repository":2897,"state":2912,"title":2939,"updated_at":2940,"url":2941,"score":2942},"**Describe the bug**\r\nSeems since the update to v2 some demos with shaders are glitchy. We should find out why.\r\n\r\n\r\n**Reproduction**\r\nv2 https://playground.tresjs.org/experiments/portal-journey\r\nv1 https://stackblitz.com/edit/tresjs-portal-threejs-journey?file=README.md\r\n\r\n**Expected behavior**\r\nv2 fireflies work as v1\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: macOS 13.2.1\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 93.83 MB / 16.00 GB\r\n Shell: 5.8.1 - /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: 111.1.49.128\r\n Chrome: 111.0.5563.110\r\n Safari: 16.3\r\n npmPackages:\r\n @tresjs/cientos: 2.0.0-alpha.5 => 2.0.0-alpha.5 \r\n @tresjs/core: 2.0.0-alpha.4 => 2.0.0-alpha.4 \r\n```\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2931,2932,2935],{"name":2920,"color":2921},{"name":2933,"color":2934},"help wanted","008672",{"name":2936,"color":2937},"v2","FEE22E",177,"[v2] - Shaders are not working 100%","2023-03-31T09:13:55Z","https://github.com/Tresjs/tres/issues/177",0.7408899,{"description":2944,"labels":2945,"number":2949,"owner":2871,"repository":2897,"state":2912,"title":2950,"updated_at":2951,"url":2952,"score":2953},"**Describe the bug**\r\nWhen use `useTres` composable inside a sub-component to obtain the state, this state never gets updated. Curiously it does get updated when accessed from `cientos` or any other package\r\n\r\n**Reproduction**\r\nPlease provide a link using this template on [Stackblitz](https://stackblitz.com/edit/tresjs-basic-trxx6f?file=src/components/TheSphere.vue) \r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to reproduction link\r\n2. Open console.\r\n4. See that the console inside of the sphere gives a default state with mostly all undefined, but the console on the parent using templateRef `context` is updated with the correct value of state\r\n\r\n**Expected behavior**\r\nState using `useTres` should provide correct updated state\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: (3) 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: 9.4.2 - /usr/local/bin/npm\r\n npmPackages:\r\n @tresjs/cientos: ^2.0.0-beta.3 => 2.0.0-beta.3 \r\n @tresjs/core: ^2.0.0-beta.9 => 2.0.0-beta.9 \r\n vite: ^4.2.2 => 4.2.2 \r\n```\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2946,2947,2948],{"name":2920,"color":2921},{"name":2933,"color":2934},{"name":2936,"color":2937},209,"useTres doesnt get updated on subcomponent","2023-04-19T08:01:20Z","https://github.com/Tresjs/tres/issues/209",0.743108,{"description":2955,"labels":2956,"number":2964,"owner":2871,"repository":2897,"state":2912,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Describe the bug\n\nWhen selecting an object, the highlight mesh is counted on the memory consumption badge\r\n\r\nWe should filter it\r\nhttps://github.com/Tresjs/tres/assets/4699008/30f52b06-5295-4a57-b05b-19ceaf11c8ac\r\n\r\n\n\n### Reproduction\n\nNot needed \n\n### Steps to reproduce\n\n1. Open vue devtools\r\n2. Select and instance and check the badge of memory consuption\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 14.2.1\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 93.17 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.139\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/core: ^3.7.0 => 3.7.0 \r\n @tresjs/eslint-config-vue: ^0.2.1 => 0.2.1 \r\n @tresjs/leches: ^0.14.0 => 0.14.0 \r\n @types/three: ^0.161.2 => 0.161.2 \r\n @vitejs/plugin-vue: ^5.0.3 => 5.0.3 \r\n three: ^0.161.0 => 0.161.0 \r\n typescript: ^5.3.3 => 5.3.3 \r\n vite: ^5.0.12 => 5.0.12 \r\n vite-plugin-glsl: ^1.2.1 => 1.2.1 \r\n vue: ^3.4.15 => 3.4.15 \r\n vue-tsc: ^1.8.27 => 1.8.27\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.",[2957,2958,2961],{"name":2920,"color":2921},{"name":2959,"color":2960},"devtools","0AD07B",{"name":2962,"color":2963},"p3-minor-bug","F28C37",533,"[Devtools]- Memory badge is counting the highlighter component","2024-07-26T11:22:17Z","https://github.com/Tresjs/tres/issues/533",0.7438929,{"description":2970,"labels":2971,"number":2975,"owner":2871,"repository":2897,"state":2912,"title":2976,"updated_at":2977,"url":2978,"score":2979},"**Describe the bug**\r\nThe following props are not being properly updated:\r\n\r\n- `enabled`.\r\n- `showX`, `showY`, `showZ`\r\n- `axis`.\r\n\r\n**Reproduction**\r\n[Stackblitz](https://stackblitz.com/edit/tresjs-transform-controls?file=src%2Fcomponents%2FTheExperience.vue,package.json) \r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to[ '...'](https://stackblitz.com/edit/tresjs-transform-controls?file=src%2Fcomponents%2FTheExperience.vue,package.json)\r\n2. Play with props on the panel top right\r\n\r\n**Expected behavior**\r\nAll props work\r\n\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: (8) 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: ^1.3.0 => 1.3.0 \r\n @tresjs/core: ^1.4.0 => 1.4.0 \r\n vite: ^3.2.4 => 3.2.4 \r\n```\r\n\r\n**Additional context**\r\nMost probably is because this properties doesn't use a `set` function\r\n",[2972,2973,2974],{"name":2920,"color":2921},{"name":2906,"color":2907},{"name":2933,"color":2934},63,"TransformControls cientos props without set method not updating","2023-01-07T18:45:57Z","https://github.com/Tresjs/tres/issues/63",0.74501693,{"description":2981,"labels":2982,"number":1229,"owner":2871,"repository":2984,"state":2912,"title":2985,"updated_at":2986,"url":2987,"score":2988},"**Describe the bug**\r\nSetting `position` on GLTFModel doesn't seem to work. Must probably forgot to pass down the props to the mesh\r\n\r\n**Reproduction**\r\nPlease provide a link using this template on [Stackblitz](https://stackblitz.com/edit/tresjs-basic?file=README.md) \r\n\r\n[Repro](https://stackblitz.com/edit/tresjs-gltf-model?file=src%2Fcomponents%2FTheExperience.vue)\r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to 'Experience.vue'\r\n2. Add `position` to the \u003CGTLFModel />\r\n\r\n**Expected behavior**\r\nThe model should translate to the provided position\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: (8) 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: ^1.0.0 => 1.0.0 \r\n @tresjs/core: ^1.0.0 => 1.0.0 \r\n vite: ^3.2.4 => 3.2.4 \r\n```\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2983],{"name":2920,"color":2921},"cientos","GLTFModel component doesn't inherit props ","2023-05-04T07:12:27Z","https://github.com/Tresjs/cientos/issues/6",0.746802,["Reactive",2990],{},["Set"],["ShallowReactive",2993],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fjMvQK93bg5eAQN5nkohXSDlvIGgdaZIZcosBFpF9kq8":-1},"/Tresjs/tres/50"]