Repository navigation
REDbridge 0.13.0
Windows x64 build of REDbridge 0.13.0. It is framework dependent, so it needs the .NET 10 runtime (winget install Microsoft.DotNet.Runtime.10).
Unzip it anywhere and point REDcode (redcode.bridgePath) or EDGEdeck (edgedeck.bridgePath) at REDbridge.exe, or let REDcode's Install REDbridge or EDGEdeck's Get REDbridge fetch it.
New
-
project.exportfor animation (part of issue #14, #14, for REDcode's animation viewer, step A2). Three newoptions, checked on game 2.5:rig(orrigs, a list) for a.mesh: the mesh skinned on that rig's skeleton, the whole skeleton in the GLB. A game path or a.rigfile on disk or underarchiveDir. Several rigs are joined into one skeleton. A body needs its deformations rig (a garment likely too, unverified),base\characters\base_entities\man_base\deformations_rigs\man_base_deformations.rig(orwoman_base), which has the animation bones (Root,Hips,Spine, ...) and the muscle bones. Addman_base.riginrigsfor the six bones only it has (LeftEye,RightEye,WeaponLeft,WeaponRight,Trajectory,reference_joint). A mesh with bones the rig lacks is refused with their names, where WolvenKit wrote a GLB that failed to save.appearancefor a.ent: one<name>.ent.glbwith the entity in that appearance (its name, the.appappearance's name, or"default"for the first). Every rig the entity's animated components name (a character's body, deformations and face rigs) is joined into one skeleton. Skinned meshes of the entity, its appearance and the appearance's parts are on it, with a morph target's base mesh unmorphed. Rigid meshes (a vehicle's body, doors, engine and steering wheel, a character's weapon) hang under the bone their slot names, so they follow it. The answer'sentitylists the appearance, the rigs, the joint count, each mesh with what it is on (skin,bone <name>, another component, orroot), and what was left out with why: the appearance's far proxy, which would cover the real meshes, components switched off in the appearance, and files not in the archives. A Trauma Team paramedic comes out as 22 meshes on 512 joints, an Archer Hella as 21 parts on 51.rootMotion: truefor an.anims: the root motion on theRootnode's translation and rotation channels, which WolvenKit's default export leaves out, so a clip moves through the scene. The clip'sextras.rootMotionTypethen names the encoding (TransformSplineSparseFrames,TransformLinearSparseFrames, ...); without it, it saysUnknown.
{ "method": "project.export", "params": { "file": "<project>/source/archive/ep1/characters/entities/corpo/corpo__ep1_traumateam_ma.ent", "archiveDir": "<project>/source/archive", "rawDir": "<project>/source/raw", "options": { "appearance": "corpo__traumateam_ma_paramedic__lvl1_01", "meshMaterials": false } } }
Other
- Not in this release from issue #14:
.animsimport,anims.infoand rig import, for EDGEfab later. Not done in an entity export: a skinned component's chunk mask (submeshes it hides; rigid ones keep theirs) and each component's mesh appearance; the materials are the mesh's own. A vehicle's shadow-only mesh (body_shadow) is kept, since nothing in the component marks it. - WolvenKit 10.0.0-beta.1's multi-mesh export fails without materials (it saves an empty material list). With
meshMaterials: false, REDbridge runs the same steps itself.
Built with WolvenKit 10.0.0-beta.1 from its NuGet packages. WolvenKit's source is https://github.com/WolvenKit/WolvenKit/tree/10.0.0-beta.1 (GPL-3.0), and the bridge's source is this repository.