Just found this while creating PBR materials from a bot. The InventoryType enum ends at
Settings = 23, Material = 24, but on the wire 24 is actually IT_PERSON. The current LL
values are:
IT_WIDGET = 23, IT_PERSON = 24, IT_SETTINGS = 25, IT_MATERIAL = 26, IT_GLTF = 27, IT_GLTF_BIN = 28
Live on Agni:
Every PBR material in my inventory reads back InvType = 26, which the enum can't name — so case InventoryType.Material and FindFolderForType just miss.
Creating a material row with InventoryType.Material (24) — the grid stored it as 27 and the material update on it failed.
Creating the same row with wire value 26 — stored as 26, update worked.
AssetType/FolderType were renumbered correctly in 3.x; InventoryType got missed. Could we bring the tail of the enum in line with llinventorytype.h (23–28) and fix the type-name table to match?
I'm happy to put together a PR on anything I report! Just let me know!
Just found this while creating PBR materials from a bot. The InventoryType enum ends at
Settings = 23, Material = 24, but on the wire 24 is actually IT_PERSON. The current LL
values are:
IT_WIDGET = 23, IT_PERSON = 24, IT_SETTINGS = 25, IT_MATERIAL = 26, IT_GLTF = 27, IT_GLTF_BIN = 28
Live on Agni:
Every PBR material in my inventory reads back InvType = 26, which the enum can't name — so case InventoryType.Material and FindFolderForType just miss.
Creating a material row with InventoryType.Material (24) — the grid stored it as 27 and the material update on it failed.
Creating the same row with wire value 26 — stored as 26, update worked.
AssetType/FolderType were renumbered correctly in 3.x; InventoryType got missed. Could we bring the tail of the enum in line with llinventorytype.h (23–28) and fix the type-name table to match?
I'm happy to put together a PR on anything I report! Just let me know!