The same for me. Had a lot of rendering work recently and noticed the same multiple times. Not sure that is about shortcuts. Looks more like bug.rayrayato wrote:I am also getting a random switch from pathtracing to infochannel kernel. Not sure what key i'm pressing but it's happening a lot on this project. Is there a keyboards shortcut table posted anywhere I can look at?
Version 3.08-RC4
Moderators: ChrisHekman, aoktar
RTX 4090 | Ryzen 9 7950X3D | 64GB | Win 11 23H2
- philcoffman
- Posts: 9
- Joined: Wed Nov 09, 2016 7:29 pm
Any update on when the C4D plug-in will support the Titan V? I keep hearing that it's coming. Did I miss anything?
Pls you should provide some good information about this! What's the exact steps to reproduce it again?Aleksei wrote:The same for me. Had a lot of rendering work recently and noticed the same multiple times. Not sure that is about shortcuts. Looks more like bug.rayrayato wrote:I am also getting a random switch from pathtracing to infochannel kernel. Not sure what key i'm pressing but it's happening a lot on this project. Is there a keyboards shortcut table posted anywhere I can look at?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Regarding Octane switching to info-channels. I see now that I'm not the only one w/this bug. 3 other users have reported.aoktar wrote:Pls you should provide some good information about this! What's the exact steps to reproduce it again?Aleksei wrote:The same for me. Had a lot of rendering work recently and noticed the same multiple times. Not sure that is about shortcuts. Looks more like bug.rayrayato wrote:I am also getting a random switch from pathtracing to infochannel kernel. Not sure what key i'm pressing but it's happening a lot on this project. Is there a keyboards shortcut table posted anywhere I can look at?
The only pattern I could see is it often happens after changing attributes with the material node system.
I'm aware of it's a problem which has been reported by a few users. Problem is that to don't know what causes it and why it happens sometimes.Iceman9 wrote: Regarding Octane switching to info-channels. I see now that I'm not the only one w/this bug. 3 other users have reported.
The only pattern I could see is it often happens after changing attributes with the material node system.
Changing from node editor? Node editor or settings window is open while doing it?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I was trying to discern the trigger point. I'm not sure. Perhaps the act of closing the node editor window. It wouldn't always happen. Maybe it's the presence of certain nodes? Or the selection/state of certain nodes within that window.aoktar wrote:I'm aware of it's a problem which has been reported by a few users. Problem is that to don't know what causes it and why it happens sometimes.Iceman9 wrote: Regarding Octane switching to info-channels. I see now that I'm not the only one w/this bug. 3 other users have reported.
The only pattern I could see is it often happens after changing attributes with the material node system.
Changing from node editor? Node editor or settings window is open while doing it?
My only suspect is about newly added solo mode. It may be due functions which handle that.Iceman9 wrote: I was trying to discern the trigger point. I'm not sure. Perhaps the act of closing the node editor window. It wouldn't always happen. Maybe it's the presence of certain nodes? Or the selection/state of certain nodes within that window.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
If that is newer code...that might make sense. This bug never happened to me until the final release of 3.08. (Maybe it existed before then but I never saw it.)aoktar wrote:My only suspect is about newly added solo mode. It may be due functions which handle that.Iceman9 wrote: I was trying to discern the trigger point. I'm not sure. Perhaps the act of closing the node editor window. It wouldn't always happen. Maybe it's the presence of certain nodes? Or the selection/state of certain nodes within that window.
I haven't used the solo mode yet but maybe something there.
Hi Ahmet,
I think you might be onto something suspecting the solo node as the culprit.
I have seen this once while working, and it happened on launch.
I haven't been able to trick it into info channels, but I can consistently get it stuck in solo node mode.
Here is a screen recording of it happening.
Hope this helps.
I think you might be onto something suspecting the solo node as the culprit.
I have seen this once while working, and it happened on launch.
I haven't been able to trick it into info channels, but I can consistently get it stuck in solo node mode.
Here is a screen recording of it happening.
Hope this helps.
OSX 10.12.4 | Intel 12 core @ 3.33 ghz | 128 gb ram | NVIDIA GeForce GTX 1080TI | Ubuntu Linux slave with 3x 1080ti
Is it what you said before?niestudio wrote:Hi Ahmet,
I think you might be onto something suspecting the solo node as the culprit.
I have seen this once while working, and it happened on launch.
I haven't been able to trick it into info channels, but I can consistently get it stuck in solo node mode.
Here is a screen recording of it happening.
Hope this helps.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw