- 02.jpg (84.54 KiB) Viewed 4441 times
OctaneRender® for 3ds max® v2.24.2 - 2.15 [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.
Scrudje
r9 3900x/64Gb/2070s/2070/win10x64/3dsmax2021
Bug.
Rendered a scene at 18000x12000 pixels. On two dedicated Titan's. and I have one other card for display.
Used a large displacement texture @ 8K res.
I cancelled render at a certain point.
GPU3 cleared GPU memory after render cancellation.
But GPU2 some how continued reporting 5800 MB of Vram being used.
In the end In the device panel. I turned off all cards and pressed apply.
Then the all Vram's usage have been cleared.
These reports are from MSI Afterburner software.
Rendered a scene at 18000x12000 pixels. On two dedicated Titan's. and I have one other card for display.
Used a large displacement texture @ 8K res.
I cancelled render at a certain point.
GPU3 cleared GPU memory after render cancellation.
But GPU2 some how continued reporting 5800 MB of Vram being used.
In the end In the device panel. I turned off all cards and pressed apply.
Then the all Vram's usage have been cleared.
These reports are from MSI Afterburner software.
My Portfolio
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
Hi I have tried to put the exact value of your obective 60mm f 1.6 and realized that it's much more complicated than it turned out = f1/6 = aperture I found only in standalone and its values of 1.8 and 60 mm helped me to calculate the standard camera 60 mm = 19 FOV ==== is it Possible to simplify the calculation ?!?!?!?!
- Elvissuperstar007
- Posts: 2506
- Joined: Thu May 20, 2010 8:20 am
- Location: Ukraine/Russia
- Contact:
bug converter Vray cam to octane
win 7 /64x C2Quad 6600 2.4/ Nvidia 9800 GX2 1gb 512 bit + Asus 480 GTX/ DDR2 8Gb / NVIDIA 460 GTX 2GB/2x NVIDIA 580 GTX 3GB
Page octane render " В Контакте " http://vkontakte.ru/club17913093
Page octane render " В Контакте " http://vkontakte.ru/club17913093
I guess Hair&fur is no longer supported other than rendering it as geometry? Which is a terrible pain regarding memory resources .
Is there any sign of supporting it in the near future?
Or it's a dead end whether because of max SDK limits or Octane dev team focus?
I know ornatrix works to some point I have an older licence . I'm currently looking forward to solve my hair scenes in native hair plugin.
Is there any sign of supporting it in the near future?
Or it's a dead end whether because of max SDK limits or Octane dev team focus?
I know ornatrix works to some point I have an older licence . I'm currently looking forward to solve my hair scenes in native hair plugin.
My Portfolio
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
Hi Jim
I have an issue with a glass object. If I set the caustic blur higher than 0 , it behaves strangely and the glass doesn't let the light pass correctly. I think it's the same issue that Goldisart exposed earlier.
Is this a bug or just need to change the workflow to avoid using caustic blur?
Thank you so much
I have an issue with a glass object. If I set the caustic blur higher than 0 , it behaves strangely and the glass doesn't let the light pass correctly. I think it's the same issue that Goldisart exposed earlier.
Is this a bug or just need to change the workflow to avoid using caustic blur?
Thank you so much
Max 2014 64bit
It seems the viewport is very laggy compared to previous versions, not sure if this is really an Octane bug but it started after I updated it to the latest, even in simple scenes.
Bug:
Displacement issue? Seems displacement is somehow incorrectly shadowed.
With displacement:

Without displacement:

Note that unchecking "Enable displacement" doesn't fix the issue, I have to remove the displacement map itself.
It seems the viewport is very laggy compared to previous versions, not sure if this is really an Octane bug but it started after I updated it to the latest, even in simple scenes.
Bug:
Displacement issue? Seems displacement is somehow incorrectly shadowed.
With displacement:

Without displacement:

Note that unchecking "Enable displacement" doesn't fix the issue, I have to remove the displacement map itself.
Hi, i just bought the software and in downloads linked me to the 2.13 version. Should i use this one instead as latest? thanks