\r\n \u003CTresScene>\r\n \u003CTresPoints>\r\n \u003CTresBufferGeometry :position=\"[vertices, 3]\" />\r\n \u003CTresPointsMaterial :color=\"0x888888\" />\r\n \u003C/TresPoints>\r\n \u003C/TresScene>\r\n\u003C/TresCanvas>\r\n```\r\nNo matter how i change `aspect`, for exampe **0.5** or **2**, there is no change in view.\r\n\r\naspect = 0.5\r\n\u003Cimg width=\"656\" alt=\"image\" src=\"https://user-images.githubusercontent.com/11868294/219375921-50474cdc-39bf-4248-bca7-1dd2ee6fe873.png\">\r\n\r\n\r\naspect = 1\r\n\u003Cimg width=\"582\" alt=\"image\" src=\"https://user-images.githubusercontent.com/11868294/219375756-00dc3849-7ec3-4428-bd6c-5ebdb00d8381.png\">\r\n\r\n\r\n\r\n\r\n\r\naspect = 2\r\n\u003Cimg width=\"634\" alt=\"image\" src=\"https://user-images.githubusercontent.com/11868294/219375639-72380307-a3f5-455f-8d7a-ef44a0e880cd.png\">\r\n\r\nMaybe i miss something?\r\n\r\n\r\n",[],"TresPerspectiveCamera: aspect not work?","2023-08-26T15:28:15Z","https://github.com/Tresjs/lab/issues/3",{"description":2919,"labels":2920,"number":30,"owner":2868,"repository":2924,"state":2878,"title":2925,"updated_at":2926,"url":2927,"score":2928},"**Describe the bug**\r\n\r\nDocumentation for events emitted by this component are missing\r\n\r\n- `dragging` event\r\n- `change` event\r\n- `mouseDown` event\r\n- `mouseUp` event\r\n- `objectChange` event\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**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to '...'\r\n2. Click on '....'\r\n3. Scroll down to '....'\r\n4. See error\r\n",[2921],{"name":2922,"color":2923},"docs","0075ca","tres","Add events to TransformControls documentation","2023-01-07T18:45:57Z","https://github.com/Tresjs/tres/issues/64",0.75156254,{"description":2930,"labels":2931,"number":2935,"owner":2868,"repository":2924,"state":2878,"title":2936,"updated_at":2937,"url":2938,"score":2939},"**Describe the bug**\r\nSeems like the state of useTres keep alive between pages, even when the routes are lazy\r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to https://serene-mousse-562782.netlify.app/MouseShaderEffect\r\n2. Move the mouse, observe no controls is on the scene\r\n3. Go to home using the navbar (here you can see we have the pam-camera-control)\r\n4. Return to the mouseShaderEffect using the navbar (observe now the state of pam-camera-controls remains)\r\n\r\nThis behavior also happens with orbicControls\r\n\r\n**Expected behavior**\r\nA new route should be a complete new canvas which also means that the old canvas should die entirely and every other effect\r\n\r\n**Additional context**\r\nThis could affect other states/effect throug the library\r\n",[2932],{"name":2933,"color":2934},"bug","d73a4a",173,"Problem with state using router navigation","2023-04-05T13:41:50Z","https://github.com/Tresjs/tres/issues/173",0.75705904,{"description":2941,"labels":2942,"number":2943,"owner":2868,"repository":2924,"state":2878,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Description\r\n\r\nRight now there is no way to access the TresCanvas context without hacking the script setup using TresCanvas:\r\n\r\n\u003Cdetails>\r\n\u003Csummary>\u003Cstrong>Hack\u003C/strong>\u003C/summary>\r\n\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nimport { TresCanvas } from '@tresjs/core';\r\nimport { computed, ref, onMounted } from 'vue';\r\n\r\nimport { extend, useTresContext } from '@tresjs/core';\r\nimport { OrbitControls } from 'three/addons/controls/OrbitControls';\r\nimport { TextGeometry } from 'three/addons/geometries/TextGeometry';\r\n\r\nconst trescanvas = ref();\r\nconst state = ref();\r\n\r\nonMounted(() => {\r\n setTimeout(() => {\r\n state.value = trescanvas.value?.context;\r\n }, 0);\r\n});\r\n\r\n// Add the element to the catalogue\r\nextend({ TextGeometry, OrbitControls });\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CTresCanvas ref=\"trescanvas\" shadows alpha>\r\n \u003CTresPerspectiveCamera :position=\"[5, 5, 5]\" />\r\n \u003CTresOrbitControls\r\n v-if=\"state?.renderer\"\r\n :args=\"[state?.camera, state?.renderer?.domElement]\"\r\n />\r\n \u003CTresMesh>\r\n \u003CTresTextGeometry :args=\"['TresJS', { font, ...fontOptions }]\" center />\r\n \u003CTresMeshMatcapMaterial :matcap=\"matcapTexture\" />\r\n \u003C/TresMesh>\r\n \u003C/TresCanvas>\r\n\u003C/template>\r\n```\r\n\u003C/details>\r\n\r\n### Suggested solution\r\n\r\nAdd default slot props, we¡ve the default slot there without any binding:\r\n```ts\r\n\u003Ccanvas\r\n ref=\"canvas\"\r\n :data-scene=\"scene.uuid\"\r\n :class=\"$attrs.class\"\r\n :data-tres=\"`tresjs ${pkg.version}`\"\r\n :style=\"{\r\n display: 'block',\r\n width: '100%',\r\n height: '100%',\r\n position: windowSize ? 'fixed' : 'relative',\r\n top: 0,\r\n left: 0,\r\n pointerEvents: 'auto',\r\n touchAction: 'none',\r\n ...$attrs.style as Object,\r\n }\"\r\n >\r\n \u003Cslot v-bind=\"context\" />\r\n\u003C/canvas>\r\n```\r\n\r\nthen in the sfc template:\r\n\r\n```html\r\n\u003CTresCanvas shadows alpha v-slot=\"{ camera, renderer }\">\r\n \u003CTresPerspectiveCamera :position=\"[5, 5, 5]\" />\r\n \u003CTresOrbitControls\r\n v-if=\"renderer\"\r\n :args=\"[camera, renderer.domElement]\"\r\n />\r\n\u003C/TresCanvas>\r\n```\r\n\r\n### Alternative\r\n\r\ncheck the hack in the description\r\n\r\n### Additional context\r\n\r\nrelated #565\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.",[],573,"provide default slot props in TresCanvas","2024-03-05T19:47:12Z","https://github.com/Tresjs/tres/issues/573",0.7571157,{"description":2949,"labels":2950,"number":2951,"owner":2868,"repository":2924,"state":2878,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Describe the bug\n\n\u003Cimg width=\"1006\" alt=\"Screenshot 2024-01-21 at 22 33 48 copy\" src=\"https://github.com/Tresjs/tres/assets/20469369/ff81041f-518b-46dc-87a5-d8c4aa16c8c4\">\r\n\r\nIn the [Tres docs](https://docs.tresjs.org/guide/), an error appears in the sandbox:\r\n\r\n```\r\nFailed to resolve component: TresDirectionalLight\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n at \u003CRepl>\r\n```\r\n\r\n\r\n\n\n### Reproduction\n\nN/A\n\n### Steps to reproduce\n\n* in the browser, navigate to https://docs.tresjs.org/guide/\r\n* in the sandbox window, see the error\n\n### System Info\n\n```shell\nTested in:\r\n\r\n* Firefox 127.0.1 (Mac ARM)\r\n* Chrome Version 120.0.6099.234 (Mac ARM)\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.",[],521,"docs(sandbox): \"Failed to resolve component: TresDirectionalLight\"","2024-01-22T15:10:07Z","https://github.com/Tresjs/tres/issues/521",0.75729495,["Reactive",2957],{},["Set"],["ShallowReactive",2960],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fLrCu7R6FIjYopZoxo7ZeVP_J-YiD3F7onv8qzxtcEbE":-1},"/Tresjs/cientos/384"]