Thanks for the tip on a workaround for the oslMap problem in the new version. I must say this sort of API change is really irritating. It took me quite a lot of time and effort to get that osl code to work in the first place, and I'm not really looking forward to redoing it. It would be really nice if some level of backwards compatibility were insured. I understand your suggestion about not putting oslMap calls into my session files, but at the time I had no reason to expect the API to change, and I based my code on reading parts of the existing chimera code. I still have no concrete feel for what parts of the API might be stable and what parts might not. Sorry for the rant, just feeling a little frustrated... ---------------------------------------------------------------------------- Steven Ludtke, PhD | Baylor College of Medicine sludtke@bcm.tmc.edu | Asst. Professor & Co-Director stevel@alumni.caltech.edu | National Center For Macromolecular Imaging V: (713)798-6989 | Dept of Biochemistry and Mol. Biol. instant messenger: sludtke42 | http://ncmi.bcm.tmc.edu/~stevel | * Thought is the arrow of time *