Access violation in MkVarTag

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 12/06/2003 at 20:04, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   8.100
Platform:   Windows ;   Mac OSX ;
Language(s) :     C++ ;

---------
op = PolygonObject::Alloc(vcount,fcount); (998,1515)
if(!op) return 0;
uvtag = (UVWTag* )op->MakeVariableTag(vtcount); (998)
if(!uvtag) return 0;

The forth time I create an object I get a 'unhandled exception in Cinema4D.exe Access Violation' error in the MakeVariableTag call. I'm only creating one UVtag per object at this point.

What would prevent me from making a call with a valid PolygonObject? I would expect it would at worst return null.

I'm having a similar problem with the ResizeObject. When I resize the third object I get the same error and then the Access error on trying to make the UV tag on the fourth if I comment out the resize call.

I have 1.5 G memory on this box now.

What would cause these types of problems (not at all assuming it's the app code and not me)?

Thanks,
David

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/06/2003 at 13:12, xxxxxxxx wrote:

hi,
MakeVariableTag(vtcount) works like that?? Shouldn´t the compiler cry?
Have you tried this: (UVWTag* )op->MakeVariableTag(Tuvw,vtcount,NULL);
You aren´t specifying the type of tag at all...weird that your compiler compiles this, mine doesn´t...
I don´t know though if this is the problem.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/06/2003 at 13:35, xxxxxxxx wrote:

Sorry - typo
the call I make is

(UVWTag* )op->MakeVariableTag(Tuvw,vtcount);
the last value defaults.

(No email on my work PC)

david

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/06/2003 at 13:36, xxxxxxxx wrote:

Are you freeing your the polygonobject at the end? Have you tried to do some debug sessions to find out where exactly it crashes?