Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolution + RenderTexture Bug #1322

Closed
amadeus opened this issue Jan 5, 2015 · 2 comments
Closed

Resolution + RenderTexture Bug #1322

amadeus opened this issue Jan 5, 2015 · 2 comments
Labels
🕷 Bug Verified that it’s actually a legit bug that exists in the current release.
Milestone

Comments

@amadeus
Copy link
Contributor

amadeus commented Jan 5, 2015

I have found yet another issue when using the resolution property with RenderTexture class. I believe this issue may be somewhat related to issue #1215 since the results are somewhat the same (some botched transformations).

The premise is quite simple. I created a two sprites. One from an image, the other based on a RenderTexture that was rendered from the sprite.

If I leave the RenderTexture resolution to the default of 1, everything works as expected:

working example - resolution @ 1

However, if I change the resolution to 2 when I instantiate the RenderTexture, I get this result:

broken example - resolution @ 2

Here is the example fiddle, I left a comment on the line that can be played with:

http://jsfiddle.net/amadeus/s87s1c3w/

@englercj englercj added the 🕷 Bug Verified that it’s actually a legit bug that exists in the current release. label Jan 8, 2015
@englercj englercj added this to the v3.0 milestone Jan 8, 2015
@GoodBoyDigital
Copy link
Member

hi! Just tested this code with v3 and works like a champ in now. 👍

@lock
Copy link

lock bot commented Feb 26, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🕷 Bug Verified that it’s actually a legit bug that exists in the current release.
Projects
None yet
Development

No branches or pull requests

3 participants