EN
12 / Performance

Performance, Settings and the Body Camera

Why the frame rate drops, what Settings → Performance actually changes, how many soldiers your machine can carry, and what the browser build on this site can and cannot do.

DummyWar Dead Ground map with a scorched tree line and shell craters
DummyWar gameplay image · Performance
The short version
  • Set Settings → Performance to match your hardware.
  • Lower the live soldier count before lowering visual quality.
  • The browser build on this site is version 0.0.4; the PC release is 0.0.5.

DummyWar is not a demanding game because of its graphics. It is demanding because every soldier on the field is a simulated physical body running AI logic at the same time as everyone else. If the frame rate is poor, turning down visual quality is not the fix. Lowering the number of live soldiers is.

There is a second factor in a browser: the game has to be downloaded and run through Unity's web player instead of running natively. This guide covers what the developer says about performance, what the Settings menu can actually adjust, and what the new Body Camera effect does.

Why the frame rate drops

The developer has been explicit about the cause. DummyWar remains a relatively demanding game, and the main reason is not the graphics. It comes down to the complexity of the physics simulations handled by NVIDIA PhysX inside Unity, combined with the large number of AI calculations happening simultaneously.

Every character uses a complex physical model that requires continuous calculations. When large numbers of soldiers are present, the computational load increases significantly. A body that has to stay upright, absorb an impact, cross uneven ground and settle after a hit is doing work every frame, and the bots deciding what to do are doing their own work on top of that.

Version 0.0.5 put a lot of work into this side. The active ragdoll system received numerous improvements, making character movement more stable, natural and predictable. Previously characters could sometimes lose their balance because of minor obstacles such as small rocks or uneven terrain, and the likelihood of these situations has now been significantly reduced. The hand bone system and weapon interactions were reworked as well, fixing incorrect hand positioning, unnatural arm movements and the infamous "detached hands" effect.

Settings → Performance is not optional

The developer strongly recommends visiting Settings → Performance and adjusting the available options to match your hardware. Optimisation remains one of his highest priorities, which is why 0.0.5 includes extensive optimisation work, improvements to computational efficiency, fixes for issues affecting FPS and general stability enhancements.

He also says plainly that some technical limitations cannot be completely solved through conventional optimisation, and that he is experimenting with new approaches. He expects the update to noticeably improve performance, especially for players experiencing unexpectedly low FPS on powerful computers.

None of that removes your job. The defaults are not tuned to your machine. Open Settings → Performance before your first serious battle and set the options to what your hardware can hold.

How many soldiers to run

This is the number that actually matters. Every soldier is a full physics body with active ragdoll behaviour, so a large roster is expensive.

Dead bodies used to be expensive too. Earlier in development, dead characters were left partially active after they went down, which meant a long battle kept paying for bodies that were no longer moving. That was fixed, so corpses now cost far less than live soldiers.

The first battle guide recommends starting with about eight soldiers and only adding more once the first fight runs smoothly. On a slow machine, treat that number as the ceiling and treat every increase as something you earn by watching the frame rate hold.

What to change when the page is slow

The embedded build is a browser build. The download is roughly 430 MB and the game only starts when the visitor asks for it, so the page load is not the slow part — the moment the battle starts is.

  • Lower the soldier count first. It is the biggest lever you have and it costs you nothing but bodies.
  • Check that hardware acceleration is on. The game runs through Unity's web player, which needs the browser to be allowed to use the graphics hardware.
  • Use a desktop browser with a keyboard and mouse. The game expects them. There is no mobile version planned, and a desktop browser gives the clearest control experience.
  • Switch to fullscreen. It removes the browser chrome around the game and lets the view fill the display.

The body camera

Version 0.0.5 adds a Body Camera effect. You can enable it and customise where the camera sits on the character's body, and a dedicated settings section lets you adjust the placement until you find the perspective that works for you.

The developer describes it as a way to experiment with camera angles and produce more immersive, atmospheric and cinematic combat footage. The camera is one you place yourself rather than one the game picks for you, so the view is yours to compose.

Other toggles worth knowing

  • Motion capture animation — walking and running are based on motion capture layered over the physics body. It makes movement look more natural and characters trip over uneven ground far less often, and it can be disabled in the settings.
  • Hitmarker, compass and key hints — all three can be toggled in the settings.

The interface is still being worked on. Certain UI elements received a refreshed appearance and some menus and settings were reorganised in 0.0.5, but the developer notes that completely redesigning the interface is time-consuming given how many systems the game now contains, so not every part has been updated yet. The redesign will continue gradually, which is worth knowing before you hunt for a button that has moved.

Audio expectations

Sound from 0.0.4 onwards is handled by Steam Audio, which accounts for the surrounding space and the acoustics of the room you are in. Heavy-vehicle sounds came with the same update.

The developer also says calibration is ongoing, so audio issues may still occur. Treat an odd-sounding fight as a known issue rather than a sign that something is broken on your machine.

What the browser build gives you

The build embedded on this site is version 0.0.4, confirmed by reading the Unity loader configuration of the hosted build. The official Windows release is 0.0.5, a separate download.

That gap matters here. The Body Camera, the reworked hand and weapon interactions, the ragdoll improvements and the Russian localisation all arrive with 0.0.5, so if you cannot find them in the browser build, that is why. The optimisation work landed in the same release, which makes the Windows build the better option if the frame rate is your problem.

Where to go next