
OctaneRender® for 3ds max® v4.00-RC6 - 6.08 [OBSOLETE]
Forum rules
Any bugs related to this plugin should be reported to the Bug Reports sub-forum.
Bugs related to Octane itself should be posted into the Standalone Support sub-forum.
Any bugs related to this plugin should be reported to the Bug Reports sub-forum.
Bugs related to Octane itself should be posted into the Standalone Support sub-forum.
It would be cool to expose these buttons to renderer properties, so we can use in maxscript. 

YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
Keep nodes is kind of magic ! But if just moving an object octane reload the geometry... strange.
Where is stored all the data ? When opening Octane render devices préférences, after closing octane viewport window, no memory is used by the gpus.
Where is stored all the data ? When opening Octane render devices préférences, after closing octane viewport window, no memory is used by the gpus.
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
- SergKlyosov
- Posts: 126
- Joined: Wed Mar 01, 2017 9:33 am
- paride4331
- Posts: 3813
- Joined: Fri Sep 18, 2015 7:19 am
Hi HHbomb,HHbomb wrote:Thank you Paride ! I know where are the buttons know. But It seems to work with only movable proxies, or I'm wrong ?
When using non movable proxy, there is no effect. ( or so small perhaps )
I personally always use everything movable proxy now, I would like developers to set everything movable proxy as default.
I see no more convenience not to use all the movable proxy.
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
- paride4331
- Posts: 3813
- Joined: Fri Sep 18, 2015 7:19 am
Thanks SergKlyosov,SergKlyosov wrote:I found reason why render had stuck at "Scene evaluation" stage
It is happening after texture compression of an RGB Image node
I can confirm your issue.
A workaround get back to Faster (compression).
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
- SergKlyosov
- Posts: 126
- Joined: Wed Mar 01, 2017 9:33 am
Hi Paride,paride4331 wrote:Thanks SergKlyosov,SergKlyosov wrote:I found reason why render had stuck at "Scene evaluation" stage
It is happening after texture compression of an RGB Image node
I can confirm your issue.
A workaround get back to Faster (compression).
Regards
Paride
For which setting are you referring to? I can't see "faster" option in compression settings of RGB Image node
Also haven't found them in the Global Settings
Win 10 64 | RTX 3090 | i9 9980XE | 64GB RAM
- SergKlyosov
- Posts: 126
- Joined: Wed Mar 01, 2017 9:33 am
I have 16k normal map which eats a lot of memory, so I decided to compress it. I don't see any quality change in my render, but it frees 1GB of VRAMDartFrog wrote:I found "faster", but I'm not sure it's working. I can't go through all my maps and change this. I'm reverting back to prev version.
I have only these options inside texture compressions settings, see attached image
Win 10 64 | RTX 3090 | i9 9980XE | 64GB RAM
i am getting this error. RC4 didnt have this bug Thanks
OctaneRender 4.00 RC6 (4000016)
CUDA error 400 on device 1: invalid resource handle
-> failed to launch kernel(kernel63)
CUDA error 400 on device 2: invalid resource handle
-> failed to launch kernel(kernel63)
CUDA error 400 on device 2: invalid resource handle
-> failed to launch kernel(kernel63)
CUDA error 400 on device 1: invalid resource handle
-> failed to launch kernel(kernel63)
CUDA error 400 on device 2: invalid resource handle
-> failed to launch kernel(kernel63)
OctaneRender 4.00 RC6 (4000016)
CUDA error 400 on device 1: invalid resource handle
-> failed to launch kernel(kernel63)
CUDA error 400 on device 2: invalid resource handle
-> failed to launch kernel(kernel63)
CUDA error 400 on device 2: invalid resource handle
-> failed to launch kernel(kernel63)
CUDA error 400 on device 1: invalid resource handle
-> failed to launch kernel(kernel63)
CUDA error 400 on device 2: invalid resource handle
-> failed to launch kernel(kernel63)
Last edited by coilbook on Thu Oct 18, 2018 3:38 pm, edited 1 time in total.