OctaneRender® for 3ds max® v4.04 - 6.17

Sub forum for plugin releases
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.
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

Hi Paride,
with this version 3ds max would just close itself during rendering. No errors, nothing.

Sometimes this error failed to download symbol
What does it mean?



and now these errors again


CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to wait for event
device 2: direct light kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to wait for event
device 1: direct light kernel failed

UPDATE:
Can a bad/faulty connection or network card on the master cause these errors? I noticed one time when viewport was opened network slave count was going from 20/20 to 10/10 and then back 20/20 (There are two slaves each holds 10 GPUs).
Both slaves had an error message about a stopped heartbeat. Octane on these slaves was restarted and it kind of fixed the problem but then if octane restart fixed it for now it can be a software problem.



Thank you
Attachments
error.jpg
User avatar
paride4331
Octane Guru
Posts: 3808
Joined: Fri Sep 18, 2015 7:19 am

Hi coilbook,
could you mail this issue to Octane help desk please?
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

paride4331 wrote:Hi coilbook,
could you mail this issue to Octane help desk please?
Regards
Paride
After many tests overclocking 3 master GPUs by 50 Mhz was the main reason for GPU failures.
richardyarlett
Licensed Customer
Posts: 197
Joined: Thu Apr 09, 2015 8:48 pm

NEW BUG introduced now.

When you hide an object that is a proxy, it disappears from the live viewer as normal.
When you UNHIDE that object it does not reappear. You have to then manually REFRESH the scene.

BIG PROBLEM.
User avatar
paride4331
Octane Guru
Posts: 3808
Joined: Fri Sep 18, 2015 7:19 am

richardyarlett wrote:NEW BUG introduced now.

When you hide an object that is a proxy, it disappears from the live viewer as normal.
When you UNHIDE that object it does not reappear. You have to then manually REFRESH the scene.

BIG PROBLEM.
viewtopic.php?f=80&t=71442&start=10#p362821
I just sent this issue to developers time ago.
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
richardyarlett
Licensed Customer
Posts: 197
Joined: Thu Apr 09, 2015 8:48 pm

Hi Paride
This also applies to the 2018 development as well. I have tried it and the same things happens so please let them know as well.
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

HI Paride,
not sure if you can help me with this. When octane viewport is opened and I have phoenix fire in the scene if I drag a time slider while octane viewport is opened 3ds max gets very slow because phoenix or octane creates 500 omni lights. I am not even sure if it is octane/phoenix bug or or just phoenix bug. Thanks
Attachments
omni.jpg
User avatar
paride4331
Octane Guru
Posts: 3808
Joined: Fri Sep 18, 2015 7:19 am

Hi coilbook,
I never had seen that issue before, could you share a file to me please?
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

HI Paride,
I guess there is another bug related to update static geometry and phoenix fd splashes (particles) When it is unchecked phoenix fd won't update splashes during animation even though it is not static geometry



Also

What does this mean when I render phoenix liquids with splash particles


Invalid mesh: vertex index out of range (17806/17804 at offset 105988)
Invalid mesh: vertex index out of range (17806/17804 at offset 105988)
cannot import a regular grid from an empty voxel buffer.
Invalid mesh: vertex index out of range (565865/565864 at offset 3379740)
Invalid mesh: vertex index out of range (565865/565864 at offset 3379740)
Invalid mesh: vertex index out of range (565865/565864 at offset 3379740)
Invalid mesh: vertex index out of range (565865/565864 at offset 3379740)

Thanks
Post Reply

Return to “Releases”