3D

It may be a specific request but since there is a zip file handler for Android, doesn't hurt to ask for a desktop (maybe multiple backends?) implementation.

I would like to try that in the future but if anyone has time before feel free to do it.

Similar

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 forum post: https://forum.babylonjs.com/t/babylon-editor-export-texture-scaling/12723/26

Reproducible via playground: https://playground.babylonjs.com/#DHZKGW#7

Currently when we export specularGlossiness PBRMaterials via _GLTFMaterialExporter._convertSpecularGlossinessTexturesToMetallicRoughnessAsync

We combine albedo + glossiness textures into Base64 texture string, stripping all

Old

When using the @enum tag by itself it puts the documentation in the global section and omits static functions on the enum. It's cluttered and missing information.

New

By adding the @namespace tag it creates a new page for the enum and sh

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