\r\n\u003C/template>\r\n\r\n//both logs from cientos\r\ntransformData: {\r\n inheritType: 1, \r\n eulerOrder: 'ZYX', \r\n rotation: Array(3), \r\n parentMatrix: _Matrix4, \r\n parentMatrixWorld: _Matrix4\r\n}\r\ntres__name: \"Group\"\r\n```\r\n\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 14.3.1\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 90.00 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node\r\n Yarn: 1.22.21 - ~/.nvm/versions/node/v18.18.0/bin/yarn\r\n npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm\r\n Browsers:\r\n Chrome: 125.0.6422.112\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/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.\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[3018,3021],{"name":3019,"color":3020},"needs reproduction","16309A",{"name":3022,"color":3023},"waiting for author","DEEAB8",429,"Tresjs","cientos","open","FBXLoader: Missing data from userData field ","2024-09-12T20:08:31Z","https://github.com/Tresjs/cientos/issues/429",0.6931756,{"description":3033,"labels":3034,"number":3044,"owner":3025,"repository":3045,"state":3027,"title":3046,"updated_at":3047,"url":3048,"score":3049},"### Description\n\nIf we found a way to put all the updates on just one loop, we can come with some interesting advantages.\r\n\r\n- What if the user wants to run the physics loop in a different priority?\r\n- What if we want to stop or apply some fps limit to the whole library?\r\n- Should this have better performance?\n\n### Suggested solution\n\nCurrently, this is an investigation and should not be prioritized\r\n\r\nI personally don't know if this is possible\n\n### Alternative\n\nWe still have the alternative to pass the limit FPS or to invalidate, or even the priority loop per component\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.",[3035,3038,3041],{"name":3036,"color":3037},"help wanted","008672",{"name":3039,"color":3040},"investigation","D03599",{"name":3042,"color":3043},"p1-chore","BFD4F2",123,"rapier","All in one renderloop?","2024-09-13T14:27:45Z","https://github.com/Tresjs/rapier/issues/123",0.74029106,{"description":3051,"labels":3052,"number":3059,"owner":3025,"repository":3026,"state":3027,"title":3060,"updated_at":3061,"url":3062,"score":3063},"### Description\n\nAs a developer using TresJS, I would like to have a component that can keep child components centered on screen, even after screen resizes.\n\n### Suggested solution\n\nA component that works like [Drei's `\u003CBounds />`](https://drei.docs.pmnd.rs/staging/bounds#bounds) would be welcome.\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.",[3053,3056],{"name":3054,"color":3055},"feature","c2e0c6",{"name":3057,"color":3058},"p2-nice-to-have","D4C5F9",408,"\u003CBounds />","2024-12-17T18:07:35Z","https://github.com/Tresjs/cientos/issues/408",0.7430743,{"description":3065,"labels":3066,"number":3069,"owner":3025,"repository":3026,"state":3027,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### Describe the bug\n\nCan someone explain to me how to make the environment work with a file? With the preset it works well. using useEnvironment doesn't work either.\r\n\r\nI tried with a file in the public folder \r\n\r\n```javascript\r\n\u003CEnvironment\r\n path=\"/milkyway-4k.jpg\"\r\n :background=\"true\"\r\n/>\r\n```\r\nbut also by importing it from the assets folder.\r\n\r\n```javascript\r\nimport MilkyWayEnvironment from '@assets/environments/milkyway-4k.jpg'\r\n\r\n\u003CEnvironment\r\n :path=\"MilkyWayEnvironment\"\r\n :background=\"true\"\r\n/>\r\n```\r\n\r\nWhen using the component I get only a warning :\r\n```\r\n[Vue warn]: expose() should be passed a plain object, received ref. \r\n at \u003CComponent path=\"/milkyway-4k.jpg\" background=true > \r\n at \u003CApp>\r\n```\r\n\r\nWhen I use useEnvironments I get 2 warnings and 1 error : \r\n```\r\n[Vue warn]: injection \"useTres\" not found. \r\nUnhandled error during execution of setup function \r\ntres.js:431 Uncaught (in promise) Error: useTresContext must be used together with useTresContextProvider\r\n```\r\n\r\nI tried to import the environment image into Stackblitz but it doesn't work. \n\n### Reproduction\n\nhttps://stackblitz.com/edit/tresjs-basic-8r1lk7\n\n### Steps to reproduce\n\n_No response_\n\n### System Info\n\n_No response_\n\n### Used Package Manager\n\nyarn\n\n### Code of Conduct\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.\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[3067,3068],{"name":3019,"color":3020},{"name":3022,"color":3023},305,"Environment not working","2023-12-22T00:49:40Z","https://github.com/Tresjs/cientos/issues/305",0.7490237,{"description":3075,"labels":3076,"number":3079,"owner":3025,"repository":3045,"state":3027,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Description\n\nWe need to handle these events or explain in the docs the behavior. Rapier automatically put in sleep object that are slow or stop a short time.\r\n\r\nAlso, many of the reactive props are setting true (awake) automatically, but that maybe is not for all use cases\n\n### Suggested solution\n\nMy idea is a new props to handle this, R3F handle this with a function, maybe we need to check that\n\n### Alternative\n\nAs this is the default behavior for Rapier I wouldn't mess around too much here, but is necessary to explain it, and/or handle it in a better way\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.",[3077,3078],{"name":3039,"color":3040},{"name":3057,"color":3058},131,"Sleep, awake events","2024-09-26T09:52:28Z","https://github.com/Tresjs/rapier/issues/131",0.75439966,{"description":3085,"labels":3086,"number":3090,"owner":3025,"repository":3091,"state":3092,"title":3093,"updated_at":3094,"url":3095,"score":3096},"**Is your feature request related to a problem? Please describe.**\r\nThe existing effects have some code parts in common that can probably be shared.\r\n\r\n**Describe the solution you'd like**\r\nShare common code parts.",[3087],{"name":3088,"color":3089},"enhancement","a2eeef",59,"post-processing","closed","Refactor existing effects","2023-12-17T21:31:05Z","https://github.com/Tresjs/post-processing/issues/59",0.7275409,{"description":3098,"labels":3099,"number":3103,"owner":3025,"repository":3026,"state":3092,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Describe the bug\n\n\r\n\r\nSome shapes have problems with colors\n\n### Reproduction\n\nhttps://stackblitz.com/edit/tresjs-basic-1skx4b?file=src%2Fcomponents%2FTheExperience.vue\n\n### Steps to reproduce\n\nCheck the console on the reprodution link\n\n### System Info\n\n```shell\npnpm\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/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.\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[3100],{"name":3101,"color":3102},"bug","d73a4a",110,"Colors error in some shapes","2023-07-18T23:12:00Z","https://github.com/Tresjs/cientos/issues/110",0.74297816,{"description":3109,"labels":3110,"number":3103,"owner":3025,"repository":3045,"state":3092,"title":3112,"updated_at":3113,"url":3114,"score":3107},"### Description\n\nRight now we can apply any force, the object is not being exported and even doing it, tryng to applyng any force, doesn't throw an error but, do nothing\n\n### Suggested solution\n\nCould be something like (currently this is not doing anything):\r\n```\r\nconst jumpCube = () => {\r\n if (rigidCubeRef.value) {\r\n rigidCubeRef.value.instance[0].rigidBody.applyImpulse({ x: 0, y: 1, z: 0 })\r\n }\r\n}\r\n```\r\nWe can expose some object like:\r\n\r\n```\r\ndefineExpose({\r\n instance: rigidBodyInfos,\r\n collider: colliderInfos,\r\n})\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/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.",[3111],{"name":3054,"color":3055},"Applyng method to RigidBodies","2024-09-12T13:49:59Z","https://github.com/Tresjs/rapier/issues/110",{"description":3116,"labels":3117,"number":3118,"owner":3025,"repository":3026,"state":3092,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Description\n\nAs a developer using cientos, I would like to have clear linting rules in all tresJs Ecosystem.\n\n### Suggested solution\n\nFollow the format on TresJs/Core\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.",[],195,"Update lint rules","2023-09-05T15:19:17Z","https://github.com/Tresjs/cientos/issues/195",0.74504346,{"description":3124,"labels":3125,"number":3126,"owner":3025,"repository":3127,"state":3092,"title":3128,"updated_at":3129,"url":3130,"score":3131},"### Description\n\nI would like to have a version for Babylon.js\n\n### Suggested solution\n\nI'm currently learning Babylon.js and have noticed some differences in terms of mesh events between Three.js and Babylon.js. Unlike Three.js, Babylon.js provides a mechanism similar to the actionManager on its meshes. I'm curious to know if Cientos has a similar feature. I'm looking forward to seeing how the combination of Vue with Babylon.js will eventually shape a project\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.",[],502,"tres","Are you considering providing a version for Babylon.js after completing this project?","2024-01-10T10:59:15Z","https://github.com/Tresjs/tres/issues/502",0.7459936,["Reactive",3133],{},["Set"],["ShallowReactive",3136],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fM1QAYUlRxFGlWuGovNtXNDAUwjhfTjYyVZz-7ggnUeU":-1},"/Tresjs/cientos/423"]