docs: updated thob task 2 (earth/moon) with upload limit audit

This commit is contained in:
divyap 2026-04-13 16:35:17 +05:30
parent 380b9982ca
commit 08af6b124e
2 changed files with 4 additions and 4 deletions

View File

@ -32,7 +32,7 @@ Implement a dynamic surface switcher (Earth/Moon) on a 3D sphere and evaluate th
- [x] Editor UX limitation (Context visibility) - [x] Editor UX limitation (Context visibility)
- [x] Documentation/Discovery limitation (Proprietary syntax) - [x] Documentation/Discovery limitation (Proprietary syntax)
- [x] Schema / data model limitation (Internal binding redundancy) - [x] Schema / data model limitation (Internal binding redundancy)
- [ ] Asset pipeline limitation - [x] Asset pipeline limitation (Silent 5MB file size upload limit)
## Workaround ## Workaround
- **Is there a workaround?**: Not required for functionality; manual memorization of syntax is currently required to bridge the documentation gap. - **Is there a workaround?**: Not required for functionality; manual memorization of syntax is currently required to bridge the documentation gap.

View File

@ -4,11 +4,11 @@
* **Possible**: Yes, Swapping between planetary textures (Earth/Moon) using a `RadioGroup` for selection. * **Possible**: Yes, Swapping between planetary textures (Earth/Moon) using a `RadioGroup` for selection.
* **Implementation used**: Hierarchical UI setup using a `RadioGroup` paired with a `For` loop to generate selectable items. Texture mapping was achieved by linking the `RadioGroup` state to a `MaterialVariant` node controlling the `map` property of the sphere. * **Implementation used**: Hierarchical UI setup using a `RadioGroup` paired with a `For` loop to generate selectable items. Texture mapping was achieved by linking the `RadioGroup` state to a `MaterialVariant` node controlling the `map` property of the sphere.
* **What worked as expected**: High-resolution textures (Earth/Moon) mapped correctly to the Sphere geometry without UV distortion. The logical flow from UI selection to 3D texture update was instantaneous. * **What worked as expected**: High-resolution textures (Earth/Moon) mapped correctly to the Sphere geometry without UV distortion. The logical flow from UI selection to 3D texture update was instantaneous.
* **Main limitation observed**: Managing multiple textures in a loop requires specific binding syntax (like `$context.item_currentItem.id`) which is a "guessing game" without integrated docs. * **Main limitation observed**: Managing multiple textures in a loop requires specific binding syntax (like `$context.item_currentItem.id`) which is a "guessing game" without integrated docs. Additionally, there is a **silent file size limit (~5MB)** for texture uploads; larger files fail to upload without any error message or user feedback.
* **Builder flow used**: Layers Panel (Node Hierarchy) -> Properties Panel (Texture Loading) -> UI Component Library (RadioGroup). * **Builder flow used**: Layers Panel (Node Hierarchy) -> Properties Panel (Texture Loading) -> UI Component Library (RadioGroup).
* **Complexity**: Medium-High. The complexity increases as you move from simple color swaps to multiple asset-based texture swaps in a logical loop. * **Complexity**: Medium-High. The complexity increases as you move from simple color swaps to multiple asset-based texture swaps in a logical loop.
* **Main limitation signals**: An extreme volume of `GetBindingData... method already registered` warnings appearing in clusters every time a new texture is selected. * **Main limitation signals**: Cluster of `GetBindingData` redundancy logs and **silent upload failures** for high-resolution texture files exceeding 5MB.
* **Workaround status**: Successfully implemented using 100% native builder components. * **Workaround status**: Limited; high-res textures must be manually compressed before upload to ensure they are accepted by the builder's asset pipeline.
### Console Warnings/Errors Seen (Deduplicated) and Probable Meaning ### Console Warnings/Errors Seen (Deduplicated) and Probable Meaning
1. **Redundant Binding Registration**: `GetBindingData... method already registered`. 1. **Redundant Binding Registration**: `GetBindingData... method already registered`.