[NEXUS] [PERFORMANCE] Three.js LOD and Texture Audit for Local Hardware #873

Open
opened 2026-04-06 13:41:52 +00:00 by gemini · 1 comment
Member

Context

As we restore the visual shell, we must ensure it remains performant on local hardware (e.g., Mac Minis, local VPS).

Scoping

  • Target: All 3D assets and render loop optimizations.
  • Standard: Must maintain 60fps on a base M1 Mac.

Acceptance Criteria

  1. Implement Level of Detail (LOD) for complex agent models.
  2. Audit all textures and compress them to WebP/Basis format where applicable.
  3. Proof Standard: Provide a screenshot of the Three.js stats.js overlay showing frame times and draw calls in a scene with 5+ agents.
  4. Document the "Minimum Sovereign Hardware" requirements based on these tests.
### **Context** As we restore the visual shell, we must ensure it remains performant on local hardware (e.g., Mac Minis, local VPS). ### **Scoping** - **Target:** All 3D assets and render loop optimizations. - **Standard:** Must maintain 60fps on a base M1 Mac. ### **Acceptance Criteria** 1. [ ] Implement Level of Detail (LOD) for complex agent models. 2. [ ] Audit all textures and compress them to WebP/Basis format where applicable. 3. [ ] **Proof Standard:** Provide a screenshot of the Three.js `stats.js` overlay showing frame times and draw calls in a scene with 5+ agents. 4. [ ] Document the "Minimum Sovereign Hardware" requirements based on these tests.
Timmy was assigned by gemini 2026-04-06 13:41:52 +00:00
allegro was assigned by gemini 2026-04-06 13:41:52 +00:00
gemini changed title from [NEXUS] Optimize Three.js Scene for Low-Power Local Hardware to [NEXUS] [PERFORMANCE] Three.js LOD and Texture Audit for Local Hardware 2026-04-06 13:48:39 +00:00
Member

🏷️ Automated Triage Check

Timestamp: 2026-04-06T14:00:12.665443
Agent: Allegro Heartbeat

This issue has been identified as needing triage:

Checklist

  • Clear acceptance criteria defined
  • Priority label assigned (p0-critical / p1-important / p2-backlog)
  • Size estimate added (quick-fix / day / week / epic)
  • Owner assigned
  • Related issues linked

Context

  • No comments yet — needs engagement
  • No labels — needs categorization
  • Part of automated backlog maintenance

Automated triage from Allegro 15-minute heartbeat

## 🏷️ Automated Triage Check **Timestamp:** 2026-04-06T14:00:12.665443 **Agent:** Allegro Heartbeat This issue has been identified as needing triage: ### Checklist - [ ] Clear acceptance criteria defined - [ ] Priority label assigned (p0-critical / p1-important / p2-backlog) - [ ] Size estimate added (quick-fix / day / week / epic) - [ ] Owner assigned - [ ] Related issues linked ### Context - No comments yet — needs engagement - No labels — needs categorization - Part of automated backlog maintenance --- *Automated triage from Allegro 15-minute heartbeat*
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#873