Several users are reporting stability issues @OTOY Support about latest Studio Nvidia driver 555.85 version and c4doctane.
Performing a clean installation of previous Studio Nvidia driver 552.22 solves the problems.
ciao,
Beppe
Stability issues with Studio Nvidia driver 555.85
Moderators: ChrisHekman, aoktar
As a general "best practices" question, does Otoy recommend updating drivers regularly? I tend to follow the "if it ain't broke don't fix it" philosophy, and as such, we are still running V 536.99 from last August. Is there a compelling reason to update drivers without specific problems or prompting from the Octane release notes?
Animation Technical Director - Washington DC
Yes, OctaneRender doesn't need to update the Nvidia Studio driver frequently, but a lot of users have other softwares that need it, like Unreal, for example.
ciao,
Beppe
ciao,
Beppe
I thought I could fix the following issues with a driver rollback and though it got better, the errors still occur:
- Alembic Files jump for one frame, not matching the rest of the simulation.
- Octane Tag with light linking gets ignored for one frame causing flickering.
I never had these problems, did anyone else experience something like that and could it be a driver issue?
Viewport AND LV is totally fine...
- Alembic Files jump for one frame, not matching the rest of the simulation.
- Octane Tag with light linking gets ignored for one frame causing flickering.
I never had these problems, did anyone else experience something like that and could it be a driver issue?
Viewport AND LV is totally fine...
6850k // 32 GB // 1080, 1080 Ti, 2080 Ti // Win 10 // C4D 19.068
Hi,
this discussion is about Live View stability with Studio Nvidia driver 555.85, for any other issue, please open a different discussion with example, screenshots and logs, so we can check, thanks.
ciao,
Beppe
this discussion is about Live View stability with Studio Nvidia driver 555.85, for any other issue, please open a different discussion with example, screenshots and logs, so we can check, thanks.
ciao,
Beppe
I can confirm this 100%.
The late May Nvidia drivers totally destroyed my ability to render nearly anything.
And the more recent Nvidia drivers released around June 3/4 did nothing but make things worse.
Thanks so much for the information on how to get rendering again!
The late May Nvidia drivers totally destroyed my ability to render nearly anything.
And the more recent Nvidia drivers released around June 3/4 did nothing but make things worse.
Thanks so much for the information on how to get rendering again!
- jessestormer
- Posts: 55
- Joined: Mon Nov 23, 2015 2:32 pm
- Contact:
I've been really having to troubleshoot the heck out of getting my computers to render, I have had no idea what is going on...
The would render with the normal Maxon One license in the software, then not render via command line ; just pause with no crash or hints in the log or anything.
I finally decided I was going to do a clean driver install... use the nvidia cleaner and/or ddu
Without even re-installing a driver myself, they're all now working fine with the 'default installed driver' that windows chose. (31.0.15.3623)
I just... don't even know... I can't afford to try installing the newer drivers and have them fail on and cause more days/weeks of troubleshooting
The would render with the normal Maxon One license in the software, then not render via command line ; just pause with no crash or hints in the log or anything.
I finally decided I was going to do a clean driver install... use the nvidia cleaner and/or ddu
Without even re-installing a driver myself, they're all now working fine with the 'default installed driver' that windows chose. (31.0.15.3623)
I just... don't even know... I can't afford to try installing the newer drivers and have them fail on and cause more days/weeks of troubleshooting
Unfortunately, Nvidia Studio 560.70 version doesn't solve the stability issue, please stay with 552.22!
ciao,
Beppe
ciao,
Beppe