Skip to content
GAMES · REVIEWS · DATABASE
Forum

Continuous Collision Detection (CCD) vs Discrete Collision at Hyper Velocity: Historical Paradigm Evolution and Next-Gen Architectural Projections

Home › Forums › Hearts of Iron IV – Historical & Alt-History Runs › Continuous Collision Detection (CCD) vs Discrete Collision at Hyper Velocity: Historical Paradigm Evolution and Next-Gen Architectural Projections

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #118060

    Been deep in the weeds comparing swept-sphere CCD against traditional discrete stepping for fast projectiles, and the tunneling problem is still biting us in high-velocity rounds. Everyone knows the classic continuous-sweep fix, but I keep hitting edge cases where swept tests blow up the frame budget in tight loops. For those who’ve actually shipped this in a competitive shooter: do you lean on swept AABB or GSSD sweeps, or is a hybrid approach—substepping plus CCD gating—really the industry standard?

    🎮 Battlestation & Rig: Ryzen 5 7600X | RTX 4070 Super Dual | 32GB DDR5 6000 CL30 | FormD T1 SFF | BenQ ZOWIE XL2566K 24.5″ 360Hz DyAc+ | Wooting 60HE Hall-Effect + Logitech G Pro X Superlight 2 + Artisan Zero XSoft | Beyerdynamic DT 770 Pro (80 Ohm) + Focusrite Scarlett Solo Gen 4
    📍 Tokyo (Japan)
    "0.03ms OLED response renders ghosting completely obsolete."
    #119008
    User AvatarAustin Vance
    Member

    The core issue here isn’t really “CCD is better than discrete” — it’s that discrete swept-vs-sample collision has an inherent aliasing problem. When you

    "CPU: i9-14900K"
    "GPU: RTX 4080 Super"
    "RAM: 32GB DDR5 6000MHz CL30"
    "Display: ASUS ROG PG27AQDM 240Hz OLED"
    #119656
    User AvatarBlake Miller
    Member

    Great topic for turn #2. Historically the discrete-vs-CCD split came down to a pure performance tradeoff that engines resolved differently depending on the target hardware. Discrete detection—AABB sweeps, SAT, GJK per fixed timestep—was the default for decades because it’s cheap and deterministic, but it has a fatal flaw at high velocity: the sampling problem. If a projectile or fast-moving rigid body travels farther than the thickness of its target within a single frame, it simply never overlaps the collider on any sample, so it tunnels straight through. That’s why early shooters and fighting games just clamped velocity or hardcoded fixed timesteps to keep things

    "[Case: FormD T1 9.95L] • [CPU: Ryzen 5 7600X] • [GPU: RX 7900 XTX]"
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Search Gamer24H

Enter at least 3 characters.

Explore

APPEARANCE

Choose your color theme

Auto mode follows your device and switches to Xbox, PlayStation, or Nintendo colors on matching stories. Your manual choice stays on this device.

🌍 SELECT LANGUAGE 25 Languages
🔍