VulkanScope

• VulkanScope 0.41.3 is a cumulative release covering the user-visible, Vulkan-query, analysis, reporting, safety and compatibility changes introduced after 0.35.1. Build/compilation-only fixes are intentionally excluded from these notes.
• Highlights
• Added a dedicated Analysis workspace for offline snapshot comparison, regression inspection, minimum/profile evaluation, dependency analysis, watched evidence, sharing and optional isolated Vulkan self-tests. Added richer format and extension inspection, including selected-format Image Format Properties2 drill-down and registry-reference metadata. Added bounded Vulkan extension dependency-graph analysis with separate registry-reference and runtime-evidence presentation. Added a diagnostic evidence score based only on explicit collector errors and safety rejections. Added local QR/permalink sharing for official VulkanScope Database reports without adding a runtime QR/network service. Hardened Vulkan enumeration and multi-stage query handling against driver-controlled count changes, incomplete results and unsafe second-stage results. Improved Surface/WSI enumeration completeness tracking and reporting. Strengthened Turnip/imported-driver validation and Android compatibility. Clarified Properties & Limits totals so safety diagnostics are not presented as newly added Vulkan properties. Corrected queue-family and Vulkan Video support/availability semantics and canonical zero-mask presentation. Preserved Vulkan 1.4.360, Database schema 2 and technicalReport schema 3.
• Analysis and comparison
• A new Analysis page provides local, evidence-based inspection tools without changing the canonical Vulkan capability report.
• Snapshot comparison
• Added export/import of bounded VulkanScopeAnalysisSnapshot1 snapshots. Added offline comparison of a saved baseline against the current device/driver report. Added searchable lazy diff presentation without the previous fixed row truncation. Difference/regression labels describe evidence changes only and are not conformance or performance judgments. Snapshot parsing validates schema, total size, entry count, key length and value length before use. Snapshot export reports failures explicitly and does not silently truncate oversized data. Minimums and profile analysis Added minimum/profile evaluation by reusing VulkanScope's existing profile evidence. Unknown or unavailable evidence remains UNKNOWN; missing information is not converted to unsupported. Watched evidence Added a persistent local watch list for selected capability/evidence tokens. Watch-list storage remains local to the application. The list is bounded to 256 entries. Registry dependency analysis Added a generated Khronos registry extension-reference catalog. Added extension dependency/reference inspection using embedded registry metadata. Added cycle-safe dependency traversal bounded to four levels and 64 unique nodes. Added a visual dependency graph bounded to 24 nodes for legibility while retaining the complete bounded textual traversal. Registry dependency relationships are shown separately from runtime extension enumeration and dedicated query-handler evidence. Registry metadata never fabricates runtime support. Missing embedded registry fields remain explicitly unavailable. Extension detail views retain access to the authoritative Khronos extension page. Release verification now checks query-handler/reference-catalog parity.
• Extension and format inspection
• Extensions
• Added richer extension details, including: runtime enumeration evidence, dedicated query-handler evidence, registry dependency/reference metadata. handler:true is derived from VulkanScope's actual query map together with checked-in reference metadata rather than guessed support. Formats Added selected-format Image Format Properties2 drill-down using already-collected runtime evidence. Preserved 64-bit VkFormatProperties3 / VkFormatFeatureFlags2 data as authoritative when available. Legacy 32-bit format-feature values remain fallback evidence only. Format detail presentation does not infer missing Image Format Properties2 results. Optional isolated Vulkan self-tests Added explicit, user-triggered self-tests through the isolated Vulkan probe for:
• minimal VkDevice creation, minimal SPIR-V shader-module creation, minimal pipeline-layout creation, minimal compute-pipeline creation. Self-tests:
• use the currently selected Vulkan driver path, require no optional Vulkan feature or extension, do not dispatch GPU work, create only the minimal required Vulkan objects, run only when matching destruction paths are available, report unavailable safe paths as UNAVAILABLE rather than guessing success or support, preserve deterministic ownership and cleanup behavior. These tests are diagnostics only and do not alter the normal capability collection result.
• Vulkan query safety and correctness Hardened second-stage count handling for driver-controlled Vulkan enumerations. Added capacity revalidation before indexing/resizing second-stage results. Hardened applicable enumeration paths including: device extensions, physical devices, queue families, Vulkan tools, Vulkan Video formats, device groups, Surface formats, Surface present modes, cooperative-matrix properties, Sparse Image Format Properties2. Partial VK_INCOMPLETE data remains positive partial evidence and is not converted to unsupported. Failed second-stage cooperative-matrix results are no longer emitted as though complete. Sparse Image Format Properties2 revalidates returned counts before indexing. Vulkan Video and Vulkan Tool partial enumerations preserve incompleteness provenance. Fixed Sparse Image Format Properties2 safety-rejection JSON serialization. Native queue, memory and Surface safety-rejection evidence is preserved through the UI and detailed report pipeline.
• Surface / WSI
• Surface format and present-mode enumeration now use bounded retry-aware helpers. Added dedicated safety limits and second-stage capacity validation. Added explicit enumeration-completeness state. Surface completeness information propagates through the normal Surface capability data and report paths. Partial Surface results remain partial positive evidence. Missing or incomplete Surface data is not automatically interpreted as unsupported. Surface format rows are lazy-rendered for large result sets.
• Properties & Limits evidence semantics
• The complete detailed-property pipeline now distinguishes normal Vulkan property/query evidence from mandatory query-safety diagnostics.
• The four Vulkan Query Safety rows are retained for: queue-family enumeration, memory-heap count, memory-type count, Surface queue-family enumeration. Totals are now labeled separately as: total evidence rows, Vulkan property/query rows, safety diagnostics, unique report fields / property names, limits. A total such as 1473 evidence rows is therefore not presented as 1473 Vulkan properties; the underlying split remains 1469 property/query rows + 4 safety diagnostics. UI, TXT and HTML use the clarified evidence-count semantics.
• Queue-family and Vulkan Video semantics
• Queue capability booleans remain direct evidence from VkQueueFamilyProperties::queueFlags. A zero VkQueueFlags value is displayed as zero queue capability bits and is no longer labeled with a nonexistent generic VK_NONE. Corrected the Vulkan 1.4.360 known queue-bit mask from 0x577 to 0x57F, so VK_QUEUE_SPARSE_BINDING_BIT is not duplicated as an unknown bit. VkQueueFamilyVideoPropertiesKHR query availability is now tracked independently per queue family. A successfully queried zero VkVideoCodecOperationFlagsKHR value is displayed canonically as VK_VIDEO_CODEC_OPERATION_NONE_KHR. When VK_KHR_video_queue is absent, the video-codec-operation query is Not applicable. Failed or missing video-property query evidence remains Unavailable or Unknown rather than being inferred as unsupported. Queue UI, TXT, HTML and Database technicalReport now carry the same video-codec query state and reason. Turnip / imported-driver hardening Installed Turnip bundle resolution is now metadata-authoritative. A valid installed bundle requires: exactly one bounded meta.json, schemaVersion 1, exactly one declared Vulkan .so, exact containment inside the app-private driver path, a readable, non-empty declared library. The previous arbitrary first-.so fallback is no longer used. ZIP import remains bounded by: entry count, per-file size, aggregate extracted size, path length, canonical extraction containment. Turnip import is gated to Android 9+ arm64-v8a together with the existing runtime support checks.
• Android compatibility and probe lifecycle
• Probe-result publication no longer depends on java.nio.file, preserving VulkanScope's Android API 24 support. Probe results are published through bounded UTF-8 output, flush/sync and app-private atomic rename behavior. Temporary publication files are removed after publication failure. Probe result reads use bounded streaming reads up to the defined 64 MiB result limit. Destroying the Activity terminates any still-running isolated Vulkan probe process after lifecycle cancellation. Isolated Surface ownership and process shutdown remain deterministic.
• Diagnostic evidence score
• Added a local diagnostic evidence score based only on explicit collector errors and query-safety rejections. The score is not a Vulkan conformance result. It is not a benchmark, performance score, GPU-quality score or hardware ranking. Missing capability evidence is not treated as a negative score by inference. Database permalink and QR sharing Added official VulkanScope Database permalink presentation and local QR generation. QR encoding is performed locally. No remote QR-generation endpoint, analytics endpoint or automatic report upload was added. Database URLs remain fixed to the official HTTPS origin. Report identifiers are validated as lowercase SHA-256 hexadecimal identifiers. Reporting and Database compatibility UI, TXT, self-contained HTML and Database technicalReport continue to use the same underlying collected evidence. Analysis features do not change canonical Vulkan capability semantics. Surface completeness, query-safety diagnostics and queue/video query states propagate consistently through applicable report paths. Database submission remains explicit and complete-report based. No automatic/background report submission was introduced. Canonical schemas remain: Database submission schema: 2 technicalReport schema: 3
• Specification and provenance
• Published/query Vulkan baseline remains 1.4.360. Corrected stale active native checkpoint provenance from 1.4.357 to 1.4.360. The Vulkan-Headers field-coverage generator now requires header revision 360. Runtime capability decisions continue to use actual Vulkan API/extension/query evidence rather than GPU-name, vendor, Android-version or marketing inference.

Write a review