Jump to content


Nvidia drivers and R20 viewport issues

Recommended Posts

Anybody else having viewport issues with Nvidia driver (390 series) and R20?


Basically my viewport lags like crazy on R20 with the 390 series drivers. I had to downgrade to 380 series to get rid of the issue. This sucks because I can't use the latest Redshift version 2.6.


I contacted MAXON tech support but they are kinda opaque saying they are working with Nvidia to resolve the issue. It seems MAXON doesn't have a public issue tracker so I have no idea how many people are facing this issue or if there are any updates. How does MAXON tracks bugs? Is it all over email?


This is the first time I have had a issue with C4D stability and I was always impressed by how stable the software is and now that I am forced to downgrade to R19 I am having a bad taste in my mouth...



Share this post

Link to post
Share on other sites

The issue as introduced with the NVIDIA 39x.xx drivers and - depending on the timing of your machine - the issue can happen in R20, R19, R18, ... .


If you're running into this issue, then besides reverting to a not crashing driver is disabling the threaded viewport redraw to work around this driver (crash) bug:


  • To enable the workaround a command line parameter needs to be set for Cinema: g_threadedRedraw=false
  • It will - as the name implies - disable the threaded redraw in the viewport (which is triggering the NVIDIA driver crash). This parameter can either be set via the Windows command console or - easier - by creating a program shortcut and adding the parameter to the target field.
  • These are the steps to create the program shortcut:
  • 1. Select the CINEMA 4D.exe in the Explorer and press the right mouse button.
  • 2. Create a shortcut for the program.
  • 3. Open the properties of the shortcut.
  • 4. The first editable field of the shortcut contains a line called "Target" which contains the program path and name enclosed in quotation marks. Add one space behind the last quotation mark and add  g_threadedRedraw=false (without any quotation marks) at the end of this line.
  • The resulting "Target" line might (depending on the install path) be something like: "C:\Program Files\MAXON\R17\CINEMA 4D.exe" g_threadedRedraw=false
  • 5. Confirm your changes with "OK".

Regarding how MAXON tracks bugs: It happens (of course) in a database and the crash reporter (that 's popping up in case of a crash) is used to submit them - in case you submitted a valid email address, support or development will use this to get in touch with you.


Best regards,



  • Like 1
  • Namaste 1
  • Awesome 1

Share this post

Link to post
Share on other sites
  • Topic Author
  • Thank you Wilfried!


    That seems to resolve the issue on R20. Wish MAXON US support had told me this over the email.


    Unfortunately I couldn't report this issue via crash reporter because technically the machine wouldn't crash but the viewport would slow down drastically. And it is definitely a timing issue because it happened randomly.


    Share this post

    Link to post
    Share on other sites
    18 hours ago, zenmonkey said:

    How does MAXON tracks bugs? Is it all over email?

    I will just add, because MAXON does things as it does, Cinema 4D is super stable. ;)

    Share this post

    Link to post
    Share on other sites

    Just to let you know I had the same issue with a Quadro P4000. The screen would flash while running C4D and a lag followed. I tried the fix described and it seems to have worked for me as well. By the way, I am running the latest (411) driver.

    Share this post

    Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

    • Recently Browsing   0 members

      No registered users viewing this page.