\r\n \u003CTresMeshStandardMaterial v-bind=\"pbrTexture\" />\r\n \u003C/TresMesh>\r\n\u003C/template>\r\n```\r\n\r\nHere we are getting the ref for the mesh with the Mesh instance so we can update the rotation, but `boxRef` remains a Proxy, a solution would be to `unref` or use a shallowRef since Direct template ref are not available see https://github.com/vuejs/core/issues/1227\r\n\r\n\r\nI would love to have your input here @wheatjs @kissu @Astanusic \r\n\r\n## Food for though \r\n\r\nhttps://discoverthreejs.com/tips-and-tricks/#performance ",[3080,3083],{"name":3081,"color":3082},"help wanted","008672",{"name":3084,"color":3085},"discussion 💭","AE4C80","Performance discussion","2023-12-13T08:55:23Z","https://github.com/Tresjs/tres/issues/33",{"description":3090,"labels":3091,"number":3097,"owner":3020,"repository":3045,"state":3035,"title":3098,"updated_at":3099,"url":3100,"score":3101},"**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",[3092,3093,3094],{"name":3031,"color":3032},{"name":3081,"color":3082},{"name":3095,"color":3096},"v2","FEE22E",177,"[v2] - Shaders are not working 100%","2023-03-31T09:13:55Z","https://github.com/Tresjs/tres/issues/177",0.73322034,{"description":3103,"labels":3104,"number":3115,"owner":3020,"repository":3116,"state":3035,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### Describe the bug\r\n\r\nLensflare seems to be broken on v4\r\n\r\nCannot destructure property 'registerCamera' of '(intermediate value)(intermediate value)(intermediate value)' as it is undefined.\r\n\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nRun local playground\r\n\r\n### Steps to reproduce\r\n\r\n_No response_\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 14.5\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 51.02 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 10.5.0 - ~/.nvm/versions/node/v20.12.2/bin/npm\r\n pnpm: 8.15.4 - ~/Library/pnpm/pnpm\r\n bun: 1.0.2 - ~/.bun/bin/bun\r\n Browsers:\r\n Brave Browser: 120.1.61.116\r\n Chrome: 125.0.6422.142\r\n Safari: 17.5\r\n npmPackages:\r\n @tresjs/core: 4.0.0-rc.2 => 4.0.0-rc.2 \r\n @tresjs/leches: ^0.14.0 => 0.14.0\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/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.",[3105,3106,3109,3112],{"name":3031,"color":3032},{"name":3107,"color":3108},"v4","EEF2B0",{"name":3110,"color":3111},"p4-important-bug","D93F0B",{"name":3113,"color":3114},"regression","167F7A",435,"cientos","Lensflare playground demo is broken","2024-08-28T19:23:52Z","https://github.com/Tresjs/cientos/issues/435",0.739147,{"description":3122,"labels":3123,"number":3128,"owner":3020,"repository":3045,"state":3035,"title":3129,"updated_at":3130,"url":3131,"score":3132},"**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",[3124,3125],{"name":3031,"color":3032},{"name":3126,"color":3127},"pending-triage","97A4FE",162,"[v2] - Failed to resolve component warnings","2023-11-23T18:35:20Z","https://github.com/Tresjs/tres/issues/162",0.744832,["Reactive",3134],{},["Set"],["ShallowReactive",3137],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f6oUg6HyoMyjbIEs707LcSuuN5NQ7fEawRuO2HFgI6AU":-1},"/Tresjs/tres/533"]