Combat & survival
Check why a main-hand weapon is missing
Start with weapon type and the active set. The developer answered an invisible-long-sword dual-wield report by specifying two short swords, or a long sword with a shield. On 1.06, also distinguish an equipment-visibility choice from an unequipped weapon: that update added the ability to hide equipment, but does not document the exact visibility controls.
On this page
1. Is this an unsupported combination?
Read each item’s type. If you are combining a long sword with a short sword to get two swords, first use the documented short + short pair. This is the most specific answer to the October 23 report; calling it a rendering bug before checking the types skips the developer’s explanation.
2. Is the intended equipment drawn?
Check the currently held set rather than relying only on equipped inventory slots. The October 24 developer reply says switching weapons with R can put a weapon away. That is a dated PC statement, not a full current keyboard/controller binding table: use the controls actually shown in your build if they differ.
3. Did the appearance change on 1.06?
Update 1.06 announces equipment hiding. If your build exposes a visibility setting, inspect whether it was deliberately hidden and reverse only that choice before testing again. This is a diagnostic inference from the new feature; the patch note does not name a menu, hotkey, affected item slots or prove that hiding caused your symptom. We do not invent a toggle location.
4. Is the weapon missing—or is the character stuck in a pose?
The October 22 dual-short-sword report describes a block pose remaining on screen while attacks still hit. It is an animation/defense symptom, not the same thing as an invisible weapon. Update 1.05 explicitly lists its fix. Use the blocking guide for that branch.
If a valid, visible, drawn pair is still wrong
Keep your save. Record both item names/types, Demo/full edition, displayed version, input device and whether the model is absent or merely stuck. Include a screenshot if you choose to report it in the Steam discussion. There is no established all-purpose fix here; deleting progress, reinstalling or repeating an old pre-1.04 workaround is not supported by this evidence.
You have isolated the problem when…
You know whether it is a pair mismatch, a different active set, a visibility choice or an unresolved model/pose problem. If the supported pair appears after a change, keep that result separate from a claim that every missing-weapon bug is fixed.
Sources & version
Source-based explanation; no independent gameplay or file-transfer test. Original source dates retain their scope. Later notes establish the changes they explicitly describe; silence is not proof that every mechanic stayed identical.