Aardvark.Dom.Remote 1.1.6

There is a newer version of this package available.
See the version list below for details.
dotnet add package Aardvark.Dom.Remote --version 1.1.6
                    
NuGet\Install-Package Aardvark.Dom.Remote -Version 1.1.6
                    
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="Aardvark.Dom.Remote" Version="1.1.6" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Aardvark.Dom.Remote" Version="1.1.6" />
                    
Directory.Packages.props
<PackageReference Include="Aardvark.Dom.Remote" />
                    
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 Aardvark.Dom.Remote --version 1.1.6
                    
#r "nuget: Aardvark.Dom.Remote, 1.1.6"
                    
#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 Aardvark.Dom.Remote@1.1.6
                    
#: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=Aardvark.Dom.Remote&version=1.1.6
                    
Install as a Cake Addin
#tool nuget:?package=Aardvark.Dom.Remote&version=1.1.6
                    
Install as a Cake Tool

Aardvark is an open-source platform for visual computing, real-time graphics and visualization.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  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 (2)

Showing the top 2 NuGet packages that depend on Aardvark.Dom.Remote:

Package Downloads
Aardvark.Dom.Server

Aardvark is an open-source platform for visual computing, real-time graphics and visualization.

Aardworx.WebAssembly.Dom

WebAssembly libraries for Aardvark

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.1.9 150 5/19/2026
1.1.8 281 4/28/2026
1.1.7 224 4/28/2026
1.1.6 158 4/27/2026
1.1.5 182 4/26/2026
1.1.4 178 4/26/2026
1.1.3 174 4/26/2026
1.1.2 174 4/26/2026
1.1.1 169 4/26/2026
1.1.0 452 4/25/2026
1.0.25 202 4/15/2026
1.0.24 226 4/13/2026
1.0.23 573 11/20/2025
1.0.22 392 11/13/2025
1.0.21 328 11/9/2025
1.0.20 306 10/28/2025
1.0.19 293 10/28/2025
1.0.18 295 10/23/2025
1.0.17 417 10/22/2025
1.0.16 285 10/22/2025
Loading failed

refactored pick-chain selector to use FShade 5.7.4's `Effect.Dependencies`. The old logic gated mode A vs B on `Map.containsKey "PickViewPosition" eff.Outputs` (a coarse "does the user effect declare it?" check) and used `hasAllInputs` over a fully-linked module to test whether the with-normal variant was viable (one `Effect.toModule` call per draw setup). Both replaced by a pure-map analysis: for each pick-relevant semantic (`ViewSpaceNormal`, `PickViewPosition`, `PickPartIndex`) we ask "can the user's effect produce this with the geometry's actual vertex attributes?" via `EffectDeps.resolveTop`.
normal handling now has two paths, mirroring how pi/pvp work:
1. user effect produces `ViewSpaceNormal` (per-pixel pick normals — e.g. normal mapping) → use theirs, skip injection
2. geometry has `Normals` attribute → inject `viewSpaceNormalEffect` to synthesise vsn from the model normal
3. neither → no-normal variant
user effects that declare a pick output (e.g. `PickPartIndex`) but whose dep closure isn't satisfied by the geometry (e.g. they read `[<InstanceId>]` from a non-instanced render object) now degrade gracefully to the no-pi variant — previously this caused a silent attribute demand and "no buffer is bound to enabled attribute" at draw time.
extracted `PickShader.chooseChain` / `PickShader.composePickChain` as pure, public helpers; added `Aardvark.Dom.Tests` project with unit tests covering each branch of the selector + the FShade `Positions0` frag-input-renaming quirk.
requires FShade 5.7.4 (deps tracking is upstream).