c4d background object behavior differs between viewport render and live viewer.
Version 3.08.1-R4 (obsolete stable)
Moderators: ChrisHekman, aoktar
- Attachments
-
- G3-398-infiniteWhiteRoom.c4d.zip
- (100.9 KiB) Downloaded 258 times
3.08 seems generally solid for me so far.
But one bug that keeps repeating: If I use the node editor, my render kernel gets getting changed to info-channels. This has happened about a dozen times in the past few days.
It didn't happen before final release of 3.08.
But one bug that keeps repeating: If I use the node editor, my render kernel gets getting changed to info-channels. This has happened about a dozen times in the past few days.
It didn't happen before final release of 3.08.
Version and OS?Iceman9 wrote:3.08 seems generally solid for me so far.
But one bug that keeps repeating: If I use the node editor, my render kernel gets getting changed to info-channels. This has happened about a dozen times in the past few days.
It didn't happen before final release of 3.08.
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
Please post a few bugreport.zip!GlynD01 wrote: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.
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
Yes, It's not implemented yet.MWAtech wrote:c4d background object behavior differs between viewport render and live viewer.
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'm away but please show it by some video and where's the parameters you mentioned. I'll try to think what about.GIOLETS wrote: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.
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
Have you tried updating to the latest stable version? You have a release candidate from a couple versions back.DinoMuhic wrote: 3.08 RC3
OSX 10.12.4 | Intel 12 core @ 3.33 ghz | 128 gb ram | NVIDIA GeForce GTX 1080TI | Ubuntu Linux slave with 3x 1080ti
Re issue where my kernel render gets switched to InfoChannels:aoktar wrote:Version and OS?Iceman9 wrote:3.08 seems generally solid for me so far.
But one bug that keeps repeating: If I use the node editor, my render kernel gets getting changed to info-channels. This has happened about a dozen times in the past few days.
It didn't happen before final release of 3.08.
System:
-3.08 final for standalone and plugin
-C4d R19.053
-Windows X.0.16299
-Nvidia 397.31 (I just updated but it was doing this last night also. I doubt it's GPU issue)
It seems to happen after using the node editor--though not every time. It's happened maybe 10-12 times.
Hi Aoktar,
here I've recorded a brief video that shows the problem, ass I said I've found the same on 2 different machine.
I don't say that is a bug, but ask where to investigate in order to know the relationship between my texture path and the camera imager while rendering in Live Viewer.
My texture disk (E:/) it's an SSD with almost 500GB of data, but never had this problem before (3.06 and 3.08 test 6)
here I've recorded a brief video that shows the problem, ass I said I've found the same on 2 different machine.
I don't say that is a bug, but ask where to investigate in order to know the relationship between my texture path and the camera imager while rendering in Live Viewer.
My texture disk (E:/) it's an SSD with almost 500GB of data, but never had this problem before (3.06 and 3.08 test 6)
i9-10900x, 96GB DDR4, 2xRTX 2080 TI, ASUS X299 SAGE, Windows 10
http://www.visual4d.it
http://www.visual4d.it