While not promising any fixes, I would be intrigued to see what you've got if you want to share it. If you could tar your net, cfg, C program, and test data, I bet it would be a pretty small file, so you could attach it to email. If you don't want to share it with the whole list, send it to me personally. If you don't want to that's OK, too!
I can run it on an SGI and see if I get the same behavior with the Image flashing. I didn't realize -script mode disallowed DXLink. Anyone else have any insight on that issue? Are you invoking DX from within your program? (DXLStartDX?) See the Programmers Guide, for DXLink for more info. I guess I can believe you can't start it in script mode per se, but I can't believe you can't run a DXLink app that needs only Image and not the whole UI. This may still not solve the flashing problem though. Is the Image size or view changing each iteration or is it just the redraw that is annoying? To lock the size/view, find a good view with test data then Export the camera output from Image (middle output) to a cam.dx file. Throw away the Export module, then Import (cam.dx) and feed it to the "defaultCamera" input on Image. You must first open the Image Config Dialog by clicking the Image module (not window) and pressing Ctrl-F to see and then unhide this input. Thereafter the Image camera will be your chosen camera on reset. There is also a Reset toggle in there that you may want to set to off. You might also try software rendering mode to see what happens. Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED] (607) 257-8335 or (607) 254-8794
