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
Here is a screenshot demonstrating a minimum reproducible bit of code that causes the problem:
I would like to add that the three obj method does work, but only once: the first time it's run it does effectively set the draw range, but since it "kills" the index attribute it can not be run more than once.
MORE INFO:
the index is being lost in the three.js function "syncToModel", because for some reason it thinks it's an "attribute generated by three", or something like that. I will report back with more info / a pull request if I can fix this.
The text was updated successfully, but these errors were encountered:
Here is a screenshot demonstrating a minimum reproducible bit of code that causes the problem:
I would like to add that the three obj method does work, but only once: the first time it's run it does effectively set the draw range, but since it "kills" the index attribute it can not be run more than once.
MORE INFO:
the index is being lost in the three.js function "syncToModel", because for some reason it thinks it's an "attribute generated by three", or something like that. I will report back with more info / a pull request if I can fix this.
The text was updated successfully, but these errors were encountered: