It still crashes
Less than it did. When it does, the launcher now says whether the crash was ours or inside another mod, and names the mod. The ones we know are ours are below, each with what to do until it is fixed.
This is the real list, in the real order. Nothing on it is marked done because it was written down; things come off it when the people playing stop reporting them.
The road ahead
Ordered by what is worth fixing first, not by what is easiest. Everything else gets measured against these.
Everything else is decoration if the session ends at twenty minutes. The launcher now tells a crash of ours from a crash inside another mod, names the mod, and warns before Play when a setup is known to crash. The crashes that are ours are in the known issues below, each with what to do until it is fixed.
If you killed it, it is dead for them too; if they looted it, the chest is empty for you. NPCs that froze or multiplied around reconnects are fixed. In the build we are testing: quest scenes that both games play without talking over each other, things one player carries moving smoothly for the other, and downed NPCs getting up in both games. In progress: showing the other player sooner, with a delay that follows the connection instead of a fixed quarter of a second.
VR has gestures a flat game never had: reaching over your shoulder, holstering at your hip, grabbing something out of the air. In hand: your head nodding and looking up on your copy, the arrow on your friend's bow, and the fix for a body that turns with the head instead of with the hips. Next: pulling a living NPC that the other game runs, and feeling it in your hand when the other player grabs it.
Dragging a corpse works, and both players see it. A corpse lies in the same place in both worlds, and anyone can now drag one by grabbing it. Still to do: another player's body, and living NPCs, which your hand will pull in the game that runs them.
NPCs occasionally arrive below the ground they should be standing on. They are in sync, just in sync at the wrong height.
Blades that meet are felt, heard and seen by both players, the defender's screen decides whether a hit was parried, and only a weapon or a shield parries. In the build we are testing: blades that stop on each other instead of passing through, a swing into the other player's sword that sounds like steel rather than flesh, and the fix that brings swords back for anyone with a recent PLANCK. Still open: your own sword sometimes hitting where the blade is not.
Today
Current, specific, and not a formality. If you hit something that is not here, it is genuinely new. Send the log.
Less than it did. When it does, the launcher now says whether the crash was ours or inside another mod, and names the mod. The ones we know are ours are below, each with what to do until it is fixed.
It comes from the mod's own in-game menu. Saves made before it are fine, and there is nothing to change on your side.
Loading during the downed sequence, or right after it, can crash. Wait a few seconds after you are back on your feet.
A crash a moment after arriving somewhere far away, when copies of the other player's NPCs were left behind. Not seen since 3 October, but not proven fixed either. Travel together, or turn PLANCK off for co-op.
Once so far, on 17 October, in the fight with Alduin: the picture stopped, the music played on, and nothing crashed. From the next release the game writes down what it was doing when it freezes, and collect-logs takes that file. If it happens to you, send it.
On the current release, a recent PLANCK keeps the other player's body and sword out of the physics in your game, so blades never meet: no clash, and no parry. Fixed for the next release, and seen working in our own fights.
Parrying is new. The other player's copy sometimes holds no weapon, or holds a two-handed one in the wrong grip, and in one fight blocks counted on one side only; a fix for that is in testing. An arrow held in the hand before it is nocked is not shown yet.
An essential NPC knocked down in one game could stay down in the other, then slide along behind the real one once it got up. Fixed in the build we are testing; it comes with the next release.
Something one player carries can flicker, almost invisible, for the other, who then sometimes cannot pick it up. Fixed in the build we are testing, not yet seen in a real session.
With both of you near the same quest scene, lines cut each other off, subtitles vanish and the scene runs ahead. Fixed in the build we are testing, with a fix from Skyrim Together Reborn.
A corpse lies in the same place in both worlds, and anyone can now drag one. Another player's body, and living NPCs being moved, can still end up in different places, and a body one player has dragged sometimes cannot be grabbed by the other afterwards.
Synced correctly, standing in the wrong place. Mostly cosmetic, occasionally fatal to a fight.
Travel quickly and your follower may be several cells back. The client is relinquishing actors in cells the game unloaded, which is correct behaviour producing an incorrect-looking result.
Stand still and look around, and on the other screen your hips and legs turn with your head. Measured in a real session on 17 October; the fix is being built.
Hands sit a little low with the palms together, the legs do not walk or run when you move with the stick, and the face does not always look like the character.
When you get on a horse, the other player never sees you on it. Parked for now: it needs real reverse engineering of the VR game.
NPCs from a mod one of you lacks do not sync, and a character can look wrong to the other player: one player's orc arrived as a pale Nord with a black face. The same modlist avoids it, and the next release logs which part of a look failed to load.
Live since October 9, 2026, and not yet proven over a full session. If a friend cannot connect, forward the port or use Tailscale, as on the hosting page.
The launcher copies the files into Data, as before, and they do not show in Vortex's mod list. Updating Vortex fixes it.
Reported twice by the same player. Nothing in the mod touches the map indoors, and we do not know yet whether it is the mod at all.
Say yes when the launcher offers to send a crash report. Without the launcher, run collect-logs.bat in the mod's launcher folder: it leaves a zip on your Desktop with the client log, any crash dump and both build versions. That report is the difference between a fix this week and a theory this month.
Behind us
Not a changelog. The devlog is the changelog. Just the shape of the last few weeks.