Fatal error: Segmentation fault Tweet

[juanto_92]

Okay, thank you very much, I will upload everything and put the link, even so, since I use octane in houdini, any project ends up breaking, I usually do 100 frames in a row. But there comes a time when I have to go from 5 to 5, 10 ... never more than 20 frames in a row, I do not understand why at the beginning it is going well, and once I get the error it already gives me always. Sometimes there is a numbering in the error, sometimes there is another and sometimes there is no message and it closes alone, I don't understand anything.

[juanto_92]

Thats the scene:

https://we.tl/t-k1BEsOuRhD

The simulation is not here because it weighs 11 Gb

But in this link I upload the frame 100 of simulation, because that's what i use.
https://we.tl/t-p6JsxtXnaP

In my scene they are cached from 1 to 100, but I suppose that only with frame 100 will it be the same.
My scene is the frame 100 of smoke simulation, in every frames with timeshift node.

[juanto_92]

from 1 to 100 SIM

https://fromsmash.com/W~ACDK4Q..-c0

Thanks

[juanjgon]

Ok. Thanks. I'll try to reproduce the problem here. In any case, the crash log file inside the scene .zip file comes from a successful rendering ... I wonder if the crash could be on the Houdini side. Do you know at what point Houdini crashes (while extracting the scene, while updating the GPUs or while rendering)?

Thanks,
-Juanjo

[juanjgon]

Ok. I think that this problem could be related to a problem already fixed in the Octane 2018 and Octane 2019 plugin builds. Do you have the license updated to work with these new builds, or do you still need to continue working with Octane 4.05?

Thanks,
-Juanjo

[juanto_92]

Okey Thanks!!!
I think the problem is in the passage of a frame rendered to the next frame, in the ipr window, everything always works, and when rendering a sequence fails, I save all the frames before the error. When I open houdini again, I render and until it fails, everything is exported well. I'm new to Houdini, I don't know if you have to configure something before using octane. I just installed it.

[juanjgon]

If you can't update to Octane 2018/2019, I can try to send you a custom 4.05 build with an attempt to fix this problem.

Thanks,
-Juanjo

[juanto_92]

I have V.4.05 because a year ago I pay "life license" but I dont know that 2019 and now 2020 are "different programs"

I would rather not update it, so as not to have the feeling of having thrown the money in the trash, but seeing how this works, I will surely use other renders ...

I don't understand how my mistake is a program error.
(an error of a paid program) and that the only solution is to pay the following program (2019, 2020 ...).
However, thanks for the quick responses.

[juanto_92]

Anything you can do to help me, you will be welcome, thanks

[juanjgon]

Yes, sorry, if the problem is what I think it is, this was an issue reported and fixed after the latest 4.05 plugin build release, so this is why it is not fixed on it. In any case, I'll try to port back this fix from the current supported Octane builds to the 4.05 plugin and send you by pm a custom build to check if it helps. I'll write to you as soon as possible.

Be aware that the only way to have the latest fixes and features in any software is to upgrade to the current version to be able to install the latest builds. It is impossible to support all the past builds available.

Thanks,
-Juanjo