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
We are currently utilizing the 3d-tiles-renderer with a custom points material which could support both NORMAL/NORMAL_OCT16P per-point feature (as a standard normal attribute), and BATCH_LENGTH global feature.
I understand that the default PointsMaterial in three does not currently support normal attributes. However, I would like to propose adding support for loading NORMAL/NORMAL_OCT16P, in line with three semantics.
Moreover, I suspect that since BATCH_LENGTH as no equivalent in the default PointsMaterial, we'll have to assign it later when using our custom points material. However, could we at least disable the warnings to not flood the console?
Before submitting a PR, I would appreciate your feedback on this proposal. =)
The text was updated successfully, but these errors were encountered:
Hello! If you'd like to implement a PR to add support for the NORMAL and NORMAL_OCT16P feature flags for PNTSLoader that would be great. I don't want to add custom materials for lit points but we can definitely add a "normal" attribute to the points geometry and then you can replace the material with a custom lit one when loaded using the load-model event.
Regarding BATCH_LENGTH - I think that can be removed since it's read and used in the PNTSLoaderBase class.
Hi!
We are currently utilizing the 3d-tiles-renderer with a custom points material which could support both
NORMAL
/NORMAL_OCT16P
per-point feature (as a standardnormal
attribute), andBATCH_LENGTH
global feature.I understand that the default
PointsMaterial
in three does not currently supportnormal
attributes. However, I would like to propose adding support for loadingNORMAL
/NORMAL_OCT16P
, in line with three semantics.Moreover, I suspect that since
BATCH_LENGTH
as no equivalent in the defaultPointsMaterial
, we'll have to assign it later when using our custom points material. However, could we at least disable the warnings to not flood the console?Before submitting a PR, I would appreciate your feedback on this proposal. =)
The text was updated successfully, but these errors were encountered: