Update 17: switching, favorites and bindings
The official note lists R on keyboard and B on gamepad for switching between an equipped weapon and a spell. PC number keys 1–8 are now hotkeys. The quick-options wheel selects favorited weapons, rather than the equipped-weapon list; tapping the relevant control toggles sheathing.
Autorun is listed as Q on keyboard. There is no default gamepad autorun binding in the note, but one can be assigned. The previous equip system remains an option at the bottom of Gameplay settings. These are patch-note defaults, not a guarantee about a remapped layout or every Steam Input profile.
Update 17 multiplayer and companion changes
NerveLabs reports improved online stability and alerts when either host or client disconnects. The patch also addresses missing Amphitheater ghosts after delayed co-op quest loading. These are specific developer-reported changes, not proof that every save, connection or quest-state issue has disappeared.
Companions no longer react to player crimes, and a case where dismissed companions failed to appear received a fix. This does not remove guards or the evidence-chest crime system, nor does it establish new party-size or cross-play rules. The separate host-world and guest-character model introduced in Update 16 remains the documented starting point.
Current issue evidence states
| Status | Evidence | Limits |
|---|---|---|
| Officially fixed / addressed | Update 17: bow camera, shields, missing fast travel, dismissal and delayed co-op ghosts | Not independently reproduced by this site |
| Officially changed | Rolling removed for now; restoration over time; unknown shared effects hidden | Do not classify intended behavior as a bug |
| Potentially present | Update 8 low-VRAM texture-loss caveat at high settings | No blanket hardware fix claimed |
| Historical regression addressed | Hotfix 10 addressed the prior hotfix's temporary performance regression | Not presented as a permanent current regression |
| Community report / unconfirmed | Control and save complaints require a directly attributable record | No verified current report or site reproduction claimed here |
Changed in Update 17
This page was compared with the official Update 17 announcement on September 25, 2026. The changes above are developer-reported; details requiring in-game testing remain explicitly unresolved.
Record a useful current report
- Update number and Steam build
- Save age and whether the behavior began before an update
- Solo, host, guest or split-screen role
- Exact location, objective and reproduction steps
- Hardware and settings when performance or texture behavior is involved
Evidence boundary
Exact values, requirements and edge cases stay marked as unverified until they can be checked in the current build.
Issues addressed in official notes
An official fixed or addressed entry records developer action in that build. It does not prove that a similar-looking symptom in Update 16 has the same cause or is resolved for every save.
| Area | Current status | Official patch context |
|---|---|---|
| Camera | Addressed by official patches | Hotfix 9 camera fixes; Hotfix 10 further camera improvements |
| Performance regression | Fixed in Hotfix 10 · temporary regression | Hotfix 10 says it fixed the regression introduced by the previous hotfix |
| Textures and VRAM | Still potentially present at higher graphics settings | Update 8 added low-VRAM texture-loss protection but retained this explicit limitation |
| Quest direction | Addressed in official updates | Update 7 and Update 8 improved directions; current stalls still require build- and save-specific evidence |
| POI and map | Current official behavior | Update 7 added POIs and quest areas; Hotfixes 9 and 10 added POI fast travel under Accessibility |
| Multiplayer | Addressed in earlier official patches | Hotfix 4 stability work; Update 6 inventory, quest-state and progress-wipe fixes |
| Co-op quest autosave | Officially addressed in Update 11 | Autosave not storing quest state in co-op was fixed |
| Console input lock | Officially addressed in Update 11 | Console input no longer locks when another window is open |
| Third-person spell targeting | Officially addressed in Update 11 | Third-person spells now target correctly |
| Fire spellcrafting damage | Officially addressed in Update 11 | Fire spellcrafting now gives correct damage |
| Spellcrafting dropdown color | Officially addressed in Update 11 | Dropdown colors were corrected |
How to read a current community report
Steam Community discussions can show that a player experienced a symptom in a named build. They do not establish prevalence, cause or a universal workaround without repeatable current-build evidence.
Check the report date, game build, save age, host or non-host role and hardware context. Keep the observation attributed to the reporting player until it can be independently reproduced.
Triage a quest that will not advance
- Read the newest journal objective and compare it with any Update 7 map area.
- Confirm the relevant item, NPC or POI is being checked on Update 16.
- Record whether the save began before the patch tied to the quest fix.
- Reload a recoverable save before the suspected state change when available.
- Report the exact quest name and objective text without guessing at an internal stage number.
Triage performance or co-op symptoms
For performance, capture the GPU model, VRAM, driver and whether disabling shadows changes a repeatable scene. For co-op, capture host status, which inventory or quest state differs and whether the same character behaves differently in single player.
These details connect a report to the categories addressed by official patches without declaring that an older bug has returned.
How issue states are classified
No unsupported master bug list, guaranteed workaround or invented internal quest command is published here. Earlier reports were checked against Update 16 on September 13, 2026; new reports require the current installed build.
Original guide diagram
Issue classification
Separate Fixed, Mitigated and Reported
- FixedThe official note names a completed correction.
- MitigatedThe symptom can still occur under stated conditions.
- ReportedA player observation still needs current-build reproduction.
- UnknownThe registered record does not establish the behavior.