After extensive troubleshooting, trial and error, I finally arrived at what was causing my problem. But first, allow me to detail the complexity of my troubleshooting steps.
Step one was to visit NVIDIAs website, as opposed to allowing GeForce Experience to automatically pick the driver. This way, I would know, that I had entered all of the explicit details pertaining to my setup. Using the precise settings, I download both the Game, as well as the Studio versions of the driver.
Started with a reinstall of the Game driver. No go.
Next, the Studio driver. No go.
Seeing then, that changing the driver had no impact on the issue, I proceeded to call on my years of troubleshooting techniques ironing out other problems, and decided to iron it out, piece by piece, starting with the System files.
SFC, as well as DISM showed everything being perfect.
Next, I opted for a clean boot. Set the clean boot up, restarted, computer comes back up, I try C4D UV Edit, …it worked perfect again. Uh huh, this is my first lead in some time. So we have a Service of some type doing the damage. So I check boxed to hide all Microsoft, and there were only like, six unique entries listed, so it wouldn’t take me very long to go through the list, adding checkmarks and rebooting until finally C4D would cease to work again.
I did just that, and the problem entry ended up being the very last entry that I check marked, which was, “NVIDIA Display Container LS”. That’s the entry that did it.
Ultimately, at this point, the problem still comes back to the video driver, in one way or another, …or does it.
I reset my boot options back to normal, rebooted, now back in Win 10, I went under Services, and Disabled, “NVIDIA Display Container LS”, and C4D worked perfectly, once again.
But then I’m saying to myself, alright, everything is back to normal again, but, somewhere, somehow that can’t be good to have that aspect of the driver disabled. Typical scenario with a little devil on one shoulder, and an angel on the other.
Went back in, and set “NVIDIA Display Container LS” back to its normal settings again, and figured, well, anytime I do UV work, I can just go in and disable it again. But that isn’t correct, that’s too much work, that shouldn’t need to be done anyway.
My whole system is back to where I started, fully frustrated and about to just close shop with a defeated feeling, I said to myself, just for kicks and giggles, let me try one other thing that probably won’t make a difference at all, but at this point, anything is worth a try.
I run a 55” 4K UHD Samsung @ 4K resolution, (3840x2160) @ 120hz refresh rate. I dropped the refresh rate down to 30hz. Fired up C4D, and UV Edit worked. Bam! That was it.
Next I started climbing the refresh rate up from 30hz, step by step to see where C4D would stop functioning again. 60hz is the highest that C4D will function. Anything above 60hz, and my problem comes back. Interestingly enough, all of C4D works perfect at 120hz, except for “BP – UV Edit”.
Now I can’t run my monitor at 120hz, but, C4D works once again with all of the NVIDIA driver installed.
Ultimately, this may, or may not be something of interest to Maxon, because I did iron it out deep enough to find that, it was indeed the NVIDIA service entitled, “NVIDIA Display Container LS” that was keeping, “BP – UV Edit” from functioning properly, with any screen refresh higher than 60hz. At least on my end, with the above listed hardware.
Cerbera, thank you for your input. As with everything dealing with digital artistry, there are far more than one way to achieve the same goal. Your method was quite spot on, and worked very well. I then tried a little experimentation, and found that if I simply assigned the two points of the, "measure & construction" tool to the exact width dimension I needed, and then resized/placed the reference image to fall exactly behind the "measure & construction" tool line, that worked really well as well.
