Skip to content

VulkanScope 0.80.15

Choose a tag to compare

View all tags
@EFIShell0 EFIShell0 released this 06 Sep 06:08
· 7 commits to main since this release
0.80.15
1bc5cb8

VulkanScope 0.80.15 consolidates the application, Vulkan reference, accessibility, reporting, Database integration and Material 3 Expressive work completed from 0.80.3 through 0.80.15.

This release keeps Vulkan runtime evidence separate from registry/reference metadata, preserves complete-report semantics, and substantially improves the application's usability across phones, tablets, Android TV, large text, RTL locales and different display sizes.

Highlights

  • Refined the application-wide Material 3 Expressive interface with responsive layouts, clearer hierarchy, improved dialogs and consistent shared components.
  • Reworked Format and Extension details into compact, responsive evidence dialogs that adapt to narrow displays, large text and long Vulkan identifiers.
  • Added activity-aware scroll boundary hints that appear only when useful, fade when scrolling stops and return when scrolling resumes.
  • Reworked Overview Explore and Quick access into width-aware layouts instead of fixed or horizontally clipped arrangements.
  • Improved TalkBack, large-text, RTL, system-font and Android TV behavior across the application.
  • Strengthened collection-result semantics so failed and incomplete collection states are not presented as successful results.
  • Moved the full Encyclopedia and Analysis workspace out of Overview into dedicated destinations while retaining compact entry points.
  • Updated the locked Vulkan Registry / Vulkan-Headers baseline to Vulkan 1.4.362 / header 362.
  • Expanded the registry-driven physical-device provider set to 304 Android-queryable providers.
  • Regenerated the offline Vulkan Encyclopedia to 842 commands, 6248 VK_* tokens, 2461 Vk* types and 476 extensions.
  • Retained 110 implemented physical-device structs / 104 runtime query groups and the bounded 47-profile Vulkan Video capability census.
  • Preserved Database submission schema 2 / technicalReport 3 and current compatibility with VulkanScope Database 0.39.27.

Material 3 Expressive and responsive UI

The UI has been re-audited and refined as one coherent Material 3 Expressive system rather than a collection of isolated screens.

Responsive Overview

  • Explore no longer relies on a horizontally clipped strip on narrow phones.
  • Quick access adapts its column count to available width instead of forcing a fixed four-column layout.
  • Layouts remain usable with enlarged Android display size and font scaling.
  • Important action titles and subtitles are allowed to wrap instead of being unnecessarily truncated.

Format and Extension details

  • Format and Extension rows expose a clear Details action rather than making the whole browse card behave like an implicit action.
  • Detail content uses a bounded Material dialog suitable for long Vulkan evidence.
  • Evidence is grouped into compact tonal cards with responsive label/value rows.
  • Long labels, identifiers and registry descriptions stack when needed instead of being forced into cramped columns.
  • Long values remain left-aligned and readable.
  • The dialog keeps a stable Close action while its technical body remains independently scrollable.
  • The layout is designed to remain usable across portrait, landscape, narrow screens, large text and long translated strings.

Scroll boundary hints

Shared scroll hints now behave consistently across applicable scrollable surfaces:

  • At the absolute top: only the Down hint is eligible.
  • In the middle: Up and Down are both eligible.
  • At the absolute bottom: only the Up hint is eligible.
  • Non-scrollable content shows no hints.
  • The Up hint overlays the upper part of the viewport.
  • The Down hint overlays the lower part of the viewport.
  • Hints no longer permanently reserve a side lane or reduce usable content width.
  • The arrows fade away after scrolling becomes idle and return when gesture, fling or programmatic scrolling resumes.

Encyclopedia and Analysis

Dedicated destinations

The complete Encyclopedia and Analysis workspace were moved out of the Overview feed into dedicated Overview-parent destinations.

Overview now keeps compact entry surfaces while large searchable/reference workspaces remain separate.

Encyclopedia reliability

  • Fixed malformed generated registry rows that could break Encyclopedia search.
  • Generated symbol parsing now fails closed when a row does not contain the expected fields.
  • Search results are rendered as proper top-level lazy items.
  • Registry/reference presence remains explicitly separate from selected-device runtime support.

Current offline reference corpus

The Vulkan 1.4.362 reference corpus contains:

  • 842 Vulkan commands
  • 6248 VK_* tokens
  • 2461 Vk* types
  • 476 registered extensions
  • 50 canonical VkResult entries

Large symbol searches remain bounded and local; no network dependency is introduced for the Encyclopedia.

Vulkan 1.4.362 registry update

The locked Vulkan Registry and Vulkan-Headers baseline advanced from Vulkan 1.4.361 to:

  • Vulkan 1.4.362
  • VK_HEADER_VERSION 362

