snoyer
snoyer
it broke a broken test, the math checks out :) (test was ensuring only the one wrong behavior this PR fixes and none of the correct ones) I've fixed this...
Nice! thanks @NaniNoni As it is, from a user point of view, this could answer "where are the current config files?" but not "where should I _create_ my config file?"...
Would it be better to improve the separation of concerns between `GetConfigPaths` and `ReadConfigFiles` instead of trying to include the user-facing logging into `ReadConfigFiles` with a dry-run param? The idea...
> The only downside I'm aware of is that the `print_config_info` command considers `"config"` as the only `configSearch` query for `GetConfigPaths` You'd have to track down where the `configSearch` param...
I haven't checked the provided file but we've seen issues with 3mf from BambuStudio/OrcaSlicer before due to the `assimp` library not handling model instancing/references: #1708 Upstream issue: https://github.com/assimp/assimp/issues/5811
the material says ```json "pbrMetallicRoughness": { "baseColorTexture": { "index": 0, "texCoord": 1 }, ``` so UVs should be read from `TEXCOORD_1` but could they be wrongly read from the default...
> Are you sure this file is valid ? It's a sub-optimal GLB file because it has both a binary buffer (for the geometry) and a data-URI buffer (for the...
> When the file is a binary, the main buffer is saved first, then an empty buffer is saved, followed by the remaining buffers. The problem is the buffer views...
Turns out it doesn't mention the length but it's here: https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#glb-stored-buffer > A buffer with data provided by the GLB-stored `BIN` chunk, MUST be the first element of `buffers` array...