\r\n\r\n**Additional context**\r\nThis is useful is you want to manipulate the vertex individually, in the vertex shader\r\n",[2943,2946],{"name":2944,"color":2945},"question","d876e3",{"name":2947,"color":2948},"waiting for author","B145BC",230,"Support inline method in geometries ( EJ: toNonIndexed , setFromPoints)","2025-02-21T16:45:38Z","https://github.com/Tresjs/tres/issues/230",0.7510045,{"description":2955,"labels":2956,"number":2876,"owner":2877,"repository":2894,"state":2957,"title":2958,"updated_at":2959,"url":2960,"score":2883},"### Description\n\nFor more options on outside environment\n\n### Suggested solution\n\nhttps://github.com/pmndrs/drei#sky\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/cientos/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/cientos/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://cientos.tresjs.org/guide).\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.",[],"closed","Sky","2023-09-17T19:26:21Z","https://github.com/Tresjs/cientos/issues/106",{"description":2962,"labels":2963,"number":2965,"owner":2877,"repository":2935,"state":2957,"title":2966,"updated_at":2967,"url":2968,"score":2969},"## Bug\r\n\r\nNodeOps accidentally shares `scene` across multiple `TresCanvas`s.\r\n\r\nSee the StackBlitz reproduction for details.\r\n\r\n## Problem\r\n\r\nNodeOps's [`let scene`](https://github.com/Tresjs/tres/blob/f6097a3d6a3e34fddb689266b062869fe5a9bf1e/src/core/nodeOps.ts#L15) is [set whenever a new `Scene` is added to any `TresCanvas`](https://github.com/Tresjs/tres/blob/f6097a3d6a3e34fddb689266b062869fe5a9bf1e/src/core/nodeOps.ts#L84) – i.e., the variable points to the last `Scene` added to a `TresCanvas`. If elements from another `TresCanvas` read `scene` in nodeOps, the code expects that they will find *their* `Scene`, but they do not.\r\n\r\n## Solution?\r\n\r\n### Solution A\r\n\r\nWe could refactor nodeOps as `(context: TresContext) => NodeOps`. \r\n\r\nEvery new instance of `TresCanvas` could create a new nodeOps instance which contains a unique `TresContext` (i.e., with the appropriate `Scene`) within its scope.\r\n\r\n### Solution B\r\n\r\nOtherwise, we could simply recurse up the parent chain until we reach a `Scene` or run out of parents.\r\n\r\n## Reproduction\r\n\r\nhttps://stackblitz.com/edit/tresjs-basic-e6uzmm?file=src%2FApp.vue\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: 18.18.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 10.2.3 - /usr/local/bin/npm\r\n pnpm: 8.14.0 - /usr/local/bin/pnpm\r\n npmPackages:\r\n @tresjs/cientos: ^3.5.1 => 3.5.1 \r\n @tresjs/core: ^3.4.1 => 3.4.1 \r\n @tresjs/eslint-config-vue: ^0.2.1 => 0.2.1 \r\n vite: ^4.5.0 => 4.5.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.",[2964],{"name":2888,"color":2889},560,"NodeOps shares `scene` across multiple`TresCanvas`s","2024-03-08T10:36:46Z","https://github.com/Tresjs/tres/issues/560",0.71202606,{"description":2971,"labels":2972,"number":2986,"owner":2877,"repository":2935,"state":2957,"title":2987,"updated_at":2988,"url":2989,"score":2990},"### Describe \r\n\r\nAs a developer using TresJS, I would like the tone-mapping of the renderer to be set to `ACESFilmicToneMapping` as default.\r\n\r\nThis will introduce a Breaking change.\r\n\r\nDecisions based on feedback from the community: \r\n\r\n\r\n\r\n\r\n\r\n\r\nFrom left to right: r3f, Tres, Threlte\r\n\r\n\r\n\r\n\r\n## Docs\r\n\r\n[Render defaults](https://docs.pmnd.rs/react-three-fiber/api/canvas#render-defaults)\r\nCanvas uses [createRoot](https://docs.pmnd.rs/react-three-fiber/api/canvas#createroot) which will create a translucent THREE.WebGLRenderer with the following constructor args:\r\n\r\nantialias=true\r\nalpha=true\r\npowerPreference=\"high-performance\"\r\nand with the following properties:\r\n\r\noutputColorSpace = THREE.SRGBColorSpace\r\ntoneMapping = THREE.ACESFilmicToneMapping\r\nIt will also create the following scene internals:\r\n\r\nA THREE.Perspective camera\r\nA THREE.Orthographic cam if orthographic is true\r\nA THREE.PCFSoftShadowMap if shadows is true\r\nA THREE.Scene (into which all the JSX is rendered) and a THREE.Raycaster\r\nIn recent versions of threejs, THREE.ColorManagement.enabled will be set to true to enable automatic conversion of colors according to the renderer's configured color space. R3F will handle texture color space conversion. For more on this topic, see https://threejs.org/docs/#manual/en/introduction/Color-management.\r\n\r\n",[2973,2976,2979,2980,2983],{"name":2974,"color":2975},"good first issue","7057ff",{"name":2977,"color":2978},"help wanted","008672",{"name":2868,"color":2869},{"name":2981,"color":2982},"discussion 💭","AE4C80",{"name":2984,"color":2985},"v4","7980EA",492,"Set tone-mapping default to ACESFilmicToneMapping","2024-01-27T11:58:47Z","https://github.com/Tresjs/tres/issues/492",0.7275696,["Reactive",2992],{},["Set"],["ShallowReactive",2995],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fj1fKMGenjvyu8h8rA3I8ZQ1xX1MEpbgCgU5lqdPwVrQ":-1},"/Tresjs/tres/576"]