Replies: 1 comment 2 replies
-
@NB-NutBoi I converted this to a discussion The fact that camera.canvas is exposed seems unintended. this is not meant to be a "flixel feature" and, to my knowledge we have no intentions on adding support for this. Also i doubt this would work on all targets anyway However |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Tried to search everywhere for a solution but closest i got was a transparency issue, when i draw the camera canvas onto a new bitmap, all color transform info gets lost, i've tried every solution i could come up with and i only really found to turn blit rendering on, which is really slow, and to modify the FlxDrawQuadsItem class to directly apply the color transform to the bitmap rather than storing it in a shader, but that leads to ping-pong rendering if improperly done and is really slow, bringing performance down significantly, is there a better way to do this or is it an issue with openfl/flixel itself?
sample state to reproduce the issue
Observed behavior: The square in the game window is red, and the square in the generated .png is white
Expected behavior: Both squares should be red.
Beta Was this translation helpful? Give feedback.
All reactions