Skip to content

feat: roll in Frank's overlay-support updates#2

Merged
xXJSONDeruloXx merged 4 commits into
releasefrom
feat/overlay-support-rollup
May 13, 2026
Merged

feat: roll in Frank's overlay-support updates#2
xXJSONDeruloXx merged 4 commits into
releasefrom
feat/overlay-support-rollup

Conversation

@xXJSONDeruloXx

Copy link
Copy Markdown
Collaborator

Summary

  • cherry-pick the 3 commits from FrankBarretta/lsfg-vk-android@overlay-support
  • improve Android device feature probing/logging and add a framegen build stamp
  • add a vkCmdPipelineBarrier2 compatibility shim for older Vulkan devices

Source

Validation

  • cmake -S . -B build-pr-check
  • cmake --build build-pr-check -j8 (environment stops early here because local Vulkan headers are not installed: vulkan/vulkan.h not found)

FrankBarretta and others added 4 commits May 13, 2026 10:31
…ebug

Adds an unmistakable INFO line at the very start of Device::Device that
prints a build timestamp (__DATE__ __TIME__). When a user reports
DEVICE_LOST on Mali and this line is missing from logcat, that
unambiguously means CMake reused a cached lsfg-vk-framegen.a — the actual
storage-image-features fix is not on the device. The build stamp variable
is referenced from Device::Device so the linker can't dead-strip it.

Also adds a hard WARN-level log when the physical device reports
shaderStorageImageExtendedFormats=FALSE. That feature is what the LSFG
compute chain needs for R16G16B16A16_SFLOAT storage image access; without
it, dispatch is undefined behavior and the queue dies on first present.
This is a runtime confirmation of the root cause, not a fix — the
DEVICE_LOST warning text points future debug effort at shader rework, not
device-creation tweaks.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@xXJSONDeruloXx xXJSONDeruloXx merged commit 5afac86 into release May 13, 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.

2 participants