Skip to content

README: how draws reach the GPU, which Kotlin ships, and the glasses frame rate - #46

Merged
jpcottin merged 1 commit into
mainfrom
docs/readme-renderer-and-kotlin
Oct 24, 2026
Merged

jpcottin merged 1 commit into
mainfrom
docs/readme-renderer-and-kotlin

Conversation

@jpcottin

Copy link
Copy Markdown
Owner

The renderer uses no push constants: per-draw data travels as per-instance
vertex attributes and consecutive draws of one shape are batched into
instanced draws. GlassesGameActivity.kt is production Kotlin alongside
the bridge. The glasses loop is paced to about 34 fps, just above the
30 Hz panel, not 60. Rapid fire cuts the cooldown from 0.42 s to 0.20 s,
a little more than half.

…frame rate

The renderer uses no push constants: per-draw data travels as per-instance
vertex attributes and consecutive draws of one shape are batched into
instanced draws. GlassesGameActivity.kt is production Kotlin alongside
the bridge. The glasses loop is paced to about 34 fps, just above the
30 Hz panel, not 60. Rapid fire cuts the cooldown from 0.42 s to 0.20 s,
a little more than half.
@jpcottin
jpcottin merged commit 25aa67c into main Oct 24, 2026
21 checks passed
@jpcottin
jpcottin deleted the docs/readme-renderer-and-kotlin branch October 24, 2026 07:39
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