Clarify memory tier alignment table: tier 11 includes 4 GB devices; Switch 2 reports as Tier 1 - #982
Open
smell-of-curry wants to merge 2 commits into
Open
Conversation
…inclusive) Co-authored-by: Cursor <cursoragent@cursor.com>
…tier alignment table Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
The Memory tier alignment table in
BuildingSubpacks.mdis ambiguous at the tier 1 / tier 2 boundary: it lists tier 1 as2-4 GBand tier 2 as4-5 GB, so a creator cannot tell which side a 4 GB device lands on. In practice, memory tier 11 covers devices up to and including 4 GB of RAM, and memory tier 12 starts strictly above 4 GB.This matters a lot for real content: 4 GB is one of the most common mobile RAM sizes (iPhone 13/13 mini, iPad 9th/10th gen, many Samsung A-series, etc.). We (PokeBedrock, a large Bedrock server) shipped a resource pack with a
memory_tier: 12sub-pack based on this table, expecting 4 GB devices to qualify, and a large portion of our mobile player base was unable to select that sub-pack at all. Device testing across dozens of player-reported devices confirmed the 4-GB-inclusive boundary on tier 11.Updated table
Changes
0row for low-end mobile devices below the Nintendo Switch class (under ~3 GB of RAM, memory tier ≤7). The Script API'sMemoryTierenum similarly starts atSuperLow = 0, so the 1-5 table left the lowest class of devices unrepresented.3-4 (4 GB included)and the tier 2 range as>4-5to make the 4 GB boundary explicit.Empirical data points
From direct testing with a two-sub-pack manifest (a 2D fallback at
memory_tier: 1and a full-3D sub-pack whosememory_tierwe varied):memory_tier: 9, could atmemory_tier: 8— tier 8 ≈ 3 GB.memory_tier: 12, could at 11 — 4 GB is included in tier 11, tier 12 is >4 GB.memory_tier: 12;memory_tier: 11allowed it to load the 3D models — it reports as an original Switch (Tier 1) device.Confirmed affected devices
Devices reported by players who could not select a
memory_tier: 12sub-pack, with RAM per model spec (ranges where the model shipped in multiple configurations):Note the 6-8 GB devices in this list: several of them still could not select the
memory_tier: 12sub-pack, which shows the reported memory tier is based on the memory budget the OS makes available to the game rather than the device's physical RAM — another reason the GB ranges in this table need explicit boundaries.