Arnold, Maya 2017 doesn't load "not currently available"

[thehexeno]

// Warning: file: C:/Program Files/Autodesk/Maya2017/scripts/others/supportRenderers.mel line 64: The renderer "arnold" used by this scene, is not currently available. The "mayaSoftware" renderer will be used instead. //

So I tried Maya 2017 with Arnold and everything worked fine but then I installed the first update and now I get that warning, I already reinstalled Maya.

[Anonymous]

I would have to say maya 2017 is rather glitchy but ...... I dont have a monster pc like some in fact isnt the most perfect one but the update 1 comes with a older version of mtoaa....

and worked fine at first but then I got the same errors you all are having had to update to the newest version from solidangle and the error went away.....

I am getting problems with my hypershade panes wont load and the model toolkit less you leave it tabbbed out it will give you a const error 1691 in the mel script saying it is not there

Maya needs to come out with a hot-fix for some of this

I had to run the motaa install twice cause guess the first time it takes the older version off...... and had to go into my plugins and check the motaa preference all over again

[cakeller98]

Which is horribly bad form. If you put out 2 versions of something one that's broken, and another that isn't... you ad a minor revision - ALWAYS.

if there's a difference it should be Maya 2017, Update 1.01 or 1b. But it's just really bad if you can have 2 installers with the same version with different contents. that's a nono.

[pshwayka]

Exactly! (I was just about to make the same comment.)

[Anonymous]

I am not so sure if you meaning I ran the same installer twice might have been my own error..... but wasn't a maya installer I gave the link to where I had got the installer from in a older post...... more or less just commenting what I did and it worked for me ...... so anyways hope everyone gets the Arnold issue solved .... just trying to help with what I did

[Anonymous]

I went ahead and submitted a case with Autodesk for this issue. They are aware of the issue and are taking steps to correct it however, we probably won't see a fix for it until Update 2 comes out in a couple of months. Below are the suggestions given to temporarily fix the problem.

Autodesk Suggestions Below...

"un-install your current version of Arnold, and then download the latest version from the Solid Angle website."

"Please re-install the Maya 2017 Update 1.  Then run the Arnold installer, which will un-install Arnold.  Then re-run the installer and re-install."

If that doesn't work then...

"stay with 2017 without the update 1, and then try again with our Update 2 which will be out in a few months."

[cakeller98]

Yup that's what I had to do as well.

Installed Maya 2017, Update 1.
then I ran the installer from Solid Angle's website which was released today.
because the first run-through may have to uninstall an older version, you might have to run it 2x.

this did fix my problem. However, I also did have to re-enable it in plug-ins. but at least that was now possible.

thanks for posting this. hopefully because solid angle posted the fixed installer for arnold, most people can get it to work.

[arcon76]

I'm getting the same error issue with Arnold post Update 1, not being able to load it in the plug-in manager.

However thankfully I'm not using this garbage setup anyway lol. This whole issue is a repeat of the trashy non-existent quality control with integrated Autodesk plug-ins. 2016 was complete screw job with MR, breaking all sorts of layer functionality and leaving users scrambling for a workaround.

Its not acceptable to fallback on "new versions are buggy" when a fundamental core feature of your program doesn't even load, then expect users to scour the forums for a time consuming workaround. Thankfully there's great competition in the 3rd party render market so we don't have to put up with this.

[Anonymous]

My Graphics Card is Nvidia 1070 which is now certified. I went back a version to what was Autodesk on their chart for drivers. My AMD Processor CPU supports SSE4.2.  I get the Mel Render problem and when I go to plug-ins manager and load now the DLL Error. 

Also, I went to Arnold's website and installed the latest driver which is the same one that is shipped with an update.  When I did, the plugin disappeared.

so I also have also uninstalled three times to see if something was corrupted

Autodesk.... we are not paying for Beta Programs... we expect them to work out of box from Day one at the price you charge.  Going back to Maya 2016 and Nvidia's Iray.

Not a happy camper:-(

[Stephen.Blair]

Hi

If MtoA doesn't show up in the Plug-in Manager, then Maya did not find the MtoA module file (mtoa.mod).

mtoa.mod should be here:

• Windows
  C:\Program Files\Common Files\Autodesk Shared\Modules\Maya\2017
• Linux
  /usr/autodesk/maya/modules/2017
• OSX
  /Library/Preferences/Autodesk/maya2017

If you get MtoA to show up in the Plug-in Manager but you still cannot load MtoA, then I would check for missing dependencies. On Windows, I would use Dependency Walker for that.

The graphics card has nothing to do with the MtoA plugin, so it doesn't matter what graphic card driver you have.

Thanks

Stephen

Solid Angle Support

---

@Anonymous wrote:

My Graphics Card is Nvidia 1070 which is now certified. I went back a version to what was Autodesk on their chart for drivers. My AMD Processor CPU supports SSE4.2.  I get the Mel Render problem and when I go to plug-ins manager and load now the DLL Error. 

Also, I went to Arnold's website and installed the latest driver which is the same one that is shipped with an update.  When I did, the plugin disappeared.

so I also have also uninstalled three times to see if something was corrupted

---

[Anonymous]

I ran the Checker and it came up with API-MS-WIN-CORE-COM-L1-1-1.DLL missing. I am sure this what everyone is running into with same problem. Looking online at MSN DEV its tied to Win 8 or 8.1 I am using Windows 10 Anniversary Edition (upgraded not by choice).

This is the only software program I am problem with this on.

Steve

[Stephen.Blair]

---

@Anonymous wrote:
I ran the Checker and it came up with API-MS-WIN-CORE-COM-L1-1-1.DLL missing. I am sure this what everyone is running into with same problem. Looking online at MSN DEV its tied to Win 8 or 8.1 I am using Windows 10 Anniversary Edition (upgraded not by choice).

This is the only software program I am problem with this on.

Steve

---

That's something that can be safely ignored. You can save a .dwi file and send it to me.

How did you check for SSE4.2? Can you download and run coreinfo -f, and send me the output? It's better to be 100% sure about this before we spend more time troubleshooting.

[Anonymous]

Coreinfo v3.31 - Dump information on system CPU and memory topology
Copyright (C) 2008-2014 Mark Russinovich
Sysinternals - www.sysinternals.com

AMD Phenom(tm) II X6 1065T Processor
AMD64 Family 16 Model 10 Stepping 0, AuthenticAMD
Microcode signature: 010000DC
HTT * Multicore
HYPERVISOR - Hypervisor is present
VMX - Supports Intel hardware-assisted virtualization
SVM * Supports AMD hardware-assisted virtualization
X64 * Supports 64-bit mode

SMX - Supports Intel trusted execution
SKINIT * Supports AMD SKINIT

NX * Supports no-execute page protection
SMEP - Supports Supervisor Mode Execution Prevention
SMAP - Supports Supervisor Mode Access Prevention
PAGE1GB * Supports 1 GB large pages
PAE * Supports > 32-bit physical addresses
PAT * Supports Page Attribute Table
PSE * Supports 4 MB pages
PSE36 * Supports > 32-bit address 4 MB pages
PGE * Supports global bit in page tables
SS - Supports bus snooping for cache operations
VME * Supports Virtual-8086 mode
RDWRFSGSBASE - Supports direct GS/FS base access

FPU * Implements i387 floating point instructions
MMX * Supports MMX instruction set
MMXEXT * Implements AMD MMX extensions
3DNOW * Supports 3DNow! instructions
3DNOWEXT * Supports 3DNow! extension instructions
SSE * Supports Streaming SIMD Extensions
SSE2 * Supports Streaming SIMD Extensions 2
SSE3 * Supports Streaming SIMD Extensions 3
SSSE3 - Supports Supplemental SIMD Extensions 3
SSE4a * Supports Streaming SIMDR Extensions 4a
SSE4.1 - Supports Streaming SIMD Extensions 4.1
SSE4.2 - Supports Streaming SIMD Extensions 4.2

AES - Supports AES extensions
AVX - Supports AVX intruction extensions
FMA - Supports FMA extensions using YMM state
MSR * Implements RDMSR/WRMSR instructions
MTRR * Supports Memory Type Range Registers
XSAVE - Supports XSAVE/XRSTOR instructions
OSXSAVE - Supports XSETBV/XGETBV instructions
RDRAND - Supports RDRAND instruction
RDSEED - Supports RDSEED instruction

CMOV * Supports CMOVcc instruction
CLFSH * Supports CLFLUSH instruction
CX8 * Supports compare and exchange 8-byte instructions
CX16 * Supports CMPXCHG16B instruction
BMI1 - Supports bit manipulation extensions 1
BMI2 - Supports bit manipulation extensions 2
ADX - Supports ADCX/ADOX instructions
DCA - Supports prefetch from memory-mapped device
F16C - Supports half-precision instruction
FXSR * Supports FXSAVE/FXSTOR instructions
FFXSR * Supports optimized FXSAVE/FSRSTOR instruction
MONITOR * Supports MONITOR and MWAIT instructions
MOVBE - Supports MOVBE instruction
ERMSB - Supports Enhanced REP MOVSB/STOSB
PCLMULDQ - Supports PCLMULDQ instruction
POPCNT * Supports POPCNT instruction
LZCNT * Supports LZCNT instruction
SEP * Supports fast system call instructions
LAHF-SAHF * Supports LAHF/SAHF instructions in 64-bit mode
HLE - Supports Hardware Lock Elision instructions
RTM - Supports Restricted Transactional Memory instructions

DE * Supports I/O breakpoints including CR4.DE
DTES64 - Can write history of 64-bit branch addresses
DS - Implements memory-resident debug buffer
DS-CPL - Supports Debug Store feature with CPL
PCID - Supports PCIDs and settable CR4.PCIDE
INVPCID - Supports INVPCID instruction
PDCM - Supports Performance Capabilities MSR
RDTSCP * Supports RDTSCP instruction
TSC * Supports RDTSC instruction
TSC-DEADLINE - Local APIC supports one-shot deadline timer
TSC-INVARIANT * TSC runs at constant rate
xTPR - Supports disabling task priority messages

EIST - Supports Enhanced Intel Speedstep
ACPI - Implements MSR for power management
TM - Implements thermal monitor circuitry
TM2 - Implements Thermal Monitor 2 control
APIC * Implements software-accessible local APIC
x2APIC - Supports x2APIC

CNXT-ID - L1 data cache mode adaptive or BIOS

MCE * Supports Machine Check, INT18 and CR4.MCE
MCA * Implements Machine Check Architecture
PBE - Supports use of FERR#/PBE# pin

PSN - Implements 96-bit processor serial number

PREFETCHW * Supports PREFETCHW instruction

Maximum implemented CPUID leaves: 00000006 (Basic), 8000001B (Extended).

C:\WINDOWS\system32>

[Stephen.Blair]

Hi

Unfortunately, that shows that the processor doesn't support SSE4.2.

An asterisk means "supported", and a dash means "non supported"

SSE4a * Supports Streaming SIMDR Extensions 4a
SSE4.1 - Supports Streaming SIMD Extensions 4.1
SSE4.2 - Supports Streaming SIMD Extensions 4.2

Thanks

Stephen

Solid Angle Support

[Anonymous]

when i went enable the mtoa.dll plugin, i received this error:

// Error: line 1: The specified module could not be found.
(mtoa) //
 

please help me!

[seachordjr]

This worked for me, I downloaded the installer and ran it. The first time it gave me the option to uninstall the original version, did that and ran the installer again and when I finished the install I ran Maya 2017 and it worked. 

[herrucan.schmitt]

I have the same problem: 

Im Currently learning maya and wanted to render a frame - my maya crashed

then i saw that i didnt got mota yet so i downloaded from https://www.solidangle.com/arnold/download/#arnold-for-maya (im using maya 2017)

but i cant check that box it just gives me an error in line 1

[Stephen.Blair]

---

@herrucan.schmitt wrote:

I have the same problem: 

Im Currently learning maya and wanted to render a frame - my maya crashed

then i saw that i didnt got mota yet so i downloaded from https://www.solidangle.com/arnold/download/#arnold-for-maya (im using maya 2017)

but i cant check that box it just gives me an error in line 1

---

Maya 2017 Update 1 and MtoA 1.4.0?

What OS?

Please go through the steps listed here:

https://arnoldsupport.com/2016/11/08/mtoa-the-renderer-arnold-used-by-this-scene-is-not-currently-av...

[Anonymous]

I have freshely installed Maya 2017 on Win7 64bit pro and could not start MTOA (I don't have any other versions of Arnold/mtoa).

Unable to dynamically load : C:/solidangle/mtoadeploy/2017/plug-ins/mtoa.mll

(default installation path, correct)

CPU (i7 4790K):

SSE             *       Supports Streaming SIMD Extensions
SSE2            *       Supports Streaming SIMD Extensions 2
SSE3            *       Supports Streaming SIMD Extensions 3
SSSE3           *       Supports Supplemental SIMD Extensions 3
SSE4a           -       Supports Streaming SIMDR Extensions 4a
SSE4.1          *       Supports Streaming SIMD Extensions 4.1
SSE4.2          *       Supports Streaming SIMD Extensions 4.2

The dependancyWorker, started from Maya MEL shows an empty window. Trying to enable mtoa from Maya then doesn't do anything to it.

I have then installed the Update 1.

No changes.

I then uninstaled MTOA, rebooted, got it from Solidangle and installed again, making sure "install for Maya" was enabled and rebooted.

No changes.

I don't see any Arnold/MTOA relevant environment variables set.

This site: https://arnoldsupport.com/category/mtoa/ isn't very helpful, I don't know about the correct paths to set (eg the directory "alShaders" is not present in c:\solidangle).

Could someone pls walk me through the environment variables?

Where should ARNOLD_PLUGIN_PATH point to? C:\solidangle\mtoadeploy\2017\bin ?

I can only see, that MAYA_CUSTOM_TEMPLATE_PATH = "C:/solidangle/mtoadeploy/2017/scripts/mtoa/ui/templates;C:/Program Files/Autodesk/Extra/MtoA/scripts/mtoa/ui/templates", where the second part leads to nonexisting directory "Extra/MtoA/scripts/mtoa/ui/templates".

Thank you.

[Stephen.Blair]

The env vars to check would be things like MAYA_SCRIPT_PATH, MAYA_PLUGIN_PATH, and PYTHONPATH.

ARNOLD_PLUGIN_PATH and MAYA_CUSTOM_TEMPLATE_PATH  don't matter for loading MtoA.

It's unusually that Dependency Walker would not show anything when you load mtoa.mll.

Can you get a Process Monitor log and share it?

https://arnoldsupport.com/2016/11/08/mtoa-unable-to-dynamically-load-mtoa-mll-the-specified-module-c...

[Anonymous]

> It's unusually that Dependency Walker would not show anything when you load mtoa.mll.

Nope, just stupidity. I thought I had to load the mll in maya and expected that Dependency Walker magicaly updates.

I've attached the pml as well as dwi files.

Thank you.