Skip to content

Use NwcIO 0.15.0 for autonomous RVT export - #272

Merged
mahach666 merged 1 commit into
mainfrom
codex/rvt-use-nwcio-0.15.0
Nov 19, 2026
Merged

mahach666 merged 1 commit into
mainfrom
codex/rvt-use-nwcio-0.15.0

Conversation

@mahach666

@mahach666 mahach666 commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

Use the exact NwcIO 0.15.0 NuGet package for the optional RVT-to-NWC tool. Remove the temporary project-reference switch and the conditional code path, so the normal RvtIO checkout can run --native.

Exercise the package-backed write and strict read in the existing native export test, including mesh ownership, material colour and cache units. The original preview and optional Windows adapter retain their existing entry points.

NwcIO release preparation: IOExtend/NwcIO#267.
Package: https://www.nuget.org/packages/NwcIO/0.15.0

Verification with the published package

  • Fresh restore from NuGet.org returned NwcIO 0.15.0 as a package on both target frameworks. The exporter output contained the corresponding DLLs from that restore.
  • In network-disabled Linux containers, the .NET 8 and .NET 10 exporters wrote the public Autodesk rst_basic_sample_project.rvt. Their respective cache files matched the accepted source-built outputs byte for byte.
  • Navisworks Manage 2027 opened both files and showed all 455 element IDs, including the 453 expected elements with geometry. The published NwcIO CLI reopened both files and matched all 484 mesh owners and 84,494 ordered triangles.
  • The original two-argument preview matched its baseline byte for byte. The full RvtIO solution passed on both target frameworks.

@mahach666
mahach666 merged commit a129378 into main Nov 19, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant