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

Using renderTextures on more than one stage causes an error #1299

Closed
positlabs opened this issue Dec 27, 2014 · 6 comments
Closed

Using renderTextures on more than one stage causes an error #1299

positlabs opened this issue Dec 27, 2014 · 6 comments
Assignees
Labels
🕷 Bug Verified that it’s actually a legit bug that exists in the current release.
Milestone

Comments

@positlabs
Copy link

I would think that renderer instances would be completely sandboxed from each other, but this bug only happens when I try to use renderTexture in multiple renderers.

The bug can be seen here: http://lightpaintlive.com/dist/

I can provide some code snippets if needed.

screen shot 2014-12-27 at 10 59 05 am

@englercj
Copy link
Member

Unfortunately they are not, they share global state (at least in the webgl renderer). I am trying to address some of these issues in #1296

@positlabs
Copy link
Author

+1 for #1296.

We can probably solve this renderTexture issue by resetting some variables. At least I hope that's the case. I don't have a ton of time to spend on looking into this, but I will poke around.

@positlabs
Copy link
Author

Hmm.. I'm not going to have time to look into this any time soon. :(

@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

You are now forced to pass a renderer to a renderTexture in v3. This should stop this error from occurring. cheers! 👍

@positlabs
Copy link
Author

Awesome, thanks! I will be using renderTextures everywhere 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