Some of our Artists really like using Vertex Chameleon, but a compiled version was not released for Maya 2015. The company has released the source code so that you can compile it yourself. I compiled it, and a lot of the operations work, but operations involving vertex color layers are broken. Applying vertex colors to a model without layers works fine. But when layers are created, the vertex colors look corrupted, with black splotches all over the place.
Has anyone else tried compiling this for Maya 2015? The company no longer supports the product, so Iâm not sure where else to look for help.
After some investigation, it looks like something broke between Maya 2014 and 2015. I came up with a test case where I created a color set (using Mayaâs Color Set Editor) and then applied vertex colors (using the Maya API function MFnMesh::setFaceVertexColors). It worked in Maya 2014 but the colors got messed up in Maya 2015.
Interesting to note that the colors only get messed up if there is a âcreateColorSetâ node in the construction history. Will have to do some more digging.
UPDATE: Autodesk just released Service Pack 6 for Maya 2015, and they fixed the bug! (MAYA-51689 Fixed the setFaceVertexColors API )
So anyone compiling Vertex Chameleon for Maya 2015 should no longer have to figure out a workaround for VertexPolyColourCommand.cpp. On a side note, there is one more fix that needs to be made to get the plug-in to run on 2015 64-bit. In the file RH_VCP_Base.mel, I had to change
[QUOTE=RFlannery;27334]UPDATE: Autodesk just released Service Pack 6 for Maya 2015, and they fixed the bug! (MAYA-51689 Fixed the setFaceVertexColors API )
So anyone compiling Vertex Chameleon for Maya 2015 should no longer have to figure out a workaround for VertexPolyColourCommand.cpp. On a side note, there is one more fix that needs to be made to get the plug-in to run on 2015 64-bit. In the file RH_VCP_Base.mel, I had to change
if (endsWith($mayaVersion, "x64"))
to
if (`about -is64`)
[/QUOTE]
I patched it with this change, and compiled the 64-bit version for Maya 2015 and built an installer. Itâs just the 64 bit version for 2015.
Was interested in trying this out and as I do not have Maya 2015 installed and prefer to work in 2016 anyway, I had a quick go at compiling Vertex Chameleon for Maya 2016 on Windows. Managed to get it to a point where I can start a build and get 2k+ errors like " âminâ: identifier not found " and other stuff that make me think my paths are still not correct. I have not touched anything C++/Visual Studio/building related in a while so I might be overlooking something very simple. Iâm on Win10/VS2015 here, that might of course be a problem. Going to sleep and maybe giving this another try tomorrow.
If anyone has the .mll lying around, feel free to share! :laugh:
Hmmmm, got it built but having trouble with licensing. The plugin is free to use and the company give a license key in their manual. Itâs this one:
contact@renderheads.com-(0 user license)-RenderHeads-RenderHeads-Vertex
Chameleon 1.x-702S-6600-6C22-4861-702S-6600-4K22-4861-0N66-4R0G-546U-5N6X
But when I try to enter I get the following in the Script Editor:
Error: line 1: Syntax error: unexpected end - at position 2 while parsing:
x-*
and also, more worryingly:
Error: line 0: Cannot find procedure âRHEnterLicenseâ.
The only reference in the mel scripts to âRHEnterLicenseâ is in RenderHeadsBase.mel in the code that is supposed to send the key over to the compiled plugin code and Iâm afraid itâs missing the function because I built in some bogus way.
Download VS2015, just for this :laugh: The VS solution got migrated to VS2015 on first open, of course.
I also downloaded the Win10 Windows Kits and pointed VS at those in Include Directories instead of the Win8.1 ones (um, shared, winrt), but I doubt that makes any difference
Make sure /include and /lib from the downloaded devkit are in C++ Additional Include Directories and Additional Library Directories (lib64 not needed; I wasusing $(MAYALIBBASE) as instructed by the github readme, but that does not matter).
Add MAYA2016 to Preprocessor Definitions
Add â#include <algorithm>â to MayaUtility.h to make min & max work
?? remove WIN32 from Preprocessor Definitions ??
^ this was the critical step in making the build go through, but I wonder if thatâs also what makes the final .mll not work correctlyâŚ?
Change linker Output File from $(OutDir)VertexChameleon2016.mll to $(OutDir)MayaVertexChameleonPlugin.mll
After building rename the file to VertexChameleon2016.mll again
Awesome! :):
Thank you so much!
Got the interface working but error message :sigh: when trying to work with it:
Installed old version of vertex chamelean via their website
on Windows 10 (x64) for Maya 2016.
Overwrote all folders in the installation directory with TheMaxxâs dropbox-content.
In maya 2016 put âRH_VertexChameleonâ in mel.
and got the interface but also an error message:
â//Warning: file: C:/Program Files (x86)/RenderHeads/VertexChameleon 1.0/scripts/RH_VertexChameleon.mel line 631: The -bs/-borderStyle flag is obsolete and should not be used.â
When trying to use functions from vertex chameleon interface it doesnât work
plus I get the following error message:
â// Error: line 0: Cannot find procedure âRH_VertexPolyColourâ.â
[QUOTE=mercurius;29934]
3) In maya 2016 put âRH_VertexChameleonâ in mel.
and got the interface but also an error message:
â//Warning: file: C:/Program Files (x86)/RenderHeads/VertexChameleon 1.0/scripts/RH_VertexChameleon.mel line 631: The -bs/-borderStyle flag is obsolete and should not be used.â
[/QUOTE]
I havenât looked at the files in the dropbox location. But I know that when we updated the plugin for 2016, I had to go through all the MEL scripts, look for â-borderStyleâ and delete those flags. It wonât break anything if you leave it in there, but you will keep getting that warning message over and over.
[QUOTE=mercurius;29934]
4) When trying to use functions from vertex chameleon interface it doesnât work
plus I get the following error message:
â// Error: line 0: Cannot find procedure âRH_VertexPolyColourâ.â
Did I overlook anything when installing?[/QUOTE]
âRH_VertexPolyColourâ is a command defined by the plugin. If you go to Mayaâs Plug-in Manager, is Vertex Chameleon actually loaded?
Also, in Maya 2016, the âPolygonsâ menu set was replaced by the âModelingâ menu set. So that will have to be fixed up in a few places:
âRH_VCP.res.melâ - line 57. Change âAdd to Polygons Menuâ to âAdd to Modeling Menuâ.
âRH_VertexChameleon.melâ - Replace âpolygonsMenuSetâ with âmodelingMenuSetâ wherever you find it.
This is the easiest thing to do, but it means that the scripts will be broken for Maya 2015 and earlier. If you want it to work with both versions, you will have to add some conditional statements. For example:
int $version = VCP_GetMayaVersionNumber();
string $polyMS = "polygonsMenuSet";//`findMenuSetFromLabel "Polygons"`;
if ($version >= 2016)
$polyMS = "modelingMenuSet";//`findMenuSetFromLabel "Modeling"`;
[QUOTE=RFlannery;29936]
âRH_VertexPolyColourâ is a command defined by the plugin. If you go to Mayaâs Plug-in Manager, is Vertex Chameleon actually loaded?[/QUOTE]
Thanks for pointing at this!
Spot on.
The Maya plug-in manager has a drop down menu for
âC:/Program Files (x86)/RenderHeads/VertexChameleon 1.0/plug-insâ
However, no entries to underneath it indicating loaded/auto load.
[QUOTE=mercurius;29938]The Maya plug-in manager has a drop down menu for
âC:/Program Files (x86)/RenderHeads/VertexChameleon 1.0/plug-insâ
However, no entries to underneath it indicating loaded/auto load.[/QUOTE]
Hmmm, thatâs a strange one. Since the Plug-in Manager shows the path, I guess your MAYA_PLUG_IN_PATH is set correctly. Can you confirm that the .mll file from the dropbox download actually went into that folder?
[QUOTE=RFlannery;29939]Hmmm, thatâs a strange one. Since the Plug-in Manager shows the path, I guess your MAYA_PLUG_IN_PATH is set correctly. Can you confirm that the .mll file from the dropbox download actually went into that folder?[/QUOTE]
The âVertexChamleon2016.mllâ is in âC:/Program Files (x86)/RenderHeads/VertexC hameleon 1.0/plug-ins/2016â
Maybe something went wrong with the way I installed it.
I installed the older version to Maya 2016 and overwrote the folders.