See attached image.
Any ideas what might cause this…maybe a memory problem??
It is …not enough RAm or something???
thanks
It would help if you said what script this is. But when such an error occurs, the solution is normally to simply restart ZBrush.
It happened on one of my collegues machines…I’ll ask her to make a note
of which script she used when it happened next time.
cheers
Wild Guess… PMData might mean Projection Master?
Sven
Nah, just means ZB’s been working without a lunch break. PMData is afternoon data. 
Seriously, this just happens sometimes; best to save often. Sven, I’ve been meaning to tell you I managed to get it to occur reproducibly with looped routines.
Hi Marcus,
Details please. If you will, send me a script that reproduces it?
Whenever this warning pops up, (as Aurick says) it’s best to restart ZBrush.
The good thing about the error message is: whatever the internal state that precipitates it, ZBrush neither freezes nor aborts. You should take the message as a warning and simply save everything you are working on, quit, then reload everything after a fresh boot.
I’d like to nail the cause since it’s something several of us are doing in ZScripts. I know for a fact that some of my scripts (ZMats for one) will give a similar message after extended use: “number of inputs exceeds the number of inputs defined by the target routine”, while displaying one of my own routinecalls.
Sven
Sven,
I will send you the script - although I don’t think it will help ‘solve’ the issue. I think that its occurence - even with Projection Master - is because of the way ZB handles scripts internally rather than… bad scripting! :o