No file texture attributes: Possible install issue?

[a-dogg]

Uninstallation, and reinstallation didn't solve it.

Here's the script editor content for creating a new blinn material and adding the texture file to the Default color.

file -f -new;
// Result: ./untitled //
shadingNode -asShader blinn;
// Result: blinn1 //
sets -renderable true -noSurfaceShader true -empty -name blinn1SG;
// Result: blinn1SG //
connectAttr -f blinn1.outColor blinn1SG.surfaceShader;
// Result: Connected blinn1.outColor to blinn1SG.surfaceShader //
defaultNavigation -createNew -destination blinn1.color;
createRenderNode -allWithTexturesUp "defaultNavigation -force true -connectToExisting -source %node -destination blinn1.color" "";
defaultNavigation -defaultTraversal -destination blinn1.color;
shadingNode -asTexture file;
// Result: file1 //
shadingNode -asUtility place2dTexture;
// Result: place2dTexture1 //
connectAttr -f place2dTexture1.coverage file1.coverage;
// Result: Connected place2dTexture1.coverage to file1.coverage //
connectAttr -f place2dTexture1.translateFrame file1.translateFrame;
// Result: Connected place2dTexture1.translateFrame to file1.translateFrame //
connectAttr -f place2dTexture1.rotateFrame file1.rotateFrame;
// Result: Connected place2dTexture1.rotateFrame to file1.rotateFrame //
connectAttr -f place2dTexture1.mirrorU file1.mirrorU;
// Result: Connected place2dTexture1.mirrorU to file1.mirrorU //
connectAttr -f place2dTexture1.mirrorV file1.mirrorV;
// Result: Connected place2dTexture1.mirrorV to file1.mirrorV //
connectAttr -f place2dTexture1.stagger file1.stagger;
// Result: Connected place2dTexture1.stagger to file1.stagger //
connectAttr -f place2dTexture1.wrapU file1.wrapU;
// Result: Connected place2dTexture1.wrapU to file1.wrapU //
connectAttr -f place2dTexture1.wrapV file1.wrapV;
// Result: Connected place2dTexture1.wrapV to file1.wrapV //
connectAttr -f place2dTexture1.repeatUV file1.repeatUV;
// Result: Connected place2dTexture1.repeatUV to file1.repeatUV //
connectAttr -f place2dTexture1.offset file1.offset;
// Result: Connected place2dTexture1.offset to file1.offset //
connectAttr -f place2dTexture1.rotateUV file1.rotateUV;
// Result: Connected place2dTexture1.rotateUV to file1.rotateUV //
connectAttr -f place2dTexture1.noiseUV file1.noiseUV;
// Result: Connected place2dTexture1.noiseUV to file1.noiseUV //
connectAttr -f place2dTexture1.vertexUvOne file1.vertexUvOne;
// Result: Connected place2dTexture1.vertexUvOne to file1.vertexUvOne //
connectAttr -f place2dTexture1.vertexUvTwo file1.vertexUvTwo;
// Result: Connected place2dTexture1.vertexUvTwo to file1.vertexUvTwo //
connectAttr -f place2dTexture1.vertexUvThree file1.vertexUvThree;
// Result: Connected place2dTexture1.vertexUvThree to file1.vertexUvThree //
connectAttr -f place2dTexture1.vertexCameraOne file1.vertexCameraOne;
// Result: Connected place2dTexture1.vertexCameraOne to file1.vertexCameraOne //
connectAttr place2dTexture1.outUV file1.uv;
// Result: Connected place2dTexture1.outUV to file1.uvCoord //
connectAttr place2dTexture1.outUvFilterSize file1.uvFilterSize;
// Result: Connected place2dTexture1.outUvFilterSize to file1.uvFilterSize //
defaultNavigation -force true -connectToExisting -source file1 -destination blinn1.color;
connectAttr -force file1.outColor blinn1.color;
// Result: Connected file1.outColor to blinn1.color //

Hopefully that is helpful.

I'm also getting the following at startup, but it seems unrelated to this problem.

docServer -start;
// Warning: docServer service "aliasdocserver" does not exist. //
// Warning: Unable to Start the docServer. //

Thanks,
Andrew

[a-dogg]

I had a friend do the same procedure I did, and the one difference I'm seeing between his script editor output and mine is this:

updateBinMembershipAfterConnection xxxx

the xxxx being whatever the last connection was. I have no updateBinMembershipAfterConnection lines in my output. He has 19 occurences of it. What could be causing this?

-andrew

EDIT: here's a word doc (http://www.avatar-creative.com/maya/scriptEditor_output.doc) of the side by side output of the working script editor and mine.

[a-dogg]

I got some feedback from Alias support finally. The fix was that Dell had set font settings to "larger" or 125% in display advanced options. when I set it back to normal maya miraculously worked.

That is such a rediculous thing to not have documented. Such a huge hit in functionality from such a benign setting! If the Dell Precision M70 is listed as Certified hardware, then it needs to work out of the box, or have a glaring note to change a certain setting.

So if anyone has an issue where certain attribute editor boxes or preference settings aren't showing up at all, here is a possible fix:

Can you check your font settings? Make sure you are using "small fonts".

To check follow these steps:

1. Open the Control Panel
2. Double click on Display
3. Click on the Settings tab
4. Click on the Advanced button
5. On the General tab your font size should be set to "Small 96 dpi"

After changing it reboot your machine and try again.


a-dogg

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.