Registry-driven Android physical-device coverage now includes 304 provider extensions, consisting of 299 stable + 5 provisional providers.

New validated provider coverage includes:

  • VK_KHR_pipeline_library_group_handles
  • VK_VALVE_buffer_device_address_allocation_alignment

The VALVE allocation-alignment path preserves applicable feature/property evidence including:

  • bufferDeviceAddressAllocationAlignment
  • maxBufferDeviceAddressAllocationAlignment

The explicit native query catalog remains:

  • 110 implemented physical-device structs
  • 104 runtime query groups

VulkanScope continues to gate queries using actual API/extension/runtime evidence rather than GPU names or marketing assumptions.

Vulkan Video

The bounded Vulkan Video reference/query model remains intact.

  • 47 exact profile combinations remain represented.
  • Exact profile evidence remains separate from broad codec claims.
  • Sampled format enumeration is not promoted into exhaustive format support.
  • Explicit Unavailable, Not applicable and Unknown evidence remains distinct.
  • Retained profile rows are not treated as proof of codec-wide hardware support.

Collection state and reliability

Collection-result presentation was tightened so success is not shown when the base report is invalid or incomplete.

A successful completed state requires meaningful completed report evidence.

A distinct Failed state is used for conditions such as:

  • fatal collection failure
  • timeout
  • incomplete base report
  • zero physical devices
  • all-empty / all-unknown device evidence

Optional or deferred query groups may still independently be Unknown, Unavailable or Not applicable without incorrectly turning an otherwise valid completed base report into a global failure.

The terminal Failed state remains visible until a new collection replaces it instead of disappearing like a transient success notification.

Accessibility and large-text support

Accessibility behavior was expanded throughout the interface.

TalkBack

  • Decorative elements no longer create unnecessary duplicate announcements.
  • Read-only key/value content uses merged semantics where appropriate.
  • Section and release-note headings expose heading semantics.
  • Collection and update state changes use accessibility live regions.
  • Driver-source choices expose a single RadioButton semantic target.
  • Direct GitHub update control exposes one Switch semantic target.

Large text and display scaling

Layouts now adapt to Android font scaling and enlarged display-size settings.

Applicable surfaces can:

  • stack Overview metrics
  • reduce or wrap Quick access columns
  • stack key/value metadata
  • stack Info metadata
  • grow navigation and action surfaces instead of clipping labels
  • wrap collection-status text
  • stack paired Info actions when horizontal space is insufficient

RTL, language and system fonts

VulkanScope retains Android RTL support while keeping technical identifiers readable.

  • Material typography uses content-aware text direction.
  • Latin and Vulkan identifiers remain naturally LTR under RTL system locales.
  • Arabic and Hebrew content can resolve RTL normally.
  • Layout continues to use relative Start/End positioning.
  • Raw Vulkan/report evidence is not modified with injected bidi control characters.
  • The application continues to use Android's platform/default sans family.
  • No bundled or downloadable custom UI font is required.
  • OEM and user-selected system-font substitution and platform glyph fallback remain available.

Android TV and D-pad navigation

TV navigation continues to use standard Compose focus and BringIntoView behavior instead of custom D-pad interception.

Improvements since 0.80.3 include:

  • Format and Extension browse rows participating in TV focus traversal.
  • Detail evidence remaining readable/focusable where appropriate.
  • Update release-note rows acting as read-only focus targets.
  • D-pad traversal naturally driving the standard scroll path.
  • Scroll-boundary feedback remaining consistent with touch layouts.

Update experience

The update UI retains the established Material 3 Expressive hierarchy while improving accessibility and presentation.

  • Update release notes support bounded scrolling with boundary feedback.
  • Release-note rows remain traversable on Android TV.
  • Update-available status uses an Info-style status icon rather than the older green update badge.
  • Update state announcements remain accessible.
  • Large-text layouts provide additional space instead of clipping critical actions or release information.

Database integration

Database submission remains explicit and complete-report based.

Current report compatibility remains:

  • Submission schema: 2
  • technicalReport schema: 3
  • Companion Database: VulkanScope Database 0.39.27

The Database compatibility line was progressively updated during this release series.

New submissions use the current supported producer contract while historical report semantics remain preserved.

The application continues to avoid silently truncating a complete technical report merely to make it fit the transport limit.

Runtime capability evidence, registry metadata and Database normalization remain separate evidence layers.

Evidence-state semantics

Throughout VulkanScope, these states remain intentionally distinct:

  • Supported
  • Unsupported
  • Available
  • Unavailable
  • Not applicable
  • Unknown / not queried
  • Incomplete where applicable

Missing or unqueried information is not silently converted into Unsupported.

Registry registration, symbol presence or reference metadata does not by itself prove runtime capability.

Assets 6
Loading