WARDOGS vehicle and building bugs: stuck in a tree, swaying Z20 and structures you cannot remove

A Ural glued to a tree, a Z20 fishtailing above 250 km/h, stutters exactly when you drive into a fresh corner of the map for the first time, and structures outside the FOB that cannot be dismantled: these four reports are currently sitting in the Steam “Report a Problem” board and they cost real money in a match. We collect the confirmed state here, the official answers from Team17 Support and the workarounds that hold up in the field. Status: 22 September 2026.

Vehicle stuck in a tree, “Reposition” only oscillates

The sequence in the report: lost control of a Ural at around 70 km/h, slid into a tree, the vehicle wedges into the collision and jitters. The “Reposition” option was unusable because the vehicle alternated between jumping and standing still. Team17 Support passed the case to the development team; there is no fix yet, and a second player reported the same tree effect on the same day.

What you can still salvage in that situation:

• Get out first, then try “Reposition”. In the report the option was used from the seat while the collision was actively fighting back.
• Pull, do not push: a second vehicle can drag the Ural free if a teammate is nearby. Ramming it at speed usually just produces the next collision error.
• Save the cargo, write off the vehicle. Pallets and crates you can still unload are worth more than ten minutes of rescue attempts. If you carry explosives you can clear the wreck, but the vehicle is then gone for good.
• Prevention: ease off earlier on forest routes, and take the track on transport runs even when it is longer. The most expensive driving mistake is the one where the freight is stuck in the tree with you.

Report the case with vehicle, map, rough position and time. Those are exactly the details the team needs to reproduce the collision.

Z20 Lakota and Little Bird sway at high speed

One player describes the Z20 swaying sideways from around 250 km/h, the tail sliding out and the machine handling “like it is on ice” at times; the same effect later showed up on the Little Bird. The thread is instructive because it shows what has already been ruled out:

• Verifying the game files: fixed a second bug from the same reporter, but only slightly improved the sway.
• Unplugging unnecessary devices: support suspected a special keyboard detected as a gamepad. The reporter then tested on a plain mouse and keyboard setup and the sway remained.

So the topic is open. Until then the only help is flying inside the stable range: keep the speed below the threshold, start turns earlier, carry altitude as a reserve and plan approaches with room to spare. The Season 1 changelog from 9 September already lists a Z20 balance pass including a fix for sluggish pitch, so the flight model is being worked on. If you can reproduce the sway, report your input method, sensitivity and speed with it.

Stutters and freezes the first time you cross new ground

A category of its own that should be kept apart from the crash topic: the game stalls and briefly freezes as soon as you move in a vehicle at the start of a round, and inputs lock up while it does. In the report that ranges from a short stutter that pulls the car into the woods to freezes of several seconds that make you miss the exit from a helicopter. It gets better later in the round but comes back when entering unfamiliar areas.

The official sequence from the thread, in the order support gave it:

• Create a DxDiag and send it in so system errors become visible.
• Command prompt as administrator, run sfc /scannow.
• Turn V-Sync off and set the frame rate cap in the game instead.
• Enable G-Sync or FreeSync if your monitor supports it.

From the thread itself: rolling the Nvidia driver back to the previous Game Ready version reduced the severity of the stutters but did not remove them; frame caps and V-Sync variants did nothing for that reporter. The pattern fits terrain and shader streaming rather than a lack of frame rate. In practice that means: install the game on an SSD, let shader compilation run through once after every patch, drop view distance and texture quality by one step, and drive the first minutes of a round deliberately slower. Everything about crashes, video memory and the page file is in our crashes and performance article.

Structures outside the FOB cannot be dismantled

The report is short and unambiguous: anything built outside the FOB can no longer be removed, except with explosives. For recon tents in a bush, crooked sandbags or a wall on the wrong edge there is therefore no correction. An official answer is still pending in that thread, and we do not know whether this is a bug or a deliberate restriction.

Until that is settled, the rule for every piece is: rotate the preview and check the position, then place it. Plan in this order as well, so a misplacement costs the least:

• Load-bearing pieces first, then cover, small items such as sandbags and tents last.
• Keep clear of paths and entrances so your own construction does not block your vehicles later.
• In bushes and on slopes, step back and check from the player’s view instead of guessing from the build view.
• Anyone who plans a position before being in the match avoids the problem entirely. Our base builder and logistics planner exist for exactly that.

Our order in short

• Wedged in a tree: get out, then “Reposition”, otherwise get towed free, save the cargo, write off the vehicle.
• Swaying Z20: fly below the threshold, start turns earlier, report the case with input method and speed.
• Stutters in new areas: sfc /scannow, V-Sync off with a frame cap, G-Sync on, view distance and textures one step down, SSD and finished shaders.
• Building: rotate the preview and check the position, load-bearing pieces first, plan the position beforehand.
• Submit every report with vehicle, map, position, time and DxDiag.