Viewport freeze with liveview on Tweet

[garytyler]

This has happened to me a few times and I haven't found a setting that handles it. While navigating in the viewport with Live view on, my viewport will stop responding to my navigation input but the viewport responds on cue. Anyone have an idea how to prevent this? Retiling the viewport panes seems to reset the viewport and gets everything working again but sometimes it happens numerous times in the same 5 minutes or so. Anyone else experience this?

[aoktar]

please write your specs. Do you activated render priority=On and "low" or "medium"? What's your gpu(s), os, versions?

[muchogrande]

Same issue here. Appears more on scenes with larger/more bitmap textures. If I shut down c4d and open it again everything works fine again.

Mac Pro 5,1 Yosemite 10.10
2x GTX980
Octane C4D plugin v2.16.2

I have tried priority Med and Low Priority on the card that is driving my monitor, it appears to make no difference.

[aoktar]

Same issue here. Appears more on scenes with larger/more bitmap textures. If I shut down c4d and open it again everything works fine again.

Mac Pro 5,1 Yosemite 10.10
2x GTX980
Octane C4D plugin v2.16.2

I have tried priority Med and Low Priority on the card that is driving my monitor, it appears to make no difference.

I'm sure something is wrong on your settings. Please show your gpu settings.
Second idea: It may occurs if you have much complex objects with object tag and "geometry checking" is active. If any very high amount polygons will be resended this will take much time.

[muchogrande]

Thanks for responding so fast! These settings?

gpu settings

Yes, it is doing it on a scene with a fair bit of geo, but I am not using the Octane geo tag.

Also, if I have 4 viewports open in C4D they lock up independently (for example, my side view might still work while other views are frozen. Although eventually they all freeze, and so does the Octane preview window). When I try an manipulate an object or camera in one of the frozen panels the Octane Log posts this message repeatedly:

Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (105)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (105)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (105)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (105)
Tried to access null node pin

[aoktar]

really hard to figure your problem without seeing it live. Also this messages is not very important for this issue. What happens when you check the "use priority" on both? If it does not any difference please show me your nvidia settings.

[muchogrande]

Ok tried putting low priority on both gpus, same issue. Perspective usually locks up first. I suppose its obvious, but if I turn off 'use OPENGL' in C4D settings things work fine.

On OSX there's not much to see in the official nvidia System Prefs panel...? I haven't (don't know how) to change any settings on the cards.

I just noticed that if I go to help>show gpu info in the Live Viewer, nothing happens.

[davidtorpey]

Hello

I have been having the same issue on two very different OSX machines with Octane on them in Cinema 4d R15 and R16.

Has there been a solution created yet?

Cheers

David

[aoktar]

Hello

I have been having the same issue on two very different OSX machines with Octane on them in Cinema 4d R15 and R16.

Has there been a solution created yet?

Cheers

David

i don't think it's a octane problem. It works very well on windows pcs. Maybe some issue with drivers against c4d and octane. But hard to understand the issue without checking directly.

Can someone capture a video to show the issue?

[FormaDisseny]

Hi everyone

I'm Jules FAIVRE from Forma Disseny http://www.formadisseny.com

We've been working with Octane in C4D since V2 on many machines at the Studio running with Windows 7, Windows 8, Windows 8.1, Windows 10 and Apple's OS

Since Octane V.3 xx it could be with ANY HARDWARE , ANY DRIVERS and ANY V3 VERSIONS OF OCTANE

* * * CINEMA 4D STILL CONSTANTLY FREEZING WHEN OCTANE IS RENDERING WITH MORE THAN 1 or 2 GPU'S * * *
It could be the Liveviewer or the Picture viewer, every 15 seconds when you have many transparency or severals heavy elementa in the scene it will depend the project, Cinema4D and even the entire system will freeze 5 to 20 seconds. And it happens with any specs : GTX970, 980, 980ti, TITAN X, 1080.
There is a serious issue here since at least 2 years.

In a 3D Production like ours this issue slow us down enough to miss the project on time. And because the issue still in the new versions, now the Boss of the Studio asked me that I must looking for another engine.
PLEASE THIS MUST BE FIXED we have all of the machines running Octane, and all are well sets. The last thing I need is to switch all machines to another engine.
But making shaders with the liveviewer active on our projects just become a nightmare.

DETAILS OF THE ISSUIE :

- Happen since all version 3. Octane C4D v3.08 T6.1 still happen
- It will depends of the hardware : Sometimes 2 gpus could work fine, like if you have if you have 4 GTX1080 active it freeze. If you disable 2 of them, it works.
If you have 3 GTX980 active it freeze. if you disable 1 it still freeze, 2 of them disable and it works etc..
- Happen on any Software/Versions between Mac and Windows, with any grafic driver. More than 10 Machines tested.
- Disable OpenGL in cinema preference don´t solve anything. The only way is to Disable gpus.
- It start happening when you add Speculars Materials, even on a small scene. More close you get of the element more it freeze.
- Happen with heavy scene even if you hide everything. That means if you still have many shaders, Geometries, Particles sets present in the project but hidden to modified
the shader using liveviewer just for a small element. You will experience those freeze constanly.
- When sending the scene to the render queue, Octane make windows freezing every 15/30 seconds during 10 to 20 seconds each time. witch slow down the render time
massively. We tried on some project to disable 2 1080 of 4 and had better result at render time... And finaly choose this way Making possible to deliver on time.

EXAMPLES :

Here you have some project where those freeze slow us down seriously :
http://formacg.es/en/portfolio/bmwprotocol/
http://formacg.es/en/portfolio/thecgbros/
http://formacg.es/en/portfolio/demoreel/

I am available to share any sample/scenes you'll need if it can help to fix this issue.

Best Regards