`","2024-08-21T10:29:21Z","https://github.com/Tresjs/tres/issues/418",0.74229866,{"description":2913,"labels":2914,"number":2922,"owner":2874,"repository":2892,"state":2923,"title":2924,"updated_at":2925,"url":2926,"score":2927},"**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",[2915,2916,2919],{"name":2901,"color":2902},{"name":2917,"color":2918},"good first issue","7057ff",{"name":2920,"color":2921},"help wanted","008672",63,"closed","TransformControls cientos props without set method not updating","2023-01-07T18:45:57Z","https://github.com/Tresjs/tres/issues/63",0.6896895,{"description":2929,"labels":2930,"number":2931,"owner":2874,"repository":2892,"state":2923,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Describe the bug\n\nThis error hapend when I write ` const state = useTres()` or `const { state } = useTres()` In devtools, and the scene is not loaded.\r\nThis is my code (in App.vue):\r\n```\u003Cscript setup lang=\"ts\">\r\nimport { TresCanvas, extend, useTres } from '@tresjs/core';\r\nimport { OrbitControls } from 'three/addons/controls/OrbitControls.js'\r\nimport { watchEffect } from 'vue'\r\n\r\nconst state = useTres()\r\n\r\nlet controls: OrbitControls | null = null\r\n\r\nwatchEffect(()=>{\r\n if (state.renderer && state.camera) {\r\n controls = new OrbitControls(state.camera.value!, state.renderer.value.domElement )\r\n }\r\n})\r\n\r\nextend({OrbitControls})\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CTresCanvas window-size>\r\n \u003CTresPerspectiveCamera />\r\n\r\n \u003CTresScene>\r\n \u003CTresMesh>\r\n \u003CTresBoxGeometry />\r\n \u003CTresMeshNormalMaterial />\r\n \u003C/TresMesh>\r\n \u003C/TresScene>\r\n \u003C/TresCanvas>\r\n\u003C/template>\r\n```\r\n\r\nI did it like in this tutorial: [The tutorial](https://youtu.be/QP3gCY5_dds)\n\n### Reproduction\n\nhttps://stackblitz.com/edit/tresjs-basic-fg1y4w?file=src%2FApp.vue\n\n### Steps to reproduce\n\nAdd \r\n```\r\nimport { useTres } from '@tresjs/core';\r\nconst state = useTres()\r\n```\r\nto your code\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.",[],410,"Uncaught Error: useTresContext must be used together with useTresContextProvider","2023-09-30T07:00:08Z","https://github.com/Tresjs/tres/issues/410",0.6959275,{"description":2937,"labels":2938,"number":2942,"owner":2874,"repository":2892,"state":2923,"title":2943,"updated_at":2944,"url":2945,"score":2946},"**Describe the bug**\r\nUsing tweakpane `useTweakPane` folders on parent and child component overlaps\r\n\r\nI am doing ... What I expect is ... What actually happening is\r\n\r\n**Reproduction**\r\n[Repro](https://stackblitz.com/edit/tresjs-basic-ntxpns?file=src%2Fcomponents%2FTheExperience.vue,src%2Fcomponents%2FThePortal.vue,vite.config.ts,src%2Fshaders%2Ffragment.glsl,src%2FApp.vue)\r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Add ' const { pane } = useTweakPane()` in both parent component and child\r\n2. Add inputs or folders in both\r\n\r\n**Expected behavior**\r\nControls stack instead of overlap\r\n\r\n**Screenshots**\r\n[Video](https://user-images.githubusercontent.com/4699008/208600428-8a982969-845e-4c29-b770-6edfe9d42214.mov)\r\n\r\n**System Info**\r\n\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.2.2 => 1.2.2 \r\n @tresjs/core: ^1.3.2 => 1.3.2 \r\n vite: ^3.2.4 => 3.2.5 \r\n```\r\n\r\n",[2939,2940,2941],{"name":2901,"color":2902},{"name":2917,"color":2918},{"name":2920,"color":2921},50,"Using tweakpane on parent and child component overlaps","2022-12-20T09:47:37Z","https://github.com/Tresjs/tres/issues/50",0.7227956,{"description":2948,"labels":2949,"number":2953,"owner":2874,"repository":2892,"state":2923,"title":2954,"updated_at":2955,"url":2956,"score":2957},"**Is your feature request related to a problem? Please describe.**\r\nIn the current implementation, `useTres` uses a [global state](https://github.com/Tresjs/tres/blob/196606faba790a81dc9b8cdf36133400bcdbb545/src/composables/useTres/index.ts#L100) which has some downsides.\r\n\r\n1. It prevents having multiple canvases on the same page. Fixing this issue might help solving #153 \r\n2. Fixing this issue might help solving #173 \r\n3. Global states are prone to [cross-request state pollution](https://vuejs.org/guide/scaling-up/ssr.html#cross-request-state-pollution) in the SSR context\r\n4. One could put anything inside the state by using [setState](https://github.com/Tresjs/tres/blob/196606faba790a81dc9b8cdf36133400bcdbb545/src/composables/useTres/index.ts#L128), but there would be no representation of it in [TresState](https://github.com/Tresjs/tres/blob/196606faba790a81dc9b8cdf36133400bcdbb545/src/composables/useTres/index.ts#L5). DX suffers from this.\r\n\r\n**Describe the solution you'd like**\r\nWe could restructure `useTres` to make it use the [provide context pattern](https://medium.com/@maoberlehner/context-and-provider-pattern-with-the-vue-3-composition-api-17247eb7b001). `TresCanvas` would be the entity to provide things like renderer, camera and so on (see [TresState](https://github.com/Tresjs/tres/issues/new?assignees=&labels=enhancement&template=feature-request-%F0%9F%AA%90.md)). Any entity being child of `TresCanvas` could use the composable that injects those things.\r\n\r\n**Additional context**\r\nI'm not 100% sure if my proposed solution works. Let's see this issue as a opportunity for a little experiment 😊.\r\n",[2950],{"name":2951,"color":2952},"v2","FEE22E",183,"feat: restructuring useTres using the provide context pattern","2023-04-04T15:47:17Z","https://github.com/Tresjs/tres/issues/183",0.7229672,{"description":2959,"labels":2960,"number":2873,"owner":2874,"repository":2961,"state":2923,"title":2962,"updated_at":2963,"url":2964,"score":2880},"When looking at docs for Bloom I can see empty canvas box with console message saying:\r\n```md\r\nframework.8oxMyIc2.js:1 TypeError: Class constructor ue cannot be invoked without 'new'\r\n at guide_effects_bloom.md.7kCtuEBS.js:1:914\r\n at Object.i [as default] (framework.8oxMyIc2.js:1:16078)\r\n at Proxy.\u003Canonymous> (useRouteDisposal.tyh0ETgK.js:3645:321145)\r\n at ei (framework.8oxMyIc2.js:1:16394)\r\n at Mi.F [as fn] (framework.8oxMyIc2.js:1:49505)\r\n at Mi.run (framework.8oxMyIc2.js:1:4163)\r\n at B.p.update (framework.8oxMyIc2.js:1:49779)\r\n at B (framework.8oxMyIc2.js:1:49805)\r\n at ie (framework.8oxMyIc2.js:1:48650)\r\n at V (framework.8oxMyIc2.js:1:48444)\r\n```\r\n",[],"post-processing","Bloom demo is broken","2024-10-12T11:30:57Z","https://github.com/Tresjs/post-processing/issues/108",{"description":2966,"labels":2967,"number":2873,"owner":2874,"repository":2978,"state":2923,"title":2979,"updated_at":2980,"url":2981,"score":2880},"### Description\n\nResearch of how to apply joints with tres-rapier \n\n### Suggested solution\n\nCould be based on: https://github.com/pmndrs/react-three-rapier?tab=readme-ov-file#joints\r\n\r\nI suggest create a new issue for each joint\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.",[2968,2969,2972,2975],{"name":2920,"color":2921},{"name":2970,"color":2971},"feature","c2e0c6",{"name":2973,"color":2974},"p3-significant","2C78E3",{"name":2976,"color":2977},"v1","5B6B67","rapier","Joints","2025-03-18T09:47:48Z","https://github.com/Tresjs/rapier/issues/108",{"description":2983,"labels":2984,"number":2989,"owner":2874,"repository":2892,"state":2923,"title":2990,"updated_at":2991,"url":2992,"score":2993},"### Description\n\nAs a maintainer of TresJS, I would like to clean up and remove unnecessary code from the core.\n\n### Suggested solution\n\nRemove useSeek utils. Consider something similar in cientos.\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.",[2985,2986],{"name":2973,"color":2974},{"name":2987,"color":2988},"breaking-change","5612D2",984,"Remove `useSeek`","2025-04-18T09:24:24Z","https://github.com/Tresjs/tres/issues/984",0.73292863,["Reactive",2995],{},["Set"],["ShallowReactive",2998],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fU-3Irt8ypraMCOd5VQuPqg5QznmHkR8aD-Vby3ptsPA":-1},"/Tresjs/tres/209"]