SLAB_SKINS_BMAT_NAMES not working correctly when printing 9th < skin

[Miko]

In a label this SLAB_SKINS_BMAT_NAMES parameter "breaks" when listing the 8 or 9th skin (and further skins). Works as expected in 7 or fewer. Tried it with a very dumbed down version of my label, simple rows with: text2 0, "manuallychangedposition",SLAB_SKINS_BMAT_NAMES [manually changed id][1]. If a slab had 4 skins and I wanted to print the 7th skin, it printed nothing, which is correct, no 7th skin, but if i wanted to print the 9th skin the label started to look like a dot - missing object, even if i added lower skins for the function to read, once i added the 9th skin, it always showed only a dot. Unless the slab had acces to the 9th skin, in which case it broke on the 10th skin.

[Lingwisyer]

What does the Report say? Should return an error message related to the failed object generation. Though, why are you trying to query non-existant skins? If you need to have user input, you could link the parameter back to the skin count, with a Request into a Range.

If you make a composite with more than 10 skins, then query the 10th, does it work? If that does work, my guess is that the array that contains the skin list dynamically changes based on the number of skins, but has a minimum size. If it does not, than I guess this would be a bug to report.

Ling.

[Miko]

Where can i find that Report

Edit:

I was trying to query nonexistant skins to troubleshoot the problem, everything works even with nonexistant skins, but when querying for the 9th or futher skins it stops working

[Lingwisyer]

File => Info => Session Report

It should automatically pop up on your tab bar when an error occurs though... Or at least the Action Center will...

[Miko]

Ecodesign Star failed and Polygon is degenerated, nothing else.

This is when its working

And this is when i try to list from a slab that has 8 or 9 + skins

[Lingwisyer]

So when the label fails to generate, it does not return an error message? Odd...

[Barry Kelly]

You can inquire the number of wall skins with ... WALL_SKINS_NUMBER

If that helps.

Barry.

[runxel]

For whatever reason the SLAB_SKINS_NUMBER is capped at 8... this makes me believe that also all the other skin reading parameters do not go beyond that either.

Why Walls can have 127 skins but Slabs can't? Well, err..... 👀 GS? Please tell us. Or do something about it 😄

[runxel]

Ohhhh, I got it now. 😳

All of this got superseded by requesting "Component_IDs_Of_Parent" and then "Component_Property_Values_Of_Parent"!

Man, it was not easy to figure that one out. 😐

[Barry Kelly]

Sorry.

Where did I get WALL_SKINS from when you are talking about slabs. 😞

Barry.