momade wrote:Sory. Me again:
Mixing GTX and RTX does not lead to issues right?
Just lost another GPU..
TonyBoy wrote:Ahmet, any possibility that the latest build is compatible with C4D 15?
forward wrote:I can confirm that the problems that sbstnc is having with an unresponsive LV are happening for us as well.
We also have a dual card setup and even switching off one card in the settings does not help with the interface freeze happening inside C4D.
sbstnc wrote:Behaviour is the same as 4.01 versions, C4D interface can't be used when LV is on.
Mac OSX 10.12.6, CUDA 387.178, GPU 378.05.05.25f01
2 x 1080Ti, C4D R20
Any scene with a decent amount of geo and textures, say 4-gb VRAM.
It's like C4D stops while LV updates. As soon as LV refreshes with new samples, C4D becomes responsive for a split second, before stopping again while LV thinks some more.
What's going on please. This has only happened since 4 on a machine where nothing else has changed for 18 months. Updating 10.12.6 from 10.12.4 and new drivers has not worked. I have work to get out and I can't press a damn button.
LV on prevents any sort of viewport navigation. Can't pan, can't move around, because C4D is only responsive for 0.01 seconds every 3 seconds. Pause the LV (if you can manage to press the pause button in that 0.1second) then magically the viewport becomes super fluid and response, can pan all over, tons of geo, no problems. LV back on... can't click anything, C4D too slow, LV just keeps trying to refresh refresh, it's like LV is sucking up all system resources, but looking at stats, on an 8core C4D is 100% of 1 core and memory is fine.
I'm pretty frustrated now.
Edit: looks like some max users posting the same thing, RC7 OK but 4 onward no good.
Is it core that's the problem? If so why?
Users browsing this forum: BCres and 6 guests