Web: document dlink_enabled as the GDExtension tradeoff it is, not a requirement - #9
Open
octopusburrow wants to merge 1 commit into
Open
Web: document dlink_enabled as the GDExtension tradeoff it is, not a requirement#9octopusburrow wants to merge 1 commit into
octopusburrow wants to merge 1 commit into
Conversation
…requirement The README's single build command and the FAQ presented dlink_enabled=yes as required for the WebGPU export template. It is the engine's GDExtension switch (default off), and the WebGPU template builds and runs without it — verified end to end: compile, desktop rendering, and immersive-vr session entry on a non-dlink build. The cost of leaving it on for projects that ship no GDExtensions is real and user-visible: a split main+side module is larger than the monolithic build (50MB vs 43.5MB here), and the side module's link/relocation runs on the main thread AFTER the download bar completes — measured as ~10s of silent post-bar stall vs 2-3s for the monolithic build, whose compilation overlaps the download via streaming compile. Same total work, much worse distribution: the visible progress ends before the expensive step begins. Present both commands, defaults-first, with a per-flag tradeoff table (also covering opengl3/threads), matching upstream's model of shipping both template variants and selecting per-project via the export preset.
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
1 participant
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.
The README's single build command and the FAQ presented
dlink_enabled=yesas requiredfor the WebGPU export template. It is the engine's GDExtension switch (default off), and
the WebGPU template builds and runs without it — verified end to end: compile, desktop
rendering, and immersive-vr session entry on a non-dlink build.
The cost of leaving it on for projects that ship no GDExtensions is real and
user-visible: the split main+side module is larger than the monolithic build (50MB vs
43.5MB here), and the side module's link/relocation runs on the main thread AFTER the
download bar completes — measured as ~10s of silent post-bar stall vs 2–3s for the
monolithic build, whose compilation overlaps the download via streaming compile. Same
total work, much worse distribution: the visible progress ends before the expensive
step begins.
This presents both commands defaults-first with a per-flag tradeoff table (also covering
opengl3/threads), matching upstream's model of shipping both template variants and
selecting per-project via the export preset. Docs only; no code change.