Hi all, After some digging and finding nothing on performance with Interpolators at the Sun site I did find a saving snippet from this lists archive! Maybe it should be added to one of the FAQs? As this seems to at least trouble more then just me! :) To sum up, as Interpolators are kicked into life on every frame and having a few of them can add a fair amount of load to the system. You can either rewrite the Interpolators classes to wake up less often or add a delay to the FrameCycleTime. As my 3D scene is only a visualisation of my underlying data and other user interfaces I don't need it to be the highest priority so changing the default MinimumFrameCycleTime from "0" to "100" leaves room for all the non-rendering processes. Now I can look around faster, activate pick methods faster and mess with the Swing components of my App without having to wait 1 sec for them to update/active. :-) su.getViewer().getView().setMinimumFrameCycleTime(100); Does the trick for me. I found in my App that a smaller value kept the CPU% at 100% and response low but a larger value made the scene too jumpy when navigating. Not rocket science I know, but it's been the most impressive performance boost I've been able to achieve so far with my code. :) Jason. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
