3.08 still has problems with camera imager

[miohn]

Hi Ahmet,

I hoped, since all devs are concentrated on Version 4, that latest Version 3.08 is working correct now!
But sadly, the camera imager (from camera tag), when enabled, causes the main C4D viewport to extremly slow down.
As soon as I deactivate "camera imager" viewport reacts fine again.

I have a fresh new PC-Setup (8700K running 5Ghz, 980 Ti Hybrid + 1 x 1080 Ti Hybrid, latest nvidia 3.9793 , 64 Gig Ram)
Had similar problems with "camera imager" with earlier 3.08 Test-Versions on all my other mashines and thought, that this
problem is fixed long ago in latest "stable" 3.08. But .....

Could this be solved please?

3.07 runs without any problems - so its a problem with 3.08 Version

regards
Mike

regards
Mike

[GIOLETS]

I also think that should be resolved soon, but in the meantime if you want you could fix with this tip:
viewtopic.php?f=85&t=66885&p=337439#p337439

[aoktar]

I'm using the plugin every minutes on everydays. I don't see any problems like you said.
Do you have a custom lut in imager? And have a lot of texture paths in search paths? Anyway i've tried with CUSTOM LUT and didn't see any problem in codes. It's working very well.

[miohn]

Hi Giolets,

indeed!
When I load any Lut-File and set the strength to "0" everything runs smooth again!
Never worked with Luts before and I missed this Post - so thanks very much!

Funny, that this workaround comes from a User and not from the Devs.
Please Devs! When will this "Bug" be fixed????

Thanks
Mike

[aoktar]

Hi Giolets,

indeed!
When I load any Lut-File and set the strength to "0" everything runs smooth again!
Never worked with Luts before and I missed this Post - so thanks very much!

Funny, that this workaround comes from a User and not from the Devs.
Please Devs! When will this "Bug" be fixed????

Thanks
Mike

Funny really
Do you mean me as devs?

[miohn]

Funny, funny, that I suddenly get an answer now.

Please don't get wrong Ahmet!
I love the Octane-Plugin and I'm working with it since many years!
But sometimes, I have the feeling, that posts concerning problems/bugs/strange behaviors whatever
with different Versions of the plugin are ignored or not thoroughly investigated.

I wished, that this tip to bypass the problem with the camera imager (and it seams, that I'm not tho only one, having
this behavior) was coming from you!
Or at least a short statement that you have taken note of the problem and take care of it

Implied, that you are the Dev.

regards
Mike

[aoktar]

I wish that people give enough information to track the problems. I couldn't understand that your issue and where to look, without answer of "Giolets". I believe that hard to understand for your guys how I could estimate the problems and handle the work-loads of developers.

[miohn]

Hi Ahmet,

sure I understand, but why should I write a novel?

I said, that I have massive slowdown with stable 3.08 in the C4D-Viewport as soon I have "camera imager" activated.
I said, that this problem dissapears, when I deactivate "camera imager"
So for me it sorted out, that there is a problem with the "camera imager".

Please let met know "whatelse" should I say ??????
I'm not a Dev - I'm just a Freelancer who needs to get the jobs done.
Sorry, but at all readiness, what should I tell more????
If you tell me, what you need to know - and if I'm able to give you the info you need - I will do!

I did not know about the tip from Giolet before.
And 2 days I did not get any response from you.
But as soon as I add a little criticism, I get a response.
But sadly not concerning my problem with the "camera imager"

I reported months ago about nearly the same problem with an 3.08 test version.
(I know that a test-built could have problems.)
But that post got sanded as well.

Sorry Ahmet, but please also understand Users!

And now please lets go back to the problem "camera imager"
Will you have a look at this? What could I tell you more?

regards
Mike

[aoktar]

Shortly, I'll check that!
But cannot know where to look if you just say it's about CameraImager. So Guilets's notification made a big different to know what could be. So give me enough idea where to look and how to reproduce. And it will be fixed if it's reproductable on me.

[miohn]

as said, I did not know about the trick with that "Lut-File" so I could not report about this.
But anyway - nice to hear that you will check!

Again info about my system: I have a fresh Win 10 Installation (1803), Octane 3.08 latest stable, R19, 980Ti + 1080Ti, latest NVidia Drivers, 64 Gig Ram, 8700K

Thank you!

regards
Mike