Page 2 of 5
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Mon Jan 27, 2020 3:06 pm
by mbetke
paride4331 wrote:mbetke wrote:Works really cool so far. Had a "material conversion" day here and not a single crash. Also fast browsing.
But noticed two things:
1. Color Correction: Brightness can't set higher than "1.0"? In old version I was able to place higher values. It is intended?
also
2. On Mix Texture I can't swap materials anymore. Only copy and instance is there.
Hi mbetke,thanks for your report, set to developers.
Regards
Paride
Also the other bug with forest here in this thread? Just want to make sure if you need additional stuff.
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Mon Jan 27, 2020 3:26 pm
by paride4331
mbetke wrote:paride4331 wrote:mbetke wrote:Works really cool so far. Had a "material conversion" day here and not a single crash. Also fast browsing.
But noticed two things:
1. Color Correction: Brightness can't set higher than "1.0"? In old version I was able to place higher values. It is intended?
also
2. On Mix Texture I can't swap materials anymore. Only copy and instance is there.
Hi mbetke,thanks for your report, set to developers.
Regards
Paride
Also the other bug with forest here in this thread? Just want to make sure if you need additional stuff.
Hi mbetke,
I downloaded it and I'm going to test it.
Regards
Paride
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Mon Jan 27, 2020 9:29 pm
by coilbook
Hi Paride,
I asked them many times about this problem where phoenix grid creates an opposite effect with camera motion blur when ti is linked to a moving object.
When will they fix it?
Original post
viewtopic.php?f=81&t=70717
Thanks
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Tue Jan 28, 2020 3:25 pm
by remKa
Okay this version is very unstable, it's crashing all the time when I'm rendering big scenes with proxies or forest pack Pro object, whaterver the value of Out of core memory and GPU headroom.
I did a clean installation of the NVidia studio driver (with GURU in safe mode) like you said but nothing helps !
It's either "GPU Failure" or 3dsmax shutting down with no warning
EDIT : I've found out that motion blur on my proxies was responsible of the crashes.
First I launch a render without MB, then I can reactivate it with no troubles
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Wed Jan 29, 2020 2:30 am
by coilbook
why can't you fix standard particles motion blur direction once and far all. We posted like 5 reports for many years about incorrect mb direction at different frames
Thanks
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Thu Jan 30, 2020 3:41 am
by neonZorglub
coilbook wrote:why can't you fix standard particles motion blur direction once and far all. We posted like 5 reports for many years about incorrect mb direction at different frames
Thanks
Hi coilbook,
I re checked some of my samples; it works for me;
it could come from loading an old scene, that would need to update some settings.. or maybe issues with MB sample count more than 2 ..
I'll investigate more..
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Thu Jan 30, 2020 3:42 am
by neonZorglub
mbetke wrote:Works really cool so far. Had a "material conversion" day here and not a single crash. Also fast browsing.
But noticed two things:
1. Color Correction: Brightness can't set higher than "1.0"? In old version I was able to place higher values. It is intended?
also
2. On Mix Texture I can't swap materials anymore. Only copy and instance is there.
Hi mbetke,
Thanks for reporting.
Those 2 issues will be fixed in the next release.
The missing xRef for forest pack will also be fixed
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Thu Jan 30, 2020 4:39 am
by coilbook
neonZorglub wrote:coilbook wrote:why can't you fix standard particles motion blur direction once and far all. We posted like 5 reports for many years about incorrect mb direction at different frames
Thanks
Hi coilbook,
I re checked some of my samples; it works for me;
it could come from loading an old scene, that would need to update some settings.. or maybe issues with MB sample count more than 2 ..
I'll investigate more..
Thank you. I will share the scene tomorrow. Please look into instance objects like itoo using too much vram. We went from 400k grass objects to 1.4 mill and max crashes even though it's just instance
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Thu Jan 30, 2020 11:15 am
by remKa
Hello,
yesterday everything was working fine (with my motion blur deactivated in the first place then reactivated), but today everything is crashing just after scene evaluation.
Scene is using 8gb of VRam, I tried with and without Out of Core and different values of GPU Headroom with no luck
I have 3 proxies cars with motion blur in a 6 million poly scene (with 1 big xref).. the difference between yesterday and today is that I've modelled a 2000 polygons object, not a big deal !
When the render is starting (1 time on 5), with Out of Core on, some material with displacement are missing and some objects are transparent.
My specs : Windows 10, last NVidia studio driver (with clean guru install), 32 GB DDR-4, 2x 1080ti and a Titan XP
thx
EDIT : please see the Log attached (I didn't change any materials or textures since yesterday)
EDIT 2 : when I remove displacement textures (from quixel materials), everything works fine
Re: OctaneRender® for 3ds max® v2019.1.5 - 8.17
Posted: Thu Jan 30, 2020 2:32 pm
by paride4331
remKa wrote:Hello,
yesterday everything was working fine (with my motion blur deactivated in the first place then reactivated), but today everything is crashing just after scene evaluation.
Scene is using 8gb of VRam, I tried with and without Out of Core and different values of GPU Headroom with no luck
I have 3 proxies cars with motion blur in a 6 million poly scene (with 1 big xref).. the difference between yesterday and today is that I've modelled a 2000 polygons object, not a big deal !
When the render is starting (1 time on 5), with Out of Core on, some material with displacement are missing and some objects are transparent.
My specs : Windows 10, last NVidia studio driver (with clean guru install), 32 GB DDR-4, 2x 1080ti and a Titan XP
thx
Hi remKa,
what about your parallel sample setting?
Regards
Paride
EDIT : please see the Log attached (I didn't change any materials or textures since yesterday)
EDIT 2 : when I remove displacement textures (from quixel materials), everything works fine