Invisible materials causing packagetool warnings

Questions & Community Discussions
1

I am using Blender and I created a mesh collider for an object as instructed
by the
SDK,
set its material to type Invisible and checked Collision Material. Then I
exported the object and launched fspackagetool.exe to compile it. Package
tool reported a warning about alpha value:

Invisible material ‘collider’ has an alpha value below 0.1; this will make
it hard to see when debugging. Since it is invisible under normal
circumstances, consider putting a higher alpha value.

I did not change alpha value nor is it even settable with this material type
(settings grayed out). Either the Blender exporter sets wrong alpha value or
fspackagetool reports unnecessary warnings. When debugging, the collision mesh
is visible and covered with chessboard pattern. Version information:
Microsoft Flight Simulator 1.25.9.0 (Steam version) Official MSFS Blender IO
1.1.6

2

The same occurs with 3DSMax 2018 and Latest SDK The alpha in this example has
been set in 3DS Material editor as 1.00 Invisible material ‘Occlusion’ has an
alpha value below 0.1; this will make it hard to see when debugging. Since it
is invisible under normal circumstances, consider putting a higher alpha
value.

3

I think it’s a fair warning (at least it’s not an error) as it’s trying to
help you with future in-sim debugging if you’re expecting to see something
with an alpha below 0.1. However the debugger could probably be more helpful
by not issuing a warning /false positive where “ASOBO_material_invisible” :
“enabled” = true in the GLTF if that’s what you mean? Specifically

               "ASOBO_material_invisible" : {
                    "enabled" : true
                }