Skip to content
This repository has been archived by the owner on Mar 16, 2021. It is now read-only.

Why CanvasRenderer is not available as add on? #1

Open
YvensFaos opened this issue Aug 30, 2017 · 2 comments
Open

Why CanvasRenderer is not available as add on? #1

YvensFaos opened this issue Aug 30, 2017 · 2 comments

Comments

@YvensFaos
Copy link

I am in need of adding Thee.CanvasRenderer to my project but I just saw that it is not available on your list of add ons? Why is it so? Do you plan on adding it soon?

@marcofugaro
Copy link
Owner

Both CanvasRenderer and Projector are not included for now because the Three.js code already attaches those names to the THREE object, thus resulting in an error when the plugin tries to override it.

This is where those name get attached, as you can see those are only deprecation warnings.

I submitted an issue about this some time ago, but it never got resolved.

You're right, I should probably write that in the README.

Does your project give you an error if you try to do this?

import * as THREE from 'three';
import './CanvasRenderer'; // or Projector

@YvensFaos
Copy link
Author

Not exactly an error, but my code does not run if i keep this line:
import './CanvasRenderer'; // or Projector

If i take it out, it will throw the deprecated warning.
THREE.CanvasRenderer has been moved to /examples/js/renderers/CanvasRenderer.js

My issue is that my code should be able to run on browsers that do not support webgl, so I though on using CanvasRenderer instead of default WebGLRenderer in these cases, but, apparently, it won't work anyway. I'll give a try on the webpack as mentioned here.

Thank you very much.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants