Maya 2016.5 Errors

[Magnetic Dreams]

Hi,

We are rendering with RR 7.0.35 and Maya2016.5 (Extension 2 SP1), and have a few errors that are being generated in the logs that we have no idea how to troubleshoot. If anyone has any ideas, we would greatly appreciate the feedback. Thanks!

Our Maya test scene contains text, and we get lots of these errors (we do not even use the S drive):
R241| API error detected in S:\Maya_2016_R2_DI\src\Maya\src\Type\fontNode.cpp at line 2029

R242| : (kFailure): Unexpected Internal Failure

Another error we get is:

R234| Error in this log file (241): error: file: //rrserv/rr/render_apps/scripts/kso_maya.mel line 11: line 1: invalid \x escape

This one is strange, since we don't even have FumeFX for Maya:

R 60| Unable to execute xgen.mel.' 16:34.59 rrMaya : Loading FumeFX

R231| Error in this log file (151): error: line 1: plug-in, "fumefx", was not found on maya_plug_in_path.

We also get several xgen errors:

R 56| Error: file: C:/Program Files/Autodesk/Maya2016.5/plug-ins/xgen/scripts/igInitialize.mel line 63: ImportError: file C:\Program Files\Autodesk\Maya2016.5\plug-ins\xgen\scripts\xgenm\xmaya\xgmExternalAPI.py line 110: DLL load failed: The specified procedure could not be found.

R 57| Error: Unable to execute igInitialize.mel.

R 58| Unable to execute igInitialize.mel.Error: line 0: ImportError: file C:\Program Files\Autodesk\Maya2016.5\plug-ins\xgen\scripts\xgenm\xmaya\xgmExternalAPI.py line 110: DLL load failed: The specified procedure could not be found.

R 59| Error: Unable to execute xgen.mel.

[RR, Schoenberger]

Hi

 

1) S drive: As you can see from the filename, it was a .cpp file, it is the source file that was used to compile a part of Maya.

Some parts of Maya report the source location if they crash.

 

2) invalid \x escape.

That should not happen. It might have a lof reasons, but to find it out, the complete log file would help.

The messages above that error. You can upload a render log file via www.RoyalRender.de/upload_r.php

 

3) FumeFX: RR has a load command for the plugin as the auto-load did not work.

 

 

4) Xgen had the same issue as FumeFX, but these messages should not appear, perhaps an issue with 2016.5.

There has been a change for the next RR version to load some xgen plugins only if you render with MRay.

 

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

---

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of Magnetic Dreams
Sent: Tuesday, July 05, 2016 7:24 PM
To: Royal Render Knights Tavern
Subject: [rrKnights] Maya 2016.5 Errors

--
If you reply, the message is send to the user group which is sufficient.
("Reply All" just sends the message twice to the last author which is not required)
---
You received this message because you are subscribed to the Google Groups "Royal Render Knights Tavern" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rrKnights+...@googlegroups.com.
Visit this group at https://groups.google.com/group/rrKnights.
For more options, visit https://groups.google.com/d/optout.

[Magnetic Dreams]

1) Right, hoping someone know the answer to why this is crashing. More of a Maya question than a RR one.

2) Uploading the logs now. We are getting the /x error on all our Maya 2016.5 jobs.

3) Good to know. Is this FumeFX line something we can remove from the Maya config?

4) We are using Redshift, so that makes sense.

[RR, Schoenberger]

1)

There is no question in the AD area about this, so I think nobody knows.

As you cannot fix it, you have to remove it.

a) First, lower the render quality and save the scene as debug start scene with name _XX

b) Then delete all geo, save it as _00.

c) Open _XX, delete the first half of the objects, save as _0X.

d) Open _XX, delete second half and save as _X0.

Submit all 4 scenes with every 10th frame.

_XX and one of the half scenes should crash, _00 should never crash and the other half scene should not crash as well.

If it is the case, then load the half scene that crashes and repeat c+d.

By cutting the scene in half every time, you should get the object quite fast.

 

 

 

2) Ok, checking them later.

 

3) You can remove it from the kso_Maya.py file

 

4) You can remove all Xgen plugin load lines as well.

 

Note: RR will not update kso_maya.py in this case any more, but there will not be many changes for RR 7 in this script so that should be fine.

 

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of Magnetic Dreams

Sent: Tuesday, July 05, 2016 9:17 PM

To: Royal Render Knights Tavern

