⚡ optimize microtubule torus with instanced mesh#75
Hidden character warning
Conversation
- Replaced individual mesh instances with InstancedMesh in MicrotubuleTorus.
- Used useMemo for Object3D matrix helper to avoid per-frame allocations.
- Optimized useFrame loop for matrix updates.
- Added key={count} and frustumCulled={false} for robustness.
- Reduced draw calls from ~1082 to ~4.
Co-authored-by: jason420247 <44763042+jason420247@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
💡 What: Replaced individual mesh rendering with
InstancedMeshin theMicrotubuleToruscomponent. UseduseMemofor a reusableTHREE.Object3Dto handle instance transformations and optimized theuseFrameloop.🎯 Why: Rendering thousands of individual meshes (360 and 720 per torus) is extremely expensive due to the high number of draw calls (~1082 for the scene).
📊 Measured Improvement: Theoretically reduced draw calls from approximately 1082 to 4. This significantly reduces CPU overhead and improves frame rates by batching geometry rendering.
PR created automatically by Jules for task 12960406486949152423 started by @jason420247