Feat/manage tile alloc #1505
Open
Feat/manage tile alloc #1505
Conversation
This file contains 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
For people who have some scenes that have more than 192 unique tiles (up to 256 in normal mode and up to 512 in color-only mode) and dont use the default ui system. issues fixed: - The background image compiler would cap at 192 unique tile, not allowing any way to have more tiles even with a plugin fix - Removed ALLOC_BKG_TILES_TOWARDS_SPR definition in the engine as the new allocation hard caps at 192 tiles
…ackground. By default its the same behaviour as GBS 4 which reserve tiles for its default ui and allocate BG tiles upwards in the shared tileset VRAM to prioritise sprite tile overflowing in it. Unchecking both options "Prioritize Sprite Allocation" and "Reserve UI Tiles" will have the same behaviour as GBS 3.
…te Allocation" is on or off.
# Conflicts: # src/lib/compiler/compileImages.ts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Feature: Allows the user to specify the tile allocation style for a background.
By default both options are checked and is the same behaviour as GBS 4 which reserve tiles for its default ui and allocate BG tiles upwards in the shared tileset VRAM to prioritise sprite tile overflowing in it.
Unchecking both options "Prioritize Sprite Allocation" and "Reserve UI Tiles" will have the same behaviour as GBS 3.
What is the current behavior? (You can also link to an open issue here)
Current behavior forces a certain tile allocation, making it hard to have control over the tileset VRAM
What is the new behavior (if this is a feature change)?
2 checkboxes are added under the background selection in a scene allowing to change tile allocation behavior.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No breaking changes should occur as the tile allocation will be the same as GBS 4 was by default.
Other information:
Some screenshots