OTOY Forums

Here I've report my troubles with the 3.08 stable and the very slow viewport issue that I've start to describe some post above.
With a very simple scene (a cube) the viewport is very fast (I use a specific card a GTX 670 dedicated to display not to the render), when I start the render on Live Viewer the viewport become very slow also if I've double checked with MSI Afterburner that my GTX670 in not loaded by the render process.
And occurs only when I use Live Viewer, and enable the Camera Imager, not in Picture Viewer.
I've tried switching back to 3.08 test 6, so with the same C4d and the same hardware configuration, and all the things come back to normality, and the viewport is fast as I expect to see also during the rendering.

My thoughts is that could be some new parameters between 3.08 test 6 and 308 stable version that produce the issue.

Can you suggest me where to investigate?



EDIT :
something is changed with the management of the texture archive? I've found that if I set in Preferences the texture archive disk and enable the Camera Imager (on camera tag) the problem start, disabling or the texture path or Camera Imager the viewport run normally.

Hi Aoktar

Thanks for updates.
Will you be adding offline mode?

Hi, Aoktar

render region not cropp Post pass (in PV)?

TMBPC wrote:Hi Aoktar

Thanks for updates.
Will you be adding offline mode?

Yes, but it's not up to me. It will be available when Otoy brings it back.

bahgoogen wrote: ...
It seems to be any parameter that is keyframable.
...
This is only while the viewport renderer is active. If i switch it off, everything goes back to normal behavior. Live Viewer is fine also, just the new viewport renderer.
Autokeying seems to work also, just when you try and manually set a keyframe while the viewport renderer is running.

Exactly the behavior I'm seeing as well, R19.053 on OS X 10.12.6

Thank you for the latest 3.08 release, it's _much_ more stable and performs better than 3.07 with network rendering on our machines.

This version works well for me.

One small thing I noticed...

The Live Viewer window says 3.07-R2 in the window bar at the top. But I am definitely on 3.08. I even have the option for the viewport rendering (which works well for me.) Guess it's really a cosmetic fix.

BCres wrote:This version works well for me.

One small thing I noticed...

The Live Viewer window says 3.07-R2 in the window bar at the top. But I am definitely on 3.08. I even have the option for the viewport rendering (which works well for me.) Guess it's really a cosmetic fix.

Live viewer.JPG

If your window is part of a saved layout you have to close it and open a new Live Viewer window.

I've been reading customer issues with Nvidia drivers causing crashes with Octane and versions which work. Well ive had no such luck with the last 5 drivers they have issued and im currently on 391.35 which I understand is the newest release and Octane 3.08 (stable) crashed a couple of times yesterday and each driver Ive installed as a fresh install after cleaning out the previous driver with DDU. If everyone is blaming drivers just why are Nvidia finding this too difficult to sort out as I know Maxon have released a patch which Im also going to try out of desperation? Im just beginning to think the problem could be much deeper and Windows 10 more at issue here even though I've also disabled the automatic driver updates as that was also prone to generate its own set of issues. Just nothing I`ve tried works to such a point I`ve become institutionalised and started accepting regular crashing as normal. All very frustrating of course but not with Octane as its not where the issue lies.

niestudio wrote:

BCres wrote:This version works well for me.

One small thing I noticed...

The Live Viewer window says 3.07-R2 in the window bar at the top. But I am definitely on 3.08. I even have the option for the viewport rendering (which works well for me.) Guess it's really a cosmetic fix.

Live viewer.JPG

If your window is part of a saved layout you have to close it and open a new Live Viewer window.

Thanks, niestudio. That was the problem. I learn something new every day.

Hi Aoktar did you found the time to check my question about the "slow viewport" issue (yust 8 post above) ?
I've checked on two machine and found the same problem.

Do you need more info (video, make another test, etc)?

Thanks a lot.