Hya, I;ve been doing a lot of big Car files recently
.9 to say 1.2 gig and some of them are failing to open when I need to work on them again.
At first I thought it was a faulty mesh figure or something, but the same thing has just happened on a totally different file.
The error reads
this has happened a few times a long time ago but not for quite a while.
I’,m using build 126.96.36.199
Any clues welcome because I save incrementally but my hard drive is getting full (maybe that’s the reason?)
Using Windows Vista 64
Oh though the error pints to a dazdevelop directory I don’t have one on my drive
thanks in advance!!
(that will teach me for saying what a good stable program carrara is…)
That is a generic C++ error. Good catch on noting the directory path that doesn’t exist on your system—but that is a red herring and its safe to ignore. What you are seeing there is actually a bit of internal Daz information…the machine that Daz compiles their code on has that directory path.
Sometimes the filename can provide you with some guessing clues as to where the problem is. Unfortunately “MCToken.cpp” isn’t setting off any lights in my brain except “it is a C++ file.”
Could it be due to the large size of your scene files? Yeah…maybe…depending on what MCToken is supposed to be doing…maybe it ran off the end of some extra large array of stuff and the code isn’t robust enough to deal with the error properly. One could connect to the Carrara.exe process with a debugger and trace what went wrong. However, without the debugging symbols (only Daz has those), you’ll be clawing your eyes out in no time…unless you are a hardcore debugging guru (I’m not, but I know some…) who can work backwards from the Assembly code.
This might be an issue worthy of a technical support ticket (I’m loathe to say that given the instability of the ticketing system these days). I wish Daz would put better logging and error handling into their software though (SQL Server rocks at this). About the only other thing you can do is find ways to reduce your file size and see if this error still reproduces.
Wish I had something more to add here…