face_off wrote:Does it happen when you render with just each card individually? Have you tried using one card as your Windows display adapter and one card for rendering? Have you tried rendering when superfly is disabled (if that's even possible)? Have you got SLI disabled?
ie... there must be something different between our configurations that means you are getting the problem and others are not.
Thanks for the info. A few users are experiencing the same problems a you with drivers after 358.50, so there is definitely a problem, and Otoy are aware of it. I will pas on the information you've provided. Thanks.Summary: Poser Plugin does not work for me under no configuration when used with an nvidia driver later than 358.50.
Which is problematic as lots of other products either require later drivers or do not work reliably with the older driver version.
face_off wrote:After doing some searching on the web, I found some other suggestions...
1) Go in to Nvidia Control Panel->Manage 3d Settings->Global Settings->Power Management Mode->set to Prefer Maximum Performance
2) Use something like MSI Afterburner to down-clock your cards. Using MSI 420, set the Core Clock to -135 to test if it helps resolve the problem. Remember to click Apply to set the clock speed to your card.
OK - thanks for trying. Otoy are talking to Nvidia about the problem, so hopefully it will be addressed in a future Nvidia driver release. For the moment, use Nvidia driver 358.50.I did Step #1 as described, then I did the equivalent under-clocking of Step #2 using Asus GPUTweak2.
Unfortunately it did not change anything. When running Octane through the plugin the CUDA driver still throws "#999 unknown internal error".
If you want me to run a debug build in a proper debugger session let me know, although the combination of Poser's execution context and
and an internal error from a driver won't make it too easy to catch good info.
Users browsing this forum: Baidu [Spider] and 1 guest