Commit graph

6 commits

Author SHA1 Message Date
3f09c7cf3f fix(visuals): measure the skull's facing from the bind pose, for all three clawed races
The eye frame was read from the head bone's pose ON THE FRAME THE EYES
WERE BUILT, snapped to the nearest axis, then cached for the life of the
eyes. Catch the head a few degrees into a turn and the snap picks the
neighbouring axis, and the pair stays wrong until something rebuilds it.

Each race met this separately and each added the same guard - do not
build while attached, mid-attack or asleep - which caught the loud cases
and left the quiet one: a race change rebuilds while the rig is still
settling, which is none of those three. That is why resetting into a
race could break the placement while logging out and back in silently
fixed it. The logout was never a fix, only a rebuild at a calmer moment,
and no fourth guard condition would have closed it - the read itself had
to stop depending on when it happens.

sharedMesh.bindposes[headBone] is the rig as authored: no animation in
it, no timing, the same answer on frame one and frame ten thousand. A
rebuild is now deterministic and a bad moment cannot exist. Falls back to
the live read, warning once, on a rig that carries no bind pose.

Lives in one shared RigBindPose rather than in three copies. The three
eye implementations are separate files by design - they differ in what
they hang and how it is coloured - but this is the one piece of maths
where a divergence would be a bug in whichever copy got fixed second,
and it had already been fixed twice. The three now-dead private
SnapToAxis copies go with it.

Also updates the Aswid eye defaults to the values dialled in on screen:
forward 0.013, height 0.004, yaw 22.068.
2026-08-12 17:33:46 +02:00
cb69d3af3e fix(aswid): land the borrowed eye sockets on the face, and make the sliders able to say so
Scale is inherited, so source.localScale could not come across either:
it is authored under a parent that puts the object at 0.02 lossy scale,
and re-parenting it under a head bone at ~95 drew the mesh some 4750x
too big - an eye the size of the character, centred near the face,
therefore mostly inside the skull with the corners reading as flat
rectangles. "Wrong place" and "blocky" were one scale error seen from
two angles. Carries lossyScale (the size the game actually draws it at
on a real skeleton) over the new parent's scale instead.

The remaining offset would not compute cleanly from either rig, so it
was dialled in on screen and written down as the new defaults rather
than guessed at again - size 1.1, forward 0.01, separation 0.007, yaw
24.664, roll -180 (the socket arrives upside down on a player's head
bone; that is the half turn that rights it).

The sliders that found those numbers could not have: they were bound at
+/-0.1 m and 0.1-5x, nowhere near far enough to pull the pair out of the
skull, so they read as doing nothing at all. Widened to +/-0.5 m and
0.01-50x.

Eye Rotation Y is now mirrored - the left eye takes the negative - so
the pair toes in or out together instead of both turning off the same
shoulder. X and Z stay shared on purpose: both eyes pitching up is a
face looking up, where mirroring pitch or roll would cross them.

Confirmed correct in game.
2026-08-12 16:25:51 +02:00
58f70f1a4c Merge branch 'war-vulture' into main
Brings in the Sverm race, the War Vulture flying mount, and Skadi's
Crystal Golem (replacing the Hidden Hollow). Resolved conflicts:
AswidVisuals.cs took war-vulture's skeleton-eye-light rewrite with
main's attach/attack/sleep timing guard re-applied on top, and
RaceCompendium.cs kept main's rewritten race entries while folding in
war-vulture's Sverm/War Vulture pages and the new Claws paragraphs for
Aswid and Fenrir.
2026-08-11 20:35:48 +02:00
Ferdinando
1c4b20bb06 warvulture 2026-08-11 19:29:58 +02:00
9e4778def7 feat(aswid): let players toggle the Vampiric Aura, move Devour off I
The Vampiric Aura had no on/off switch - it always drains/executes
nearby targets in every form. I now toggles it (AswidRace.AuraEnabled,
on by default), matching the existing toggle pattern already used for
Devour.

Devour's own toggle moves off I to make room and stays on by default;
its keybind is unbound (KeyCode.None) rather than removed outright, so
it remains a real Configuration Manager entry for anyone who wants to
bind their own key to it.
2026-08-09 17:11:25 +02:00
629a534bc3 feat(aswid): make abilities and special attacks BepInEx-configurable
Adds AswidConfig.cs, following the SkadiConfig pattern: one Configuration
Manager section per topic (Keybinds, Passive Combat, Vampiric Aura,
Superhuman Senses, Eclipse, Devour, Domination), covering every tunable
number and all five ability keybinds (Bat Form, Mist Form, Eclipse, Tame,
Toggle Devour). Defaults match the previous hardcoded constants exactly.

Also fixes a real mismatch found along the way: the tame hover-text
hardcoded "[K] Tame" while the key that actually triggered taming was U.
Both now read the same configured Tame key, so the hint stays correct if
it's rebound.

Config sections are bound alphabetically by race (Aswid before Skadi) in
RacesOfValheim.Awake(), since Configuration Manager's category list
follows bind order.
2026-08-06 13:33:39 +02:00