Tvertexmap in IN_EXCLUDE
-
On 15/04/2013 at 15:00, xxxxxxxx wrote:
User Information:
Cinema 4D Version:
Platform:
Language(s) :---------
I'm trying to only accept Vertex-Maps in my In-Exclude list. Could it be that it is not possible to
do by using the identifier? It's rather inconvenient to use the integer symbol instead.// Works IN_EXCLUDE FOOBAR_PARAMETER { ACCEPT { 5682; } // Does not IN_EXCLUDE FOOBAR_PARAMETER { ACCEPT { Tvertexmap; }Cheers,
-Niklas -
On 16/04/2013 at 00:16, xxxxxxxx wrote:
Hi Niklas,
Yes, we have to always use integer IDs, not name IDs, in resource files. This is a limitation of the resource system.
-
On 16/04/2013 at 01:11, xxxxxxxx wrote:
Are you sure that's right Yannick? Here's a line from one of my resource files which works fine:
LINK XMCO_COVER_SELTAG { ANIM OFF; ACCEPT { Tpolygonselection; Tpointselection; 5682; } }If I substitute 'Tvertexmap' for '5682' it doesn't work correctly, but it is fine with the other two name IDS.
-
On 16/04/2013 at 02:08, xxxxxxxx wrote:
Hi Steve,
Originally posted by xxxxxxxx
Are you sure that's right Yannick? Here's a line from one of my resource files which works fine:
LINK XMCO_COVER_SELTAG { ANIM OFF; ACCEPT { Tpolygonselection; Tpointselection; 5682; } }If I substitute 'Tvertexmap' for '5682' it doesn't work correctly, but it is fine with the other two name IDS.
I spoke too soon. Yes, you're right.
In the case of the Tvertexmap and other types we have to use the literal value.
I'll ask the developers because all the types are declared in ge_prepass.h so we could use them all in a description. -
On 16/04/2013 at 04:17, xxxxxxxx wrote:
Thanks for your answers. Yes it works for me with other types as well, that is why I wondered why it doesn't work with the Tvertexmap. I thought it would go for the already registered descriptions, but then Tvertexmap should work, shouldn't it?
-Niklas
-
On 16/04/2013 at 04:21, xxxxxxxx wrote:
jeah i have also ran into that behaviour some time ago. the same goes for almost
all mograph objects.