-
Notifications
You must be signed in to change notification settings - Fork 716
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
Subdivision Modifier appears to be not working (?) #10
Comments
Humm, it seems that this is using Three.js r60, which no longer has face4: mrdoob/three.js#3663 I had a similar issue, but it was obj related: mrdoob/three.js#3835 |
Yikes -- I'm going to have to push this example back to Three.js v59 until SubdivisionModifer is fixed... |
I'm new to Three.js, but your examples page is really helpful. For instance, I am working right now on the ability to add new object3D's to a scene that has an existing shape (let's say it's a smooth terrain-like shape), then the new object will 'snap' to the terrain, and as you drag the new object, it will stay on the terrain, as well as rotate to match the face it's currently sitting on. That's one small part, but there is no example for anything like that out there. What's fun, is most of the examples I've found online for copying matrices from one object to another don't work anymore because of upgrades to Three.js. fun.
|
Hi Professor Stemkoski, The Topology Data2 example appears broken as well because of this same issue. In the console window it says 'cannot read property 'face' of undefined'. Just wanted to give you a heads-up about that one also. Thanks so much for the examples - they have really helped me grasp the fundamentals of Three.js! |
I am using r60 and I have subdivision modifier working. Not sure exactly why yours isn't but I have it up and running, thanks for the example! |
I'm using slightly different code, but not much compared with yours... // CYLINDER
|
This is still broken, just wanted to ping this again to find out if there's any known workarounds. |
FYI: Last week the subdivision modifier example worked fine.
Now in both Mozilla and Chrome, the examples all look like porcupines - spikes pointing everywhere.
The text was updated successfully, but these errors were encountered: