Page 4 of 4
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Sun May 19, 2019 5:46 pm
by coilbook
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
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Mon May 20, 2019 10:23 am
by paride4331
Hi coilbook,
could you mail this issue to Octane help desk please?
Regards
Paride
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Tue May 21, 2019 3:21 pm
by coilbook
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.
NEW BUG introduced now
Posted: Fri May 24, 2019 8:03 pm
by richardyarlett
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.
Re: NEW BUG introduced now
Posted: Mon May 27, 2019 6:55 am
by paride4331
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
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Mon May 27, 2019 4:22 pm
by richardyarlett
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.
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Mon Jun 03, 2019 5:22 pm
by coilbook
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
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Tue Jun 04, 2019 7:57 am
by paride4331
Hi coilbook,
I never had seen that issue before, could you share a file to me please?
Regards
Paride
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Thu Jun 20, 2019 11:23 pm
by coilbook
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