Tweet
This is in relation to a thread I made yesterday: http://forums.chaosgroup.com/showthr...rtex-color-map
I assumed I did some mistakes during the export from Houdini because I was constantly exporting a new alembic files to test various output settings and I couldn't get them to show up in the vertex map or user defined tab.
Today I recreated everything from scratch and noticed the following behavior:
When I start a new scene, create a vray proxy and import my alembic file with the custom attributes I get them to show up in the vertex map and user defined tab.
Now when I use the same proxy object and load a different alembic file with another set of attributes they are not updated. It shows me the attributes from the last loaded object. (user defined tab and vertex map)
Creating an additional vray proxy object and loading an alembic file will result in no attributes showing up in the user defined tab and vertex map.
Saving the scene with the two different vray proxy objects, closing max and opening the scene again will not fix the issue. It will still show the empty/not updated attributes
The only way to solve this is closing max and starting a new scene again. The first proxy you create will show everything correctly as long as you don't load a new alembic file.
Tested with: Vray 3.50 (official release not beta) and 3ds max 2017
I assumed I did some mistakes during the export from Houdini because I was constantly exporting a new alembic files to test various output settings and I couldn't get them to show up in the vertex map or user defined tab.
Today I recreated everything from scratch and noticed the following behavior:
When I start a new scene, create a vray proxy and import my alembic file with the custom attributes I get them to show up in the vertex map and user defined tab.
Now when I use the same proxy object and load a different alembic file with another set of attributes they are not updated. It shows me the attributes from the last loaded object. (user defined tab and vertex map)
Creating an additional vray proxy object and loading an alembic file will result in no attributes showing up in the user defined tab and vertex map.
Saving the scene with the two different vray proxy objects, closing max and opening the scene again will not fix the issue. It will still show the empty/not updated attributes
The only way to solve this is closing max and starting a new scene again. The first proxy you create will show everything correctly as long as you don't load a new alembic file.
Tested with: Vray 3.50 (official release not beta) and 3ds max 2017
Comment