Hi Nick, If Kronos is unable to process on the GPU, it will fall back to the CPU to finish processing. The most likely reason for this is that the GPU ran out of memory, but it could be that some other error occurred. When this happens it will have to start the render again from the beginning on the CPU, so it will take longer than rendering on the CPU from the start would have done. I think this fallback could be what you're seeing; you should be able to confirm (or otherwise) by watching the CPU activity while the GPU-enabled Kronos is processing. If it is really running on the GPU, the CPU use should be minimal.
If the GPU is not being used, I'd recommend you send your script and machine specs in to Support so they can investigate why not. Regards, Lucy On Mon, Dec 5, 2016 at 5:38 AM, Nick Guth <[email protected]> wrote: > I only have a single GPU on this machine (980Ti). Still trying to figure > it out, but no combination of settings seems to make it process faster than > my CPU. > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > -- Lucy Wilkes Lead Software Engineer - Nuke Engine The Foundry 5 Golden Square, London, W1F 9HT Tel: +44 (0)20 7479 4350 Web: www.thefoundry.co.uk Email: [email protected] The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