Cc: schoen...@royalrender.de
Subject: Re: [rrKnights] Maya 2016.5 Errors

[Magnetic Dreams]

1) We know what the object is, it's the 3D Text that is added to the scene. We only get these fontNode errors with the Text added as a font. We may be approaching 3D Text incorrectly, and the font may need to be baked first.

I have commented out the FumeFX and XGen lines within our kso_maya.py, thanks for this information.

[Magnetic Dreams]

Just to update, we contacted Autodesk about the fontNode.cpp problem and it's a known issue. Some of the system fonts (such as Arial Black, and Segoe) conflict with the QT UI fonts that are used in Maya and generate the error. The workaround for now is to convert to vector.

[RR, Schoenberger]

2) invalid \x escape

 

The message is created while the scene file is loaded.

So it seems to be something in the scene file.

Do you get this error in Mayas script log or output window when you open the scene?

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of Magnetic Dreams

Sent: Tuesday, July 05, 2016 9:17 PM

To: Royal Render Knights Tavern

Cc: schoen...@royalrender.de
Subject: Re: [rrKnights] Maya 2016.5 Errors

[Magnetic Dreams]

No, I have opened the scene up within Maya and the "invalid \x escape" message does not show up in the script log. I only see this in the RR logs.

[Magnetic Dreams]

I can't help think this is connected to another problem we have. We are unable to get any xgen hair to render.
What happens is that the .xgen file is not copied from the scene folder to the local cache location. If we copy over the .xgen files manually into the local cache folder, then RR locates the .xgen file and it renders correctly.

Maybe RR is reading an xgen path (...\xgen...) and seeing the \x as an escape character, which then causes the "copy .xgen file from scene to localcache" to fail?

R143| Error: file: //rrServ/rr/render_apps/scripts/kso_maya.mel line 11: line 1: invalid \x escape

R144| Error: file: //rrServ/rr/render_apps/scripts/kso_maya.mel line 11: XGen: Failed to open file: C:/RR_localdata/cachedscenes/q_ssChristmasSpecial/scratch/4a866fe0/fur/reindeer_fur_world.0008__reindeer_fur.xgen

R145| Error: file: //rrServ/rr/render_apps/scripts/kso_maya.mel line 11: XGen: Failed to import collection from file C:/RR_localdata/cachedscenes/q_ssChristmasSpecial/scratch/4a866fe0/fur/reindeer_fur_world.0008__reindeer_fur.xgen

[Magnetic Dreams]

ah ha! I saw a previous Xgen related post by Doug Wilkinson, and he suggested disabling the "Allow Local Scene Copy", and this works! all errors are now gone. I still think the "invalid \x escape" breaks the local .xgen file from copying, if you could look into this.

[Magnetic Dreams]

I'm looking at one of our log files for this and I notice that our admin login account for RR is called "xsirender" (this was setup back in our xsi days, but RR still uses it for Maya).

We have several paths referencing this in the log file, for example:
C:\Users\xsirender\AppData\Roaming
C:\Users\xsirender\AppData\Local
USERPROFILE: C:\Users\xsirender
C:\Users\XSIREN~1\AppData\Local\Temp\rrbin64\rrResetexitcode.exe"

I was wondering if any of these paths are processed by Python by RR?
This could account for the mysterious "\x escape" error we have been receiving.

[RR, Schoenberger]

Hi

 

No, these paths are not processed in the script.

The only difference between a local scene copy job and a job without is the location of the scene.

So only that changes for the script.

I can understand that Maya could not find files relative to the scene file if they are saved with a relative path, but I do not understand why it understands the path as excape sequence. Especially as escape sequences use a backslash \ always and in your error message it uses a slash /.

 

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of Magnetic Dreams

Sent: Friday, August 05, 2016 7:12 PM

[Magnetic Dreams]

Just to clarify, the error message we receive uses a backslash "\x escape", not a forward flash.

[RR, Schoenberger]

You are right, i took a look at the wrong email where you stated

"2) Uploading the logs now. We are getting the /x error on all our Maya 2016.5 jobs."

But the other emails state it right, with a backslash.

 

 

Nevertheless, we (RR) have to investigate further into the local copy functions.

The next step is a better local texture copy that works with ref models.

And that can then be extended to cache files, either for a local copy of the cache files or for relinking the cache file location to a non-relative path.

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of Magnetic Dreams

Sent: Monday, August 08, 2016 6:59 PM