3D

Found a small error in the Real World Use Cases of the v8 Migration Guide

The example code describing that array's must be explicit is missing the .map() closing bracket.

What it is now:

<mesh>
-  {colors.map((color, index) => <meshBasicMaterial key={index} attachArray="material" color={color}

See KhronosGroup/glTF#1691 for implementation spec.

Is there an existing request for this?

• I have searched the existing requests

Forums discussion

gitter

Subproject(s) affected?

Path

Idea description

Per LGTM, many PathWB conditional DEBUG rules are "unreachable".

"Unreachable code makes the code more difficult to understand and may slow down loading of modules."

See https://lgtm.com/projects

Currently IndexDatatype.createTypedArray only outputs Uint16Array and Uint32Array. This caused a bug in #10344 because it returned a Uint16Array for uint8 indices, which was too big for the getBufferData function. The fix itself is easy but it causes a lot of unit tests to break, which will take more time to fix.

Once this function is changed to return Uint8Array, the manual check i

Please respect the following template to report a new issue, otherwise your issue will be automatically closed.

Before submitting, search through existing open or closed issues reports and through blender.stackexchange.com to check whether the issue already exists.

If the issue concerns an operator that grab geodata from an external web service (Basemaps, OSM, SRTM), then it can be a network