OTOY Forums

phaskins
Ooops!
It's the first time when Autodesk broke this formal registry path system... There was always "...\2011\...", "...\2012\..." paths...
Thank you for report. It will be fixed in installator in the next version (it is almost ready, I will release it in a few hours).
As a "quick-fix", if you want to get it installed right now, you can just add the path "HKLM\SOFTWARE\Wow6432Node\Autodesk\Maya\2013\Setup\InstallPath" and create there the string value key "MAYA_INSTALL_LOCATION" holding the path to your Maya installation (just copy it from the same key from 2013.5 path). After it you may run the installator and all will be OK.

JimStar wrote:phaskins
Ooops!
It's the first time when Autodesk broke this formal registry path system... There was always "...\2011\...", "...\2012\..." paths...
Thank you for report. It will be fixed in installator in the next version (it is almost ready, I will release it in a few hours).
As a "quick-fix", if you want to get it installed right now, you can just add the path "HKLM\SOFTWARE\Wow6432Node\Autodesk\Maya\2013\Setup\InstallPath" and create there the string value key "MAYA_INSTALL_LOCATION" holding the path to your Maya installation (just copy it from the same key from 2013.5 path). After it you may run the installator and all will be OK.

Thanks for you help Jim! In addition, I think I heard the tools guys here at work say that the plugins had to be recompiled between 2013 and 2013.5. I'm not sure if this is correct or not.

phaskins wrote:Thanks for you help Jim! In addition, I think I heard the tools guys here at work say that the plugins had to be recompiled between 2013 and 2013.5. I'm not sure if this is correct or not.

Yep! I just looked at it - Maya 2013 Extension breaks binary compatibility with Maya 2013.
It's too much weird things for one "extension"... I think I will not be able to add this binary compatibility to today release...
See PM please.