Repository navigation
Integrate Fleet Battler with the expanded SDK and qualify every sample - #31
Merged
Merged
Conversation
Record mesh uploads into caller-owned direct command lists, retain staging through fences, and convert LitCube to vertex/index buffers. Validate indexed and instanced pixels under WARP after early owner disposal.
Add fleet badges and the Proxima route planner, chart-only exploration, illustrated briefings, fleet readiness details, and a shared campaign clock. Load research from a validated catalog and resolve ring occlusion and stale constructor assignments.
Advance the campaign independently of the selected map, deliver actionable briefings on either view, and confirm one-way departures. Add the Proxima receiver mesh, signal pulse, illustration, and navigation glyphs. Exercise the package consumer’s DXC, WARP, and DirectML workload from its published output.
Use scout-led transfers and interactive fleet rosters. Synchronize Sol’s orbital periods and the campaign calendar. Add the drag-and-drop designer, data-backed hulls and modules, research doctrines, structure upgrades, naming, upkeep and pirate retreat decisions.
… 12 sample package dependencies
…on from MSVC platform defaults
atcarter714
marked this pull request as ready for review
November 18, 2026 16:56
This was referenced Nov 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This consolidates the latest Fleet Battler campaign branch and the expanded DirectX SDK into one solution. The renderer keeps indexed meshes, instancing, texture atlases, compute jobs, asset imports, and campaign progression while sharing the public native declarations and depth/stencil APIs.
Validation: qualification run 44350307091 passed all four jobs: Windows Debug/Release, Linux JIT/NativeAOT, and Windows JIT/NativeAOT plus WARP samples. Both Windows configurations rebuilt all 12 package-based samples and ran Fleet Battler for 14 frames with two resizes. The native fixture passed 2,298 checks with no live objects. WARP covered stencil readback, indexed meshes and textures, fleet views and traffic, resize, N-body, DXR, DirectML, and NativeAOT compute.
No Noesis dependency is introduced. Target-hardware validation, DirectStorage, and broader API/ABI parity work remain separate from this integration.