-
Notifications
You must be signed in to change notification settings - Fork 8
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
Does not work with latest aframe branch #4
Comments
Hmm, I'll look into this. The latest aframe branch has custom shaders which are probably which'll be used for this module once it's released. |
I just ran into this. To fix it, in createCanvas: change
to
|
I'll take care of this tomorrow, thanks! On Fri, Mar 18, 2016 at 4:54 PM, Paul M. Christian <notifications@github.com
|
This solution isn't backwards compatible, so I made a quick and dirty if...else. Should be solved in |
I've tried to get this component to work with A-Frame 0.2.0, but it doesn't work. This example just renders a white cube with A-Frame 0.2.0 and version 1.4.0 of this component:
|
@RSpace this should be fixed in |
I tried it with the latest branch of aframe.io 0.3.0 and it works fine for me. Though i|ve to admit one should use the complete example code of the repository, not the short hints giving snippets of the repository page. |
Hi,
The components works perfectly if using aframe-core, as you have in your package
"aframe-core": "0.1.2",
but the with the latest aframe branch
"aframe": "aframevr/aframe#dev"
The canvas is not drawn on the entity and I didn't get any message on the console about it.
The text was updated successfully, but these errors were encountered: