OutWit.Controller.Render.Dcc 1.6.19

dotnet add package OutWit.Controller.Render.Dcc --version 1.6.19
                    
NuGet\Install-Package OutWit.Controller.Render.Dcc -Version 1.6.19
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="OutWit.Controller.Render.Dcc" Version="1.6.19" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="OutWit.Controller.Render.Dcc" Version="1.6.19" />
                    
Directory.Packages.props
<PackageReference Include="OutWit.Controller.Render.Dcc" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add OutWit.Controller.Render.Dcc --version 1.6.19
                    
#r "nuget: OutWit.Controller.Render.Dcc, 1.6.19"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package OutWit.Controller.Render.Dcc@1.6.19
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=OutWit.Controller.Render.Dcc&version=1.6.19
                    
Install as a Cake Addin
#tool nuget:?package=OutWit.Controller.Render.Dcc&version=1.6.19
                    
Install as a Cake Tool

OutWit.Controller.Render.Dcc

Host-only upstream DCC build controller for OmnibusCloud. Accepts a neutral DccScene payload, validates the scene contract, generates a Blender Python scene script (with a binary mesh sidecar for bulk data), and invokes Blender headlessly to produce a .blend file blob. Stays separate from OutWit.Controller.Render, which owns the downstream .blend validation, preflight, rendering, collection, and encoding stages.

Dependencies

  • OutWit.Controller.Variables (version 1.0.0 or higher)
  • OutWit.Controller.Render (version 1.23.0 or higher) — reuses the packaged Blender runtime from the Render controller for the .blend generation path.
  • OutWit.Controller.Render.Model (version 1.7.0 or higher) — wire cutover note: 1.7.0 flipped the scene-attachment type to MemoryPack VersionTolerant; payloads written against older Render.Model cannot be read by 1.6.18+ hosts and vice versa. Deploy hosts and initiators across that boundary together.

Activities

Activity Side Description
Render.BuildBlendFromDccScene Host Validates DccScene, prepares a normalized build input, materializes blob-backed attachments, generates a Blender scene script + binary sidecar, runs Blender headlessly (packing all images into the file), and returns the generated .blend blob.
Render.UnzipDccScene Host Decompresses a gzip-packed MemoryPack scene payload (the *Packed job scripts' input — payloads compress 6–10×). Decompression is capped at 1 GB.
Render.ClearScene Host Explicitly removes the source DccScene variable from the current pool after host-side build/preparation steps when the script author no longer needs it.

Variable Types

Type Description
DccScene Inline neutral DCC scene payload transported through MemoryPack/WitRPC (VersionTolerant end to end — a reflection test guards that every nested type stays tolerant).

Supported DCC subset

The Render.BuildBlendFromDccScene pass handles the following subset of the neutral DCC contract. Anything outside this list is rejected at validation time with a named contract error — the layer's design rule is fail fast and readable, never build a silently wrong scene.

Geometry

  • Any number of meshes; per-node transforms with keyframes.
  • Per-triangle scene-level material indices (multi-material) or a per-node material binding.
  • Primary + secondary UV layers, per-corner vertex colors.
  • Per-frame vertex deformation (shape-key sequences) for skinned/simulated meshes.
  • Render-time subdivision levels (Subsurf, clamped 0–6) and displacement with surface-relative height semantics.
  • Mesh bulk data (positions/normals/UVs/colors/indices/shape keys) travels in a binary sidecar the generated script reads back through numpy foreach_set — the conversion of a heavy scene runs in seconds, not tens of minutes.

Cameras

  • Multiple cameras with an active-camera selection; FOV, near/far clip, and depth-of-field; transform and property keyframes.

Lights

  • Point / spot / area / sun kinds with color, intensity, range, spot cone + blend, area sizes, cast-shadow flags.
  • 3ds Max "no decay" lights get a constant-falloff emulation node; photometric-unit normalization happens initiator-side.
  • Intensity/color/range/cone animation.

Materials

  • Principled surface: base color, metallic, roughness, IOR, transmission, emission, opacity with Blend/Clip/Hashed alpha modes, normal strength.
  • Texture slots: base color, roughness, metallic, normal/bump, opacity, displacement — with authored UV tiling/offset (and their animation).
  • Scalar/color/UV animation on all of the above; per-keyframe Bezier/Linear/Constant interpolation.

World / environment

  • Environment color or image (HDRI) with authored rotation; screen-mapped backdrop mode (visible to camera and in reflections); environment-as-light-source flag that suppresses the default light rig.

Attachments

  • Blob-backed image attachments are materialized into the build sandbox (path-traversal guarded) and packed into the .blend (pack_all), so the artifact is self-contained.
  • bpy.data.images.load is only ever handed a materialized attachment path inside the sandbox. A scene's raw client texture paths (SourcePath/RelativePath) are untrusted and never reach a load; referenced images are validated to have an attachment, and an image asset without one — always unreferenced — is skipped rather than loaded, so a crafted scene cannot read an arbitrary host file (or open an outbound UNC connection) via pack_all.

Operational bounds

  • Render.UnzipDccScene caps decompression at 1 GB (gzip-bomb guard; ~6× the heaviest verified scene).
  • The Blender build carries a 30-minute wall-clock watchdog on top of job cancellation — a wedged process cannot hold a worker slot indefinitely.
  • The build sandbox is a per-job temp directory, cleaned on success and failure.

Usage example

Job:RenderDccSceneStillPacked(ByteCollection:packedScene, Variable:frame, RenderOptions:options)
{
    DccScene:scene = Render.UnzipDccScene(packedScene);
    Blob:blend = Render.BuildBlendFromDccScene(scene);
    Render.ClearScene(scene);
    ~ ... downstream: pass `blend` to Render.Frame / Render.Frames / Render.EncodeVideo ... ~
}

The bundled RenderDccScene*Packed scripts (still / tiled / frames / video / export-blend) ship in OutWit.Controller.Render.Dcc.Scripts; the export variant returns the built .blend itself as the job result.

Project structure

OutWit.Controller.Render.Dcc/
  Activities/          - WitActivityRenderBuildBlendFromDccScene, WitActivityRenderClearScene
  Adapters/            - matching adapters (host-only execution)
  Variables/           - WitVariableDccScene wrapper
  Services/            - DCC-side pipeline: validator, build-input factory, blend-file builder,
                       Blender-binary resolver, Blender Python script generator
  Models/Build/        - internal build-time DTOs (DccBlendBuildArtifact, DccSceneBuildInput)
  Properties/          - AssemblyInfo
  build/               - consumer-side MSBuild .targets shipped inside the nupkg
  WitControllerRenderDccModule.cs - plugin entry point (DI registrations)

OutWit.Controller.Render.Dcc.Model/
  Scene/, Geometry/, Cameras/, Lights/, Materials/, Textures/,
  Animation/, Metadata/, Values/     - shared DCC types split by domain

The companion OutWit.Controller.Render.Dcc.Model ships separately on NuGet so external tooling can reference the neutral DCC scene types (DccSceneData, DccMeshData, DccCameraData, etc.) without taking the host-only Dcc controller as a runtime dep.

Companion controller

See OutWit.Controller.Render for the downstream pipeline that consumes the generated .blend blob: frame rendering, video encoding, tiled stills, preflight validation, runtime diagnostics.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on OutWit.Controller.Render.Dcc:

Package Downloads
OutWit.Controller.Render.Dcc.Scripts

Bundled .wit scripts for the OutWit.Controller.Render.Dcc controller — typed-scene Render DCC orchestration (RenderDccSceneFrames, RenderDccSceneStill, RenderDccSceneStillTiled, RenderDccSceneVideo, RenderDccSceneExportBlend), plus *Packed variants that accept a gzip-packed scene payload and expand it via Render.UnzipDccScene before the build.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.6.19 319 7/12/2026
1.6.18 163 7/11/2026
1.6.17 138 7/10/2026
1.6.16 169 7/9/2026
1.6.15 137 7/9/2026
1.6.14 141 7/8/2026
1.6.13 136 7/8/2026
1.6.12 132 7/8/2026
1.6.11 140 7/8/2026
1.6.10 138 7/7/2026
1.6.9 131 7/7/2026
1.6.8 125 7/7/2026
1.6.7 140 7/7/2026
1.6.6 140 7/7/2026
1.6.5 131 7/7/2026
1.6.4 133 7/7/2026
1.6.3 137 7/6/2026
1.6.2 129 7/6/2026
1.6.1 134 7/6/2026
1.6.0 146 7/6/2026
Loading failed