Disabled Marmalade's auto chromakeying of RBG ff00ff pixels in textures. - #3
Open
MickW8s wants to merge 1 commit into
Open
Disabled Marmalade's auto chromakeying of RBG ff00ff pixels in textures.#3MickW8s wants to merge 1 commit into
MickW8s wants to merge 1 commit into
Conversation
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.
Marmalade documentation states that textures with 1bit alpha will auto chromakey any RGB ff00ff pixels, but in all recent versions of Marmalade, it is performed on any texture.
I'm guessing you won't want this engine specific behaviour in your Marmalade impls, at least not enabled by default.