Lacking performance when working with hi-res textures.
Posted: Mon Dec 19, 2016 8:29 pm
Hello there... I want to start this topic by saying that this isn't the first time I've had performance issues with the Cinema4D plugin.
I remember making a thread about asking for help because my viewport was lagging when Octane was making the previews of the materials, thankfully Aoktar pointed me to the right direction and by disabling OpenGL preview and Materials Previews in the Live Viewer I was able to overcome some of these issues.
Now I've started to notice something, since I got a subscription from Poliigon I'm able to get my hands on some pretty high resolution textures and whenever I tried using them in Octane the interface would lag to the point of being unusable. I always thought the reason I was getting poor performance was because I only have one card (gtx980) but now I've come to realize that it is the plugin itself.
Why? Well, I've been learning the standalone version of the render and I must say the performance I got the first time I used it was incredible, sure it took the same amount of time for the textures to load into memory for the first time and that's obvious but after that the program ran absolutely beautiful, that means zero lag when clicking nodes and I was even able to edit the values and check the preview in real time.
Then I thought "well, maybe it's a general plugin issue" so I downloaded the demo plugin for Modo (since I use it for modelling) and even though the interface didn't compare to Cinema's (seriously!) and it took me some time to realize where everything was after I set the same scene with the same textures and the same loading time once again the program was still running perfectly and that means zero lag...
I made a video of myself using Cinema's plugin vs using the standalone, for some reason I didn't record the audio and that's important because in the video when you see the mouse standing still or moving around doing nothing, that's actually me clicking to see if something finally happens.
PD: I also want to note that for this test I was using extremely hi-res textures (22k) but they still were within the memory that the 980 have and both the stand alone and the Modo plugin ran just fine.
Note to future readers: Converting my original jpeg image files to tiff files seem to have solve this issue with performance. Also, don't forget to disable both materials and opengl previews in the liveviewer if you want to gain additional performance in heavy scenes.
I remember making a thread about asking for help because my viewport was lagging when Octane was making the previews of the materials, thankfully Aoktar pointed me to the right direction and by disabling OpenGL preview and Materials Previews in the Live Viewer I was able to overcome some of these issues.
Now I've started to notice something, since I got a subscription from Poliigon I'm able to get my hands on some pretty high resolution textures and whenever I tried using them in Octane the interface would lag to the point of being unusable. I always thought the reason I was getting poor performance was because I only have one card (gtx980) but now I've come to realize that it is the plugin itself.
Why? Well, I've been learning the standalone version of the render and I must say the performance I got the first time I used it was incredible, sure it took the same amount of time for the textures to load into memory for the first time and that's obvious but after that the program ran absolutely beautiful, that means zero lag when clicking nodes and I was even able to edit the values and check the preview in real time.
Then I thought "well, maybe it's a general plugin issue" so I downloaded the demo plugin for Modo (since I use it for modelling) and even though the interface didn't compare to Cinema's (seriously!) and it took me some time to realize where everything was after I set the same scene with the same textures and the same loading time once again the program was still running perfectly and that means zero lag...
I made a video of myself using Cinema's plugin vs using the standalone, for some reason I didn't record the audio and that's important because in the video when you see the mouse standing still or moving around doing nothing, that's actually me clicking to see if something finally happens.
PD: I also want to note that for this test I was using extremely hi-res textures (22k) but they still were within the memory that the 980 have and both the stand alone and the Modo plugin ran just fine.
Note to future readers: Converting my original jpeg image files to tiff files seem to have solve this issue with performance. Also, don't forget to disable both materials and opengl previews in the liveviewer if you want to gain additional performance in heavy scenes.