XGen Error Some surfaces have no file texture assigned to the current attribute

[Anonymous]

Hi,

i want to create a rendering with XGen like in this tutorial

https://www.youtube.com/watch?v=L7XZxffWork

When i want to create a texture, as described at 10:40, i get the message:

// Warning: file: C:/Program Files/Autodesk/Maya2017/scripts/others/art3dPaintSetPaintAttr.mel line 31: Some surfaces have no file texture assigned to the current attribute. //
# Warning: Some surfaces have no file texture assigned to the current attribute. #

The geometries then have no texture.

Hope someone can help me!

[cornelh]

@Anonymous

First off all I would recommend you install the latest Update 4 for Maya 2017 and reset you preferences.. Next I would check out the new workflows for Maya 2017 update 4 for XGen and many things have changed since that video which will not work as dictated in that video which is for Maya 2015.

http://help.autodesk.com/view/MAYAUL/2017/ENU/?guid=GUID-C6324505-BD4F-4FD2-B340-CF99158D4819

I wish you the best of luck on your XGen particles adventure!

Cheers!!

[Michael_Todd]

With the paint tool still active, select the geo and hit the assign/edit textures button in the tool settings. 

Set the size and file type and assign

You should then be able to paint. The error usually occurs because there is a non maya material assigned to the geo and artisan can't find an attribute to assign the texture to. Try to stick with default maya materials for geo that XGen is bound to if you need to paint maps. If you have mudbox you can paint ptex maps directly with a much better set of painting tools.

Cheers

[Anonymous]

I have installed Maya 2018 Update 1. Same problem here. 

The link you have put in your post is also for Maya 2015...

I don´t need luck i need support. We pay a lot of money to autodesk for it´s products.

[Anonymous]

I can paint the texture but it is not visible on the XGen geometry.

[Michael_Todd]

Depending on what renderer you are using, you need to pass the texture to the material that is attached to the description. If you're using a custom color expression, in Arnold you need to use an aiUserDataColor node to pass the expression through to the material at render time

Assigning Colors to Primitives

Other renderers have different requirements.

Cheers

[gdhmalkin]

Hi there.

I'm having this same issue and can't seem to overcome it.

If i have no map, i get a full head of hair on my character. As soon as i create a map, even if it's solid white, the scalp is patchy and weird. I see in Hypershade that when I click on the paint map button - in xgen where i've created the map - a new material and SG are created, although seems a temporary thing as this new material isn't listed in the Materials tab.

I get the error:

// Warning: file: C:/Program Files/Autodesk/Maya2016/scripts/others/art3dPaintSetPaintAttr.mel line 45: Some surfaces have no file texture assigned to the current attribute. // # Warning: Some surfaces have no file texture assigned to the current attribute. #

I have applied the default lambert1 to my scalp geo and tried applying a new lambert but no luck.  My geo has no construction history and is UVd.  I have also tried deleting my Maya prefs and reverting to default settings.

thanks for any help!

[alvaradoanimation]

If you go to the node editor and view your geo's connections you'll see file nodes with the .iff images plugging into your geoShape node. I noticed that when I was getting this error, the file nodes were trying to read "name"1 or "name"2 instead of the "name" file on disk. If you just re-direct the file node to your .iff file on disk it should resolve the problem.

[eldron2323]

I just wanted to help out with anyone that had this issue. It's because maya is looking in the wrong path even though you set the project. To fix it, go to Window>General>FilePathEditor and you will see a bunch of red Xs. There will be a certain group labeled /... Select that entire group and repath files and point them to your sourceimages/3dPaintTextures/filename folder. This should fix this dumb issue.