You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if anyone else has encountered this issue; was working on a project earlier today and noticed that the STLLoader class was failing to accurately determine what type of file my .stl was; binary or ascii.
Testing with STLLoader Example
Just to test, I passed the same URL (object being served from AWS S3 bucket) to the example that is posted in ThreeJS and was able to render the object immediately.
Testing within Meteor
When I reproduce the code within Meteor, the isBinary() check seems to silently fail or think that the object is ascii rather than a binary file so it ends up returning an empty Geometry object.
Seems like there is something within Meteor that is throwing off the automatic type detection at line 90.
The text was updated successfully, but these errors were encountered:
Not sure if anyone else has encountered this issue; was working on a project earlier today and noticed that the
STLLoader
class was failing to accurately determine what type of file my.stl
was; binary or ascii.Testing with STLLoader Example
Just to test, I passed the same URL (object being served from AWS S3 bucket) to the example that is posted in ThreeJS and was able to render the object immediately.
Testing within Meteor
When I reproduce the code within Meteor, the
isBinary()
check seems to silently fail or think that the object isascii
rather than a binary file so it ends up returning an emptyGeometry
object.Seems like there is something within Meteor that is throwing off the automatic type detection at line 90.
The text was updated successfully, but these errors were encountered: