search

anderslanglands / alShaders2

BSD 3-Clause "New" or "Revised" License
75 stars 38 forks source link

2.0.0-beta3 | AOVs missing #32

Closed chittyren closed 6 years ago

chittyren commented 6 years ago

I'm having trouble getting the latest beta release working for Maya 2018.2. The cryptomatte AOVs aren't showing up in the "Available AOVs" list.

Here are my specs:

Windows 10 Pro (build 16299) Maya 2018.2 / mtoa 2.1.0.1 (Arnold Core 5.0.2.1) (mtoa is installed locally) 2.0.0-beta3 release

Here is what I've tried:

Is there anything I'm missing with installation of Beta3 release? Any advice or assistance would be greatly appreciated! Let me know if there is any additional information I can provide.

Thanks in advance!

jonahfriedman commented 6 years ago

I don't really know, but a piece of info that might help you: The AOVs are specified by the .mtd file, so I would look to that to see what's wrong. Maybe you have an old one also installed somewhere?

Is there anything I'm missing with installation of Beta3 release?

There's nothing special about Beta3 as far as installation is concerned.

jonahfriedman commented 6 years ago

Closing this - hope you got it figured out.

SchmuckerDaniel commented 6 years ago

I've been having the exact same problem. Have been trying to get Beta3 going in a number of different ways without any success. Tried beta2 just now, worked without a problem.

jonahfriedman commented 6 years ago

First, if the AOVs do not show up in the list that means it either can't find the executable (dll on windows), or the ".mtd" file.

@chittyren - I noticed something in your env variables in Maya:

ARNOLD_PLUGIN_PATH = ;C:/path/to/alShaders-win-2.0.0b3-ai5.0.1.0;C:/solidangle/mtoadeploy/2018/shaders;C:/solidangle/mtoadeploy/2018/procedurals

If that directory, C:/path/to/alShaders-win-2.0.0b3-ai5.0.1.0, is just the unzipped folder downloaded from the releases, then the correct path for ARNOLD_PLUGIN_PATH is:

C:/path/to/alShaders-win-2.0.0b3-ai5.0.1.0/bin (Note the /bin on the end).

Hope this helps. I'm not an expert on Maya deployment strategies. That said, I have no idea why dumping the files in mtoadeploy/2018/bin/ wouldn't work.

jonahfriedman commented 6 years ago

Oh, and make sure you have the Visual Studio 2015 Redistributable installed.

chittyren commented 6 years ago

Hey Jonah, Still no luck with any of the following actions.

Oh, and make sure you have the Visual Studio 2015 Redistributable installed.

I fixed my mod file per your notes. So the /bin is apart of the cryptomatte path.

I've tried Visual Studio 2015 (x64 & x86), even downloaded Visual Studio 2017 per the link on the release notes. Did this with all the tests I've done before, and the AOVs still don't show up.

I'm hesitant suggesting to compile the source on my end, as I've never done it before. And would not want to bug you with learning how to do that. I can use Beta2 in the meantime until something else breaks. As Schmucker noted, it works as expected.

jonahfriedman commented 6 years ago

Does the shader appear in Maya at all, i.e. can you create a Cryptomatte shader?

chittyren commented 6 years ago

No, I don't see the cryptomatte node in the hypershade using Beta3. I can with Beta2 though.

jonahfriedman commented 6 years ago

Just a note- the fact that the shader can't be created in the hyperahde probably means it doesn't load at all, and doesn't have to do with the metadata. The 2017 redistributable is a possible reason why, though you say you've already installed that. You can try beta 4, but that requires the same redistributable, so it's unlikely to be different.

chittyren commented 6 years ago

@jonahfriedman - Any updated information on a potential fix for this issue? I've tried beta4 and as you predicted it doesn't work. I'm still struggling to figure out why the plugin isn't loading. I've reinstalled all the relevant Microsoft Visual C++ Distros for Maya 2018 as well as the Visual C++ 2017 Distros to fix an unrelated issue and still had no luck with beta3 and up.

anderslanglands commented 6 years ago

Can you try setting your startup log verbosity to 2 and add the contents on your output window on maya startup here? https://support.solidangle.com/display/arnsupp/2014/06/26/%5BMtoA%5D+Setting+the+startup+log+verbosity

On Fri, 22 Jun 2018 at 10:45 Alex Kline notifications@github.com wrote:

@jonahfriedman https://github.com/jonahfriedman - Any updated information on a potential fix for this issue? I've tried beta4 and as you predicted it doesn't work. I'm still struggling to figure out why the plugin isn't loading. I've reinstalled all the relevant Microsoft Visual C++ Distros for Maya 2018 as well as the Visual C++ 2017 Distros to fix an unrelated issue and still had no luck with beta3 and up.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/anderslanglands/alShaders2/issues/32#issuecomment-399266540, or mute the thread https://github.com/notifications/unsubscribe-auth/AB2IXUZ0AY_5pEb5mXDy0I6PAD15pJBcks5t_CIDgaJpZM4T3bn_ .

baiking commented 6 years ago

I've got the same problem,beta2 work for mtoa 2.1.x.x, beta3/4 only work for mtoa 3.0.x The log say: cryptomate.dll was compiled against not-compatible Arnold 5.1.0.1

chittyren commented 6 years ago

@anderslanglands - Here is the full log from startup. Looks to be the same issue as baiking reported.

00:00:00   878MB         | log started Fri Jun 22 10:28:13 2018
00:00:00   878MB         | Arnold 5.0.2.1 [0c7988c0] windows icc-17.0.2 oiio-1.7.17 osl-1.9.0 vdb-4.0.0 clm-1.0.3.513 rlm-12.2.2 2017/11/17 14:49:26
00:00:00   878MB         | running on cgi11, pid=10248
00:00:00   878MB         |  2 x Intel(R) Xeon(R) CPU E5-2687W v3 @ 3.10GHz (20 cores, 40 logical) with 130987MB
00:00:00   878MB         |  Windows 8 Professional (version 6.2, build 9200)
00:00:00   878MB         |  soft limit for open files raised from 512 to 2048
00:00:00   878MB         |  
00:00:00   878MB         | loading plugins from R:/resources/_ns_tools/maya/plugins/cryptomatte/2.0.0b4/win/bin ...
00:00:00   878MB WARNING |  cryptomatte.dll was compiled against non-compatible Arnold 5.1.0.1
00:00:00   878MB         | no plugins loaded
00:00:00   880MB         | loading plugins from R:/resources/_ns_tools/maya/plugins/cryptomatte/2.0.0b4/win/bin ...
00:00:00   880MB WARNING |  cryptomatte.dll was compiled against non-compatible Arnold 5.1.0.1
00:00:00   880MB         | loading plugins from R:/resources/_ns_tools/maya/plugins/mtoa/2.1.0.1/2018/win/shaders ...
00:00:00   882MB         | loading plugins from R:/resources/_ns_tools/maya/plugins/mtoa/2.1.0.1/2018/win/procedurals ...
00:00:00   882MB         | loaded 123 plugins from 10 lib(s) in 0:00.05
00:00:00   888MB         | loading plugin: C:/Program Files/Autodesk/bifrost/1.5.0/Arnold-5.0.0.0/bin/bifrost_procedural_0_1.dll ...
00:00:00   888MB         | loaded 5 plugins from 1 lib(s) in 0:00.00
00:00:00   889MB         | Successfully imported python module 'arnold'
00:00:00   889MB         | Successfully imported python module 'mtoa'
00:00:01   891MB         |  
00:00:01   891MB         | releasing resources
00:00:01   890MB         | Arnold shutdown
anderslanglands commented 6 years ago

Huh. I changed this a while ago. Let me check. On Sat, 23 Jun 2018 at 02:36, Alex Kline notifications@github.com wrote:

@anderslanglands https://github.com/anderslanglands - Here is the full log from startup. Looks to be the same issue as baiking reported.

00:00:00 878MB | log started Fri Jun 22 10:28:13 2018 00:00:00 878MB | Arnold 5.0.2.1 [0c7988c0] windows icc-17.0.2 oiio-1.7.17 osl-1.9.0 vdb-4.0.0 clm-1.0.3.513 rlm-12.2.2 2017/11/17 14:49:26 00:00:00 878MB | running on cgi11, pid=10248 00:00:00 878MB | 2 x Intel(R) Xeon(R) CPU E5-2687W v3 @ 3.10GHz (20 cores, 40 logical) with 130987MB 00:00:00 878MB | Windows 8 Professional (version 6.2, build 9200) 00:00:00 878MB | soft limit for open files raised from 512 to 2048 00:00:00 878MB | 00:00:00 878MB | loading plugins from R:/resources/_ns_tools/maya/plugins/cryptomatte/2.0.0b4/win/bin ... 00:00:00 878MB WARNING | cryptomatte.dll was compiled against non-compatible Arnold 5.1.0.1 00:00:00 878MB | no plugins loaded 00:00:00 880MB | loading plugins from R:/resources/_ns_tools/maya/plugins/cryptomatte/2.0.0b4/win/bin ... 00:00:00 880MB WARNING | cryptomatte.dll was compiled against non-compatible Arnold 5.1.0.1 00:00:00 880MB | loading plugins from R:/resources/_ns_tools/maya/plugins/mtoa/2.1.0.1/2018/win/shaders ... 00:00:00 882MB | loading plugins from R:/resources/_ns_tools/maya/plugins/mtoa/2.1.0.1/2018/win/procedurals ... 00:00:00 882MB | loaded 123 plugins from 10 lib(s) in 0:00.05 00:00:00 888MB | loading plugin: C:/Program Files/Autodesk/bifrost/1.5.0/Arnold-5.0.0.0/bin/bifrost_procedural_0_1.dll ... 00:00:00 888MB | loaded 5 plugins from 1 lib(s) in 0:00.00 00:00:00 889MB | Successfully imported python module 'arnold' 00:00:00 889MB | Successfully imported python module 'mtoa' 00:00:01 891MB | 00:00:01 891MB | releasing resources 00:00:01 890MB | Arnold shutdown

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/anderslanglands/alShaders2/issues/32#issuecomment-399464391, or mute the thread https://github.com/notifications/unsubscribe-auth/AB2IXZ1pG6jWHsG4Zjwye-YzM5yGXXjaks5t_QECgaJpZM4T3bn_ .

3b33 commented 6 years ago

Not getting the AOVs either with beta 4. Maya 2018.2, Arnold 2.0.2.1, win10. Any news on this?

jonahfriedman commented 6 years ago

We're moving the repo to Psyop/CryptomatteArnold very soon, this issue should be fixed. OS X should be up soon, at which time we'll replace this repo's readme.md with a note that it has moved.

"AOVS not showing up" is better described as the shader not loading, and the reason for this was that that Cryptomatte was built with a newer version of Arnold for the version you are using. It is now built against 5.0.1.0, and with Visual Studio 2015 (and not 2017), so it should be fixed.

If the issue isn't solved, please open an issue on the new repo.

chittyren commented 6 years ago

Just wanted to follow up. Updating to the latest release from the CryptomatteArnold repo fixed this issue for us! Thank you @jonahfriedman !