Page 2 of 4

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Wed Sep 18, 2019 2:22 pm
by paride4331
coilbook wrote:Hi Paride,
Do you know what's the proper way to control HDR map sun brightness? HDR settings, gamma or power ?

Thanks

Hi coilbook,
set gamma 1 then increase the power.
Regards
Paride

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Thu Sep 19, 2019 2:16 am
by coilbook
When doing xref objects movable proxy to another scene gets unchecked

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Thu Sep 19, 2019 8:57 am
by paride4331
coilbook wrote:When doing xref objects movable proxy to another scene gets unchecked


Hi coilbook,
xref scene and xref object movable proxy seem to work fine.
Regards
Paride

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Fri Sep 20, 2019 2:09 am
by coilbook
Hi Paride,
I know I bugged you about Phoenix particle texture for a long time. Currently octane renders Phoenix red particle wetmamps as spheres which makes it useless. Phoenix particle texture acts as a mask of black and white to mix dry and whet materials. Do you know anyway to get phoenix texture to work with octane. Like OSL or something. is it really that difficult to make it to work with octane? Or at least have a dirt texture that remembers where a mesh touched and changes to material number 2 even if mesh is not there
Do you know any work around?


The only solution we found is to render octane wetmaps as invisible spheres and when the touch the ground they trigger octane dirt material (the second material) which is wet material but then all other mesh that touches the ground also creates wet spots around it.

Thank you

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Fri Sep 20, 2019 11:12 am
by lunarstudio
Upon opening files/different scenes, some materials are randomly loading as completely transparent in standard default shaded viewports. They're invisible but the objects are still selectable. If I apply another material to them, then they reappear. Applying the buggy material again, they will disappear. In other instances, if I restart or load the files again, the materials may load without any issue.

My materials have been continuously updated from older versions which I suspect may have something to do with this, but again others that are older are randomly okay. Doesn't appear to be any reason. If I recreate the material from scratch and apply them within the same scene that is acting up, they will display.

They all render just fine regardless of visibility.

Here's a material that is acting up randomly. All other materials are working/seen fine within the current scene. If I open it up again, it will probably display fine again:
mat-error.jpg

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Fri Sep 20, 2019 1:08 pm
by coilbook
lunarstudio wrote:Upon opening files/different scenes, some materials are randomly loading as completely transparent in standard default shaded viewports. They're invisible but the objects are still selectable. If I apply another material to them, then they reappear. Applying the buggy material again, they will disappear. In other instances, if I restart or load the files again, the materials may load without any issue.

My materials have been continuously updated from older versions which I suspect may have something to do with this, but again others that are older are randomly okay. Doesn't appear to be any reason. If I recreate the material from scratch and apply them within the same scene that is acting up, they will display.

They all render just fine regardless of visibility.

Here's a material that is acting up randomly. All other materials are working/seen fine within the current scene. If I open it up again, it will probably display fine again:
mat-error.jpg


same here we have a mix material and it is clear in viewport like it has transparency . especially after xref it happens

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Fri Sep 20, 2019 1:08 pm
by Elvissuperstar007

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Fri Sep 20, 2019 2:08 pm
by paride4331
lunarstudio wrote:Upon opening files/different scenes, some materials are randomly loading as completely transparent in standard default shaded viewports. They're invisible but the objects are still selectable. If I apply another material to them, then they reappear. Applying the buggy material again, they will disappear. In other instances, if I restart or load the files again, the materials may load without any issue.

My materials have been continuously updated from older versions which I suspect may have something to do with this, but again others that are older are randomly okay. Doesn't appear to be any reason. If I recreate the material from scratch and apply them within the same scene that is acting up, they will display.

They all render just fine regardless of visibility.

Here's a material that is acting up randomly. All other materials are working/seen fine within the current scene. If I open it up again, it will probably display fine again:
mat-error.jpg


Hi lunarstudio,
I sent some reports to developers about material editor preview in the last few days.
Thank you for pointing.
Regards
Paride

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Sat Sep 21, 2019 3:45 pm
by coilbook
How do we use upsampling? Do I leave resolution at 1920 and during rendering it makes it twice bigger It is not working

I tried to turn it off and on and it is same size picture and even worse quality with 2x2 upsampling

Re: OctaneRender® for 3ds max® v2019.1 - 8.08

PostPosted: Sat Sep 21, 2019 10:53 pm
by Elvissuperstar007
Started logging on 22.09.19 00:45:59

OctaneRender 2019.1 (6000100)

JPEG: Corrupt JPEG data: 76 extraneous bytes before marker 0xd7
denoiserThread3 : Not enough free memory to run the denoiser. Required memory 453.47 MB
denoiserThread3: CUDA_ERROR_OUT_OF_MEMORY: out of memory
. Restart required
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB
CUDA error 2 on device 1: out of memory
-> failed to allocate device memory
denoiserThread1 : Not enough free memory to run the denoiser. Required memory 561.11 MB