\r\n\u003C/template>\r\n```\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/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.",[2893,2896,2899],{"name":2894,"color":2895},"feature","c2e0c6",{"name":2897,"color":2898},"p3-significant","2C78E3",{"name":2900,"color":2901},"v5","EFC959",883,"WebGPU support","2025-02-06T09:35:42Z","https://github.com/Tresjs/tres/issues/883",0.7453841,{"description":2908,"labels":2909,"number":2917,"owner":2872,"repository":2918,"state":2874,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Description\n\nThe current implementation is different from R3F, as you can see, the model is treat as a group (I personally prefer this approach) is best performance and cover most of the cases, BUT, not all for some specific cases maybe this is not a viable solution.\r\n\r\n\r\n\r\nR3F handling the models in which each geometry has a different RigidBody/Collider:\r\n\r\n\r\n\r\n\r\nI don't know if this will create future problems for uses cases or the people can workaround them. I don't know if this makes joints cases when models more difficult.\n\n### Suggested solution\n\nProper discussion and research\n\n### Alternative\n\nJust by the record, I like the current approach (but maybe I'm thinking in just low poly games)\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/rapier/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/rapier/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://rapier.tresjs.org/guide).\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/rapier/issues) that reports the same bug to avoid creating a duplicate.",[2910,2911,2914],{"name":2860,"color":2861},{"name":2912,"color":2913},"investigation","D03599",{"name":2915,"color":2916},"p2-to-be-discussed","97C1B1",127,"rapier","Handling models? ","2024-09-17T10:20:52Z","https://github.com/Tresjs/rapier/issues/127",0.747302,{"description":2924,"labels":2925,"number":2928,"owner":2872,"repository":2873,"state":2874,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Description\r\n\r\nAs a developer using TresJS, I want to have a `\u003CPortal>` component that can contain a separate `Scene` and `context`.\r\n\r\n### Suggested solution\r\n\r\nProvide a `\u003CPortal>` component similar to R3F.\r\n\r\n### Requirements\r\n\r\n- [ ] Add override-able pointer to `TresContext` (Also add as prop to TresCanvas: see #581 ); use vanilla `THREE.Vector2`, accept `Vector2` and `UsePointerOptions` as TresCanvas prop\r\n- [ ] Make these fields on `TresContext` swappable and (in some case injectable by the user): scene, camera, cameras, controls, raycaster, eventManager, sizes\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.",[2926,2927],{"name":2897,"color":2898},{"name":2900,"color":2901},789,"Portal","2025-02-06T09:59:01Z","https://github.com/Tresjs/tres/issues/789",0.7484833,{"description":2934,"labels":2935,"number":2939,"owner":2872,"repository":2873,"state":2874,"title":2940,"updated_at":2941,"url":2942,"score":2943},"Atm the docs don't have search functionality, as we grow on features, it's important to have it\n\nhttps://vitepress.dev/reference/default-theme-search",[2936],{"name":2937,"color":2938},"docs","0075ca",152,"Add Algolia Search to docs","2024-03-28T11:19:27Z","https://github.com/Tresjs/tres/issues/152",0.7571223,{"description":2945,"labels":2946,"number":2948,"owner":2872,"repository":2873,"state":2874,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Description\n\nAs a developer of TresJS I want to have a separation of concerns in the composables.\n\n### Suggested solution\n\nMove `perf` it out of the file.\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/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.",[2947],{"name":2883,"color":2884},1001,"Move performance state out of useTresContextProvider","2025-04-23T11:25:34Z","https://github.com/Tresjs/tres/issues/1001",0.76192224,{"description":2954,"labels":2955,"number":2956,"owner":2872,"repository":2873,"state":2957,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Describe the bug\n\nI recently found this lib and find it awesome so far! Unfortunately, while I was experimenting with the `TresDirectionalLight` I realised there is an exception thrown when passing `:shadow-map-size-width` or `:shadow-map-size-height` attrs to the component, which seems to work fine in the examples (probably something changed overtime).\r\nThe root cause as I can see, comes from `[tres/src/core/nodeOps.ts].patchProp`, which tries to retrieve an inner object prop, based on the attribute name. The problem with `shadow-map-size-height` comes from the fact it must be transpiled into `shadow.mapSize.height`, where the selector becomes `shadow.map.size.height`.\r\n\r\nAs a temporary solution, I use v-bind on the component attached to object as follows:\r\n```\r\nconst shadowConfig = {\r\n 'shadow-mapSize-width': 512,\r\n 'shadow-mapSize-height': 512\r\n}\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/tresjs-basic-yslayw\n\n### Steps to reproduce\n\nnpm intall && npm run dev\r\nerror is being logged in the inspector :/\n\n### System Info\n\n_No response_\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.",[],445,"closed","[Cannot read properties of null (reading 'size')] patchProp does not properly handle camelCase props","2023-11-28T13:27:55Z","https://github.com/Tresjs/tres/issues/445",0.6987524,{"description":2963,"labels":2964,"number":2968,"owner":2872,"repository":2969,"state":2957,"title":2970,"updated_at":2971,"url":2972,"score":2973},"**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",[2965],{"name":2966,"color":2967},"bug","d73a4a",49,"post-processing","Cannot read properties of undefined (reading 'canvas')","2023-10-19T15:07:15Z","https://github.com/Tresjs/post-processing/issues/49",0.7253551,{"description":2975,"labels":2976,"number":2977,"owner":2872,"repository":2873,"state":2957,"title":2978,"updated_at":2979,"url":2980,"score":2981},"### Describe the bug\r\n\r\nThis is more likely me doing something wrong than a bug. I am trying to setup a simple scene, where a sphere is put in front of a plane with a photo. \r\nThe sphere has [Meshtransmissionmaterial](https://github.com/pmndrs/drei-vanilla?tab=readme-ov-file#meshtransmissionmaterial) applied to it. It seems to work but the sphere is only black instead of transparent.\r\n\r\n\u003Cimg width=\"1213\" alt=\"Bildschirmfoto 2024-11-29 um 01 05 56\" src=\"https://github.com/user-attachments/assets/b82dfc5c-c4f1-46e6-aefa-0d3345a989ca\">\r\n\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nimport {\r\n Mesh,\r\n MeshStandardMaterial,\r\n PlaneGeometry,\r\n SphereGeometry,\r\n} from \"three\";\r\n\r\nimport { MeshTransmissionMaterial } from \"@pmndrs/vanilla\";\r\nimport { TresCanvas, useTexture } from \"@tresjs/core\";\r\n\r\nconst geometry = new SphereGeometry(0.4);\r\nconst material = new MeshTransmissionMaterial({\r\n _transmission: 1,\r\n thickness: 0,\r\n roughness: 0,\r\n chromaticAberration: 0.03,\r\n distortion: 0,\r\n distortionScale: 0.5,\r\n temporalDistortion: 0.0,\r\n});\r\nconst meshWithMaterial = new Mesh(geometry, material);\r\nconst { map } = await useTexture({\r\n map: \"/lola.jpg\",\r\n});\r\nconst meshPlane = new Mesh(\r\n new PlaneGeometry(0.7, 0.7),\r\n new MeshStandardMaterial({ map })\r\n);\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CTresCanvas>\r\n \u003CTresPerspectiveCamera :position=\"[0, 0, 4]\" />\r\n \u003CTresGroup :scale=\"3\">\r\n \u003Cprimitive :object=\"meshWithMaterial\" />\r\n \u003Cprimitive :object=\"meshPlane\" />\r\n \u003C/TresGroup>\r\n \u003CTresHemisphereLight :intensity=\"3\" />\r\n \u003C/TresCanvas>\r\n\u003C/template>\r\n```",[],874,"\"Drei Vanilla\"’s MeshTransmissionMaterial renders only black sphere","2024-12-01T12:42:17Z","https://github.com/Tresjs/tres/issues/874",0.72562724,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbhVApb5HE9vL_WGhyHNqidRMW7G-2HHKyIa_qO_Ku6k":-1},"/Tresjs/cientos/453"]