Editing Openai/69676758-d944-8003-a3d4-835e33b4e372 (section)

=== Assistant: Here’s a clear diagram of how a single frame splits between CPU and GPU for your 3770K + RX 6600 XT system targeting 60… ===
Here’s a clear diagram of how a single frame splits between CPU and GPU for your 3770K + RX 6600 XT system targeting 60 FPS (16.67 ms per frame). I’ve kept numbers realistic and rounded slightly for clarity.

===== <syntaxhighlight>┌───────────────────────────────────────────────┐ =====
│ TOTAL FRAME: 16.67 ms                         │
├─────────────┬──────────────┬─────────────────┤
│ CPU         │ GPU          │ Notes           │
├─────────────┼──────────────┼─────────────────┤
│ 7.5 ms      │ 9.2 ms       │ CPU + GPU must run in parallel; frame time is max(CPU, GPU)
└─────────────┴──────────────┴─────────────────┘

</syntaxhighlight>

===== |     |     |     | =====
| --- | --- | --- |
|     |     |     |
|     |     |     |
|     |     |     |
|     |     |     |
|     |     |     |
|     |     |     |

===== |     |     |     | =====
| --- | --- | --- |
|     |     |     |
|     |     |     |
|     |     |     |
|     |     |     |
|     |     |     |

===== 1. CPU-limited mechanics - Cap number of active AI/NPCs to fit 3 ms–4 ms total AI + physics per frame. - Spread expensive updates over multiple frames (tick-scheduling). =====
# GPU-limited mechanics - Keep triangle count ≤ ~10–15M on screen. - Avoid >2k × 2 shadow maps per frame. - Limit full-screen post-process passes to ≤ 2 ms.
# Scaling - LOD reduces geometry & animation cost with distance. - Streaming reduces memory footprint; chunk updates amortized over frames.

If you want, I can overlay this diagram with memory/VRAM budgets so you get a full CPU+GPU+RAM/VRAM constraint table for every mechanic on this exact system. That gives a complete “design on paper” blueprint.