\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",[3038],{"name":3019,"color":3020},"cientos","GLTFModel component doesn't inherit props ","2023-05-04T07:12:27Z","https://github.com/Tresjs/cientos/issues/6",0.7047444,{"description":3045,"labels":3046,"number":1225,"owner":3028,"repository":3047,"state":3030,"title":3048,"updated_at":3049,"url":3050,"score":3043},"### Describe the bug\r\n\r\nWhen used on a clean nuxt app, this error is prompted\r\n\r\n```bash\r\nImporting directly from module entry points is not allowed. \r\n[importing @tresjs/nuxt from virtual:nuxt:/Users/alvarosabu/Projects/tres/playground/.nuxt/plugins/client.mjs]\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-bnznqb?file=nuxt.config.ts,app.vue\r\n\r\n### Steps to reproduce\r\n\r\nRun `npm i` and then `npm run dev`\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\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: 9.4.2 - /usr/local/bin/npm\r\n npmPackages:\r\n @tresjs/cientos: ^2.1.3 => 2.1.3 \r\n @tresjs/nuxt: ^1.0.0-alpha.0 => 1.0.0-alpha.0 \r\n nuxt: ^3.5.2 => 3.5.3 \r\n three: ^0.153.0 => 0.153.0 \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.",[],"nuxt","Importing directly from module entry points is not allowed. ","2023-06-16T12:11:07Z","https://github.com/Tresjs/nuxt/issues/6",{"description":3052,"labels":3053,"number":3054,"owner":3028,"repository":3029,"state":3030,"title":3055,"updated_at":3056,"url":3057,"score":3058},"**Is your feature request related to a problem? Please describe.**\r\nRight now `\u003CTresCanvas :alpha=\"true\" />` will not change if `alpha` is updated using `tweakpane` for example.\r\n\r\n**Describe the solution you'd like**\r\nWatch mutable props and use the correct **setMethod**, for example:\r\n\r\nA change on `clear-color` prop would trigger a `renderer.value.setClearColor(props.clearColor)` \r\n\r\n**Suggested solution**\r\nCreate a utility do dynamically generate the setMethod based on the name of the prop\r\n\r\n**Docs**\r\n\r\nhttps://threejs.org/docs/?q=we#api/en/renderers/WebGLRenderer\r\n\r\n",[],52,"Update renderer TresCanvas via props using set methods","2022-12-21T11:12:42Z","https://github.com/Tresjs/tres/issues/52",0.7143982,{"description":3060,"labels":3061,"number":3065,"owner":3028,"repository":3029,"state":3030,"title":3066,"updated_at":3067,"url":3068,"score":3069},"**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",[3062,3063,3064],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},177,"[v2] - Shaders are not working 100%","2023-03-31T09:13:55Z","https://github.com/Tresjs/tres/issues/177",0.7154235,{"description":3071,"labels":3072,"number":3074,"owner":3028,"repository":3029,"state":3030,"title":3075,"updated_at":3076,"url":3077,"score":3078},"**Describe the bug**\r\nThe library still glitches in responsiveness, especially regarding models, they get distorted aspect ratio, probably the canvas.\r\n\r\n**Reproduction**\r\nRe-scale a scene\r\n\r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to any scene\r\n2. Resize until very very small\r\n\r\n**Expected behavior**\r\nRe-scaling doesn't affect objects or the camera aspect ratio\r\n\r\n**Screenshots**\r\n\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: macOS 13.2.1\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 74.72 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: 110.1.48.164\r\n Chrome: 110.0.5481.177\r\n Safari: 16.3\r\n npmPackages:\r\n @tresjs/cientos: ^1.7.0 => 1.7.0 \r\n @tresjs/core: ^1.7.0 => 1.7.0 \r\n vite: ^4.1.0 => 4.1.4 \r\n```\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[3073],{"name":3019,"color":3020},127,"Scene doesn't scale properly","2023-02-27T19:56:06Z","https://github.com/Tresjs/tres/issues/127",0.7217712,{"description":3080,"labels":3081,"number":3083,"owner":3028,"repository":3084,"state":3030,"title":3085,"updated_at":3086,"url":3087,"score":3088},"**Describe the bug**\r\nA clear and concise description of what the bug is. If you intend to submit a PR for this issue, tell us in the description. Thanks!\r\n\r\nHi! Fist of all, What a great library! I'm playing with it, and so far... I LOVE IT! now... to the error, I am currently trying to use the post-processing package on a scene and I get the following error when I use it:\r\n\r\n\r\n\r\n**Reproduction**\r\nThis same happens whenever you check the examples:\r\nhttps://playground.tresjs.org/experiments/nuxt-stones\r\n\r\n\r\n\r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Just adding the EffectComposer with a default bloom effect.\r\n\r\n**Expected behavior**\r\nFor the effect composer component to work\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\nSystem:\r\n OS: macOS 13.4.1\r\n CPU: (8) arm64 Apple M1\r\n Memory: 323.22 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node\r\n npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm\r\n Browsers:\r\n Chrome: 116.0.5845.110\r\n Safari: 16.5.2\r\n npmPackages:\r\n @tresjs/cientos: ^3.1.0 => 3.1.0 \r\n @tresjs/core: ^3.1.0 => 3.1.0 \r\n @tresjs/post-processing: ^0.3.0 => 0.3.0 \r\n vite: ^2.8.0 => 2.9.16 \r\n```\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[3082],{"name":3019,"color":3020},49,"post-processing","Cannot read properties of undefined (reading 'canvas')","2023-10-19T15:07:15Z","https://github.com/Tresjs/post-processing/issues/49",0.7256848,{"description":3090,"labels":3091,"number":1913,"owner":3028,"repository":3084,"state":3030,"title":3095,"updated_at":3096,"url":3097,"score":3098},"**Is your feature request related to a problem? Please describe.**\r\nAs of now, effects are typescript `.ts` files with `defineComponent`.\r\n\r\n```ts\r\nexport const Glitch = defineComponent\u003CGlitchProps>({\r\n name: 'Glitch',\r\n props: [\r\n 'delay',\r\n 'duration',\r\n 'strength',\r\n 'mode',\r\n 'active',\r\n 'ratio',\r\n 'columns',\r\n 'chromaticAberrationOffset',\r\n 'peturbationMap',\r\n 'dtSize',\r\n ] as unknown as undefined,\r\n\r\n async setup(props, { expose }) {\r\n const { state } = useCore()\r\n const composer = inject\u003Cany>('effectComposer')\r\n const pass = ref\u003CEffectPass | null>(null)\r\n\r\n expose({ getPass: () => pass.value })\r\n\r\n watchEffect(() => {\r\n if (state.camera && composer && composer.value) {\r\n pass.value = new EffectPass(unref(state.camera), new GlitchEffect(props))\r\n composer.value?.addPass(toRaw(pass.value))\r\n }\r\n })\r\n\r\n watch(\r\n () => props.active,\r\n value => {\r\n if (pass.value) {\r\n pass.value.enabled = value as boolean\r\n }\r\n },\r\n )\r\n\r\n return () => {\r\n pass\r\n }\r\n },\r\n})\r\n\r\n```\r\n\r\n**Describe the solution you'd like**\r\n\r\nUse a similar approach as cientos and use vue SFC components \r\n\r\n",[3092],{"name":3093,"color":3094},"enhancement","a2eeef","Refactor Effects to .vue files","2023-06-23T16:06:50Z","https://github.com/Tresjs/post-processing/issues/23",0.7271987,{"description":3100,"labels":3101,"number":1913,"owner":3028,"repository":3029,"state":3030,"title":3106,"updated_at":3107,"url":3108,"score":3098},"Atm HMR disposal is not working as expected. Meshes are duplicated and this could lead to performance issues on large scenes.\n\nAlso not nice for DX. User needs to reload everytime.\n\nThis one is pretty tricky.\n\n# Desired solution.\n\nRenderer, scene and object follow a disposal flow when HMR hits",[3102,3103],{"name":3022,"color":3023},{"name":3104,"color":3105},"discussion 💭","AE4C80","HMR disposal","2023-09-12T18:58:32Z","https://github.com/Tresjs/tres/issues/23",{"description":3110,"labels":3111,"number":3114,"owner":3028,"repository":3029,"state":3030,"title":3115,"updated_at":3116,"url":3117,"score":3118},"**Describe the bug**\r\nWhen using any of the loops from renderLoops composable, `delta = clock.getDelta()` is always 0, it can't be used for animation\r\n\r\n\r\n**Reproduction**\r\n[Reproduction Link\r\n](https://stackblitz.com/edit/tresjs-basic-animations?file=src%2Fcomponents%2FTheExperience.vue)\r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to 'TheExperience.vue`\r\n2. Check the `onLoop`composable callback\r\n3. Console delta\r\n4. See value\r\n\r\n**Expected behavior**\r\nDelta should be the seconds passed since the time [.oldTime](https://threejs.org/docs/index.html#api/en/core/Clock.oldTime) was set and sets [.oldTime](https://threejs.org/docs/index.html#api/en/core/Clock.oldTime) to the current time.\r\nIf [.autoStart](https://threejs.org/docs/index.html#api/en/core/Clock.autoStart) is true and the clock is not running, also starts the clock\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: (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.1.0 => 1.1.0 \r\n vite: ^3.2.4 => 3.2.4 \r\n```\r\n",[3112,3113],{"name":3019,"color":3020},{"name":3022,"color":3023},81,"onLoop delta is always 0","2023-01-17T09:16:52Z","https://github.com/Tresjs/tres/issues/81",0.7295462,["Reactive",3120],{},["Set"],["ShallowReactive",3123],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4w3Vt-kQ0Uz4GHGGMoX7MQLQPHJPuL2firQ2ZE1Kin0":-1},"/Tresjs/tres/63"]