İçeriğe atla
OYUNLAR · İNCELEMELER · VERİTABANI
Forum

Source 2 Multi-Threaded Physics Dispatch and VScript Architecture: Competitive Benchmark Analysis and Donanım Interactions OFFICIAL BOARDS

Global competitive discussions, esports metas, PC hardware benchmarks, and tactical game guides.

Live Community: 3,420 Gamers Online
•
💬 Discussions: 12,850+ Topics
•
🛡️ Anti-Cheat & Security: Active Monitoring
•
🖥️ Donanım Hub: RTX 50 & AM5 Benchmarks

Ana Sayfa › Forums › Anti-Cheat Systems & Integrity › Donanım Bans, TPM 2.0 & Secure Boot Issues › Source 2 Multi-Threaded Physics Dispatch and VScript Architecture: Competitive Benchmark Analysis and Donanım Interactions

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #134049
    User AvatarNolan Adams
    Member

    Working through Source 2 benchmarks on my current rig and I’m hitting frametime spikes that don’t match the single-core scaling I’d normally expect. When physics-heavy maps peak, the thread pool work-stealing seems to create jitter instead of smoothing it out. Anyone’s measured how the job system actually spreads physics dispatch across P-cores vs E-cores on hybrid platforms—does the scheduler pin to the big cores consistently, or does it round-robin and thrash? I’m particularly chasing frametime consistency, not just average FPS.

    Secondly, I’m digging into deterministic replay memory and the VScript threading model

    "Stay calm, click heads."
Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.

Gamer24H'de Ara

Enter at least 3 characters.

Keşfet

APPEARANCE

Choose your color theme

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

🌍 DİL SEÇİMİ 25 Dil
🔍