Thanks Ricky,
I PM'd you about that hair problem scene.
The "always on top"-change sounds great, thanks!
Cheers
OctaneRender 2023.1 for Houdini production (2023.1.0.3)
Moderator: juanjgon
Hey there,
currently I seem to be particularly unlucky, hehe. Here's another one. An Octane API error:
As you can see there's only 733MB used and 21408MB free. I have two 3090s. Am on Houdini 20.0.547 and this version of Octane.
I already did a clean reinstall of Nvidia drivers with DDU.
In the past I already had this error from time to time but completely random and everytime with different log results.
But now I do have a scene where it happens every single time when I start Octane. I could even reduce it to only two objects - one with only below 1000 points and another one which is rendered as fur, with about 5000 hair, which consist of only 40000 points.
If i disable one of those objects it renders fine. I can then even duplicate it very often and it still does. But as soon as both of those are visible I get this error.
Here's the scene:
https://1drv.ms/u/s!AiO-yRNxbYlojAWRXI6 ... S?e=B6G2XP
I really hope you can reproduce this.
Cheers
currently I seem to be particularly unlucky, hehe. Here's another one. An Octane API error:
As you can see there's only 733MB used and 21408MB free. I have two 3090s. Am on Houdini 20.0.547 and this version of Octane.
I already did a clean reinstall of Nvidia drivers with DDU.
In the past I already had this error from time to time but completely random and everytime with different log results.
But now I do have a scene where it happens every single time when I start Octane. I could even reduce it to only two objects - one with only below 1000 points and another one which is rendered as fur, with about 5000 hair, which consist of only 40000 points.
If i disable one of those objects it renders fine. I can then even duplicate it very often and it still does. But as soon as both of those are visible I get this error.
Here's the scene:
https://1drv.ms/u/s!AiO-yRNxbYlojAWRXI6 ... S?e=B6G2XP
I really hope you can reproduce this.
Cheers
Oh and here's the log-file for it:
https://1drv.ms/u/s!AiO-yRNxbYlojAZ5U-x ... n?e=e1nIrO
https://1drv.ms/u/s!AiO-yRNxbYlojAZ5U-x ... n?e=e1nIrO
-
ricky_otoy
- Posts: 289
- Joined: Mon Jun 19, 2023 6:34 am
Oh no! Yeah really hasn't been your week, so sorry!!
I can reproduce the error with your scene and build, but the good news is that it seems it doesn't appear on the new 2023.1.2 builds. (So far) This issue may have already been addressed in Standalone, but I will continue to test it.
There will most likely be a 2023.1.2 release tomorrow.
I can reproduce the error with your scene and build, but the good news is that it seems it doesn't appear on the new 2023.1.2 builds. (So far) This issue may have already been addressed in Standalone, but I will continue to test it.
There will most likely be a 2023.1.2 release tomorrow.