` on the same page. \n\nShould be easier now that is a custom renderer, my wild guess is that composable is being shared between the two instances, so the second one doesn't create a singleton. v1 Also is not possible\n\nThis is a nice to have.\n\n",[2939],{"name":2940,"color":2941},"v2","FEE22E",153,"closed","Multiple canvas in same page","2023-04-05T13:41:40Z","https://github.com/Tresjs/tres/issues/153",0.6568052,{"description":2949,"labels":2950,"number":2952,"owner":2863,"repository":2916,"state":2943,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Describe the bug\r\n\r\nDynamically changing the camera when passed as a prop does not change the active camera\r\n\r\n```ts\r\n\u003CTresCanvas v-bind=\"gl\" :camera=\"camera\">\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/tresjs-basic-4uzxuz?file=package.json,src%2Fcomponents%2FTheExperience.vue,vite.config.ts\r\n\r\n### Steps to reproduce\r\n\r\nChange the camera type on the controls GUI\r\n\r\n\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.20.0 - /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 pnpm: 8.6.10 - /usr/local/bin/pnpm\r\n npmPackages:\r\n @tresjs/cientos: ^3.2.0 => 3.2.0 \r\n @tresjs/core: 3.1.1 => 3.1.1 \r\n @tresjs/leches: ^0.7.0 => 0.7.0 \r\n vite: ^4.3.8 => 4.3.8\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.",[2951],{"name":2857,"color":2858},383,"TresCanvas camera prop not working as expected","2023-09-13T11:26:48Z","https://github.com/Tresjs/tres/issues/383",0.70536375,{"description":2958,"labels":2959,"number":2960,"owner":2863,"repository":2864,"state":2943,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### Description\r\n\r\nAs a developer using Tres/Cientos:\r\n\r\n* I want props listings to be generated from commented source code.\r\n* I don't want to have to copy/paste props from `.vue` files and format as markdown in most cases.\r\n\r\nThe current solution is simply to copy/paste props and format them as markdown. This means that the docs' props listings fall out of sync with actual code.\r\n\r\n### Suggested solution\r\n\r\nThe [`vue-component-meta` package](https://github.com/vuejs/language-tools/tree/master/packages/vue-component-meta) can generate a JS object describing SFC props. \r\n\r\nI suggest we use that package to generate tables from the component source files.\r\n\r\n### Alternative\r\n\r\nContinue copy/pasting props\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\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.",[],256,"Autogenerate props listings for docs","2023-11-24T12:57:33Z","https://github.com/Tresjs/cientos/issues/256",0.7128108,{"description":2966,"labels":2967,"number":2968,"owner":2863,"repository":2916,"state":2943,"title":2969,"updated_at":2970,"url":2971,"score":2972},"### Description\r\n\r\nIm probably dumb for asking this but, How do i import and texturize wavefront object files?\r\n\r\n### Suggested solution\r\n\r\nI wanted to use something like \r\n```\r\n\u003COBJModel path=\"/models/AkuAku.obj\" />\r\n```\r\nbut no-where in the docs does it mention wavefront obj.\r\n\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\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.",[],884,"Greetings","2024-12-17T21:44:35Z","https://github.com/Tresjs/tres/issues/884",0.71799386,["Reactive",2974],{},["Set"],["ShallowReactive",2977],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fOjWdtD6uq2vQ_obFKfVd0W8l3TysxseQk14Y1VpWCXA":-1},"/Tresjs/cientos/193"]