CompuServe Messages

I am able to run a slave render session in the background, and run a foreground 3ds sesion for modelling. Due to some highly technical reasons <g>, you cannot render in the foreground if you do this (unless you hold the shift key down during the render setup). For the most part, you can't ever tell the background session is sucking up spare cpu cycles. I run Warp at home, and 2.11 at the office (due to network requirements). I find that I like Warp better than 2.11, but I'm able to really wig Warp out every once in a while. I've seen some messages on internet where people have had the same problem as I've had, so maybe it will be a problem fixed by the first CSD (corrective service [?] disks). While running just a foreground session of 3ds, I show about a 10% increase in render time under Warp as compared to rendering under dos. Under 2.11, render times were slighly less versus dos. LAM