Page 5 of 21
Re: Version 3.08(latest stable)
Posted: Wed Apr 25, 2018 9:01 pm
by MWAtech
c4d background object behavior differs between viewport render and live viewer.
Re: Version 3.08(latest stable)
Posted: Wed Apr 25, 2018 10:05 pm
by Iceman9
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.
Re: Version 3.08(latest stable)
Posted: Wed Apr 25, 2018 10:17 pm
by aoktar
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.
Version and OS?
Re: Version 3.08(latest stable)
Posted: Wed Apr 25, 2018 10:20 pm
by aoktar
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.
Please post a few bugreport.zip!
Re: Version 3.08(latest stable)
Posted: Wed Apr 25, 2018 10:28 pm
by aoktar
MWAtech wrote:c4d background object behavior differs between viewport render and live viewer.
Screen Shot 2018-04-25 at 1.56.07 PM.jpg
Screen Shot 2018-04-25 at 1.56.40 PM.jpg
Yes, It's not implemented yet.
Re: Version 3.08(latest stable)
Posted: Wed Apr 25, 2018 10:39 pm
by aoktar
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.
I'm away but please show it by some video and where's the parameters you mentioned. I'll try to think what about.
Re: Version 3.08(latest stable)
Posted: Thu Apr 26, 2018 12:15 am
by DinoMuhic
yeah I also noticed the render kernel switching to info passes on its own randomly.
3.08 RC3
Win10 64
C4d R19
Re: Version 3.08(latest stable)
Posted: Thu Apr 26, 2018 12:30 am
by niestudio
DinoMuhic wrote:
3.08 RC3
Have you tried updating to the latest stable version? You have a release candidate from a couple versions back.
Re: Version 3.08(latest stable)
Posted: Thu Apr 26, 2018 1:28 am
by Iceman9
aoktar wrote: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.
Version and OS?
Re issue where my kernel render gets switched to InfoChannels:
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.
Re: Version 3.08(latest stable)
Posted: Thu Apr 26, 2018 8:22 am
by GIOLETS
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)