Page 1 of 2

Lacking performance when working with hi-res textures.

Posted: Mon Dec 19, 2016 8:29 pm
by Terryvfx
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.

Re: Horrible performance when working with hi-res textures.

Posted: Mon Dec 19, 2016 9:35 pm
by aoktar
Sorry to long post to read fully. What's expectation? Have you disabled opengl+material previews in this video?

Re: Horrible performance when working with hi-res textures.

Posted: Mon Dec 19, 2016 11:38 pm
by Terryvfx
Yeah in my video I disabled both previews but the lag is still unmanageable :cry:

Re: Horrible performance when working with hi-res textures.

Posted: Tue Dec 20, 2016 12:37 am
by aoktar
Terryvfx wrote:Yeah in my video I disabled both previews but the lag is still unmanageable :cry:
what's your image format? I just tried 8k jpegs or 15k tiffs to be sure again. It seems working very well on me. Also I didn't see this kind of feedbacks from others. Of course with disabling previews.

Re: Horrible performance when working with hi-res textures.

Posted: Tue Dec 20, 2016 4:16 am
by Terryvfx
I'm using jpgs If you could see the video, you would see I'm using .jpgs and that I disable previews.

Please take the time to read everything, this problem doesn't happen with Modo or with the stand-alone.

Re: Horrible performance when working with hi-res textures.

Posted: Tue Dec 20, 2016 4:24 pm
by aoktar
Can you post these jpgs? Note that there is still previews in imagetextures and material of node editor. Standalone does not create previews while working and you're with single GPU. I'm working on TWO. This can be a reason.
I recorded a video to show that: https://vimeo.com/196456214

Re: Horrible performance when working with hi-res textures.

Posted: Tue Dec 20, 2016 5:38 pm
by preciousillusion
aoktar wrote:Also I didn't see this kind of feedbacks from others
That's not true, it was in one of my posts 3 months ago. And you definitely read that one.

Re: Horrible performance when working with hi-res textures.

Posted: Wed Dec 21, 2016 4:34 am
by Terryvfx
This is the texture set that I used for my video: https://drive.google.com/file/d/0B-YugS ... sp=sharing

In the live viewer I disabled OpenGL and Material Previews then in futher test I even disabled node previews. I also restarted the system to make sure only C4D was running, I updated my graphic card drivers, I disabled everything that I thought could be making some sort of impact in my performance but It's the same problem, once I start to connect hires textures the plugin's performance drops down.

I only have one card BUT I need to reiterate that in Modo I don't have this problem neither in the Standalone.

I've a friend that has system with a single 980ti and he also have this problem.

With all due respect for your coding skills maybe there is a recurrent process that's being done unnecessarily, a process that's slowing down the interactivity of the UI even after the textures are loaded into memory.

Re: Horrible performance when working with hi-res textures.

Posted: Wed Dec 21, 2016 9:59 am
by miohn
Hi,

during last weeks I also had massive lags when working on projects with highres textures.
Didn't post, because I could not send a scenefile or descripe the problem in detail.

The system/C4D hangs for seconds without any response after every click.
No fun when working on a urgend project.
After skaling down all textures in PSD I could continue to work.
I have two older Titans.

I can not say, that this is happening every time when using highres textures.

So Terryvfx is not the only one.

A nice addon to the texture manager would be a "resize image" option btw. ;)

regards
Mike

Re: Horrible performance when working with hi-res textures.

Posted: Wed Dec 21, 2016 11:53 am
by Terryvfx
Speaking about improvements if the image node can have the name of the imported texture in its title that will be really helpful, similarly to the way the Standalone works.