see the attached .x file.
first; create an XFile node and open up the file in 33beta9.10
the Mesh output shows an empty set. that is wrong. only after connecting the xfile to an effect and an renderer it show the right output: a mesh with 11 subsets. why is it not showing the right data right away?
but this a cosmetic one - the following two are more serious:
second; if you look at the source of the xfile you will see various texture references. am i right that the TextureFileName pin is supposed to output a spread of these texture file names? it doesnt.
third; as we are regexpr experts here at meso hq, we tried to open up the xfile with the Reader node and tried to get our hands at the texture names ourselves. most of the time the reader does not really read our 101Kb textfile but stays empty. but i guess this is somehow a known bug.
and a cosmetic one
fourth; after we somehow manage to load the file, the tooltip shows pixel artifacts in the patch window. it somehow looks like that the full 101Kb are put into the textarea of the tooltip which starts to confuse poor old gdi?