disabling face robot and saving the scene really does remove it, but if you're using reference models, you'll need to save those too again because the face robot flag is on models.
On Mon, Oct 28, 2013 at 8:49 AM, Angus Davidson <angus.david...@wits.ac.za>wrote: > Hi Stephen > > That’s the theory. In practice not so much. We have spent hours trying > to remove it from files, and in one case last year it prevented one of the > students from using the render farm. No matter what we did it kept coming > back. > > Kind regards > > Angus > > From: Stephen Blair <stephenrbl...@gmail.com> > Reply-To: "softimage@listproc.autodesk.com" < > softimage@listproc.autodesk.com> > Date: Monday 28 October 2013 at 2:16 PM > > To: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com> > Subject: Re: FaceRobot > > Disable and save scene. That's it. Is the property really is an > infection? > > > > On Mon, Oct 28, 2013 at 7:41 AM, Angus Davidson <angus.david...@wits.ac.za > > wrote: > >> Have to agree. For all the good that face robot can do. Especially with >> students who hit the incorrect buttons on occasions its a lifetime of grief >> trying to get rid of the damn thing. Face Robot should not have a default >> key binding. Plain and simple. Also when you deactivate face robot you >> should be given a prompt to remove the rest of its infection from the file. >> >> >> >> From: "pete...@skynet.be" <pete...@skynet.be> >> Reply-To: "softimage@listproc.autodesk.com" < >> softimage@listproc.autodesk.com> >> Date: Monday 28 October 2013 at 12:13 PM >> To: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com> >> Subject: Re: FaceRobot >> >> given the insidious behaviour of FaceRobot, this should really be >> given some thought for the future. >> >> In every studio I went since FaceRobot exists, it has been perceived as >> something akin to a virus, spontaneously messing around and infiltrating >> production scenes. Every single production, some time is spent to keep it >> out reliably and do some housekeeping after it reared its ugly head. I >> think many people don’t want anything to do with it because of this. It’s >> the obnoxious child that everyone dislikes. >> Surely it could be taught more appropriate out of the box behaviour? >> >> I mean, if ICE was acting like that, people would be on the barricades, >> raiding what’s left of Softimage headquarters. >> >> >> *From:* gareth bell <garethb...@outlook.com> >> *Sent:* Sunday, October 27, 2013 7:40 PM >> *To:* softimage@listproc.autodesk.com >> *Subject:* RE: FaceRobot >> >> oh - and that can be scripted.... >> >> Application.DisableFaceRobot() >> >> >> ------------------------------ >> From: garethb...@outlook.com >> To: softimage@listproc.autodesk.com >> Subject: RE: FaceRobot >> Date: Sun, 27 Oct 2013 18:20:06 +0000 >> >> Yeah we've had this before. Normally just disabling facerobot (whilst >> switched to softimage layout) and then saving (probably a new version is >> safer) tends to get rid of it. Also try unloading it in your workgroups and >> deleting the custom property too. >> >> >> ------------------------------ >> Date: Sat, 26 Oct 2013 17:48:08 -0400 >> Subject: Re: FaceRobot >> From: stephenrbl...@gmail.com >> To: softimage@listproc.autodesk.com >> >> Don't you have to disable Face Robot in the scene? >> >> http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=15241146&linkID=12544120 >> >> >> On Sat, Oct 26, 2013 at 5:31 PM, Michael Heberlein < >> micheberl...@gmail.com> wrote: >> >> If deleting the property is enough, you could do this in an >> "siOnBeginSceneSave[As]" event. >> Am 26.10.2013 21:06 schrieb "Ognjen Vukovic" <ognj...@gmail.com>: >> >> Hi Philipp, >> >> Not having much luck, the number of scenes is already in the triple >> digits so maybe some automation would solve everything but i have to take >> into account that the deadline is in three days so i think it would be to >> risky >> now to try anything, i contemplated seriously deleting it from disk while >> the project was running but im going to wait a couple more days and nuke it >> from orbit the day we hand over the final. >> >> Ogi. >> >> >> On Sat, Oct 26, 2013 at 8:47 PM, philipp seis <dpi...@gmail.com> wrote: >> >> hello Ognjen...yup thats nasty. Could you fix it already ? If not: We >> batched all infected scenes: opening it, disabling facerobot by deleting >> the facerobot custom property, saving and closing it. voila. I recall, that >> my first approach was also fiddeling with the workgroup, but with not much >> success. Good luck ! >> >> >> 2013/10/26 Ognjen Vukovic <ognj...@gmail.com> >> >> I was considering it but we are in the middle of a project, what are the >> chances it will botch something up? >> >> >> On Sat, Oct 26, 2013 at 6:16 PM, Luc-Eric Rousseau >> <luceri...@gmail.com>wrote: >> >> Try deleting the face robot workgroup from.disk >> Le 2013-10-26 07:40, "Ognjen Vukovic" <ognj...@gmail.com> a écrit : >> >> Is there a way to remove face Robot from a work-group and generally >> from existence? >> >> We are having a awesome time as someone in the early phases of the >> project had it open somewhere in their scene and now it has reared its ugly >> tentacles into the whole project, literally every model, scene and project >> have been infected, in all this chaos i am sure i even saw it initialize >> once when someone opened up after effects... >> >> Is there a way to exorcise face robot from this project without >> offering a sacrifice to Cthulhu? >> >> Thanks in advance, >> Ogi. >> >> >> >> >> >> >> >> >> >> This communication is intended >> for the addressee only. It is confidential. If you have received this >> communication in error, please notify us immediately and destroy the >> original message. You may not copy or disseminate this communication without >> the permission of the University. Only authorised >> signatories are competent to enter into agreements on behalf of the >> University and recipients are thus advised that the content of this message >> may not be legally binding on the University and may contain the personal >> views and opinions of the author, which >> are not necessarily the views and opinions of The University of the >> Witwatersrand, Johannesburg. All agreements between the University and >> outsiders are subject to South African Law unless the University agrees in >> writing to the contrary. >> >> > This communication is intended for the addressee only. It is > confidential. If you have received this communication in error, please notify > us immediately and destroy the original message. You may not copy or > disseminate this communication without the permission of the University. Only > authorised signatories are competent to enter into agreements on behalf of > the University and recipients are thus advised that the content of this > message may not be legally binding on the University and may contain the > personal views and opinions of the author, which are not necessarily the > views and opinions of The University of the Witwatersrand, Johannesburg. All > agreements between the University and outsiders are subject to South African > Law unless the University agrees in writing to the contrary. > >
