Octane crash occurs when saving render as .png, but only when Post-Processing is enabled:
Problem signature:
Problem Event Name: APPCRASH
Application Name: octane.exe
Application Version: 3.6.4.0
Application Timestamp: 594309b0
Fault Module Name: octane.exe
Fault Module Version: 3.6.4.0
Fault Module Timestamp: 594309b0
Exception Code: c0000005
Exception Offset: 00000000001856b4
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 728c
Additional Information 2: 728cbcfc1548a678c23a8d3fa9bf6779
Additional Information 3: 48ae
Additional Information 4: 48aee287c0c8c74df7592cc4e0dccc99
________________
Image Size: 16000 x 14000
Pan Cam
Crash Report
it seems like mine crashes with this message
Started logging on 15.07.17 15:53:00
OctaneRender 3.06.4 (3060400)
c:\dev\max_plugin\src\converterhelper\converterhelper.cpp(1208): func<RgbaToBitmap>: , Assertion type WARNING: condition "0" failed, <BAD: RgbaToBitmap(), src image: (1024,512), dest bitmap: (1920,1080)
>
Started logging on 15.07.17 15:53:00
OctaneRender 3.06.4 (3060400)
c:\dev\max_plugin\src\converterhelper\converterhelper.cpp(1208): func<RgbaToBitmap>: , Assertion type WARNING: condition "0" failed, <BAD: RgbaToBitmap(), src image: (1024,512), dest bitmap: (1920,1080)
>
Can someone from Otoy chime in on this? In the meantime, I can do a PShop Bloom effect, but I like the Otoy result better.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
Sorry for the really long delay. I got pulled off of that personal project by real work, and have not been able to get back to this problem until now.
I found the problem...It is that my resolution (16000 x 14000) was too large. By dropping to a lower res, I was able to once again, toggle post-processing on and off without issue. I dropped to 8000 x 7000 with no issues. So still need to find where the trigger point is. For this scene, anyway.
I found the problem...It is that my resolution (16000 x 14000) was too large. By dropping to a lower res, I was able to once again, toggle post-processing on and off without issue. I dropped to 8000 x 7000 with no issues. So still need to find where the trigger point is. For this scene, anyway.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
Great to hear that you could get around it, this is probably Octane hitting the VRAM limit. We are working on significant memory usage improvements at the moment so that will help you loading higher resolution and more complex scenes in the near future.
Another update. I dropped down to 14000 x 12250 and am able to toggle post processing on and off without issue, but cannot save out an exr, or even a png w/ post enabled.
According to the attached image below, there is plenty of video and system RAM left, even if Octane is not fully optimizing RAM resources. No other apps are running.
According to the attached image below, there is plenty of video and system RAM left, even if Octane is not fully optimizing RAM resources. No other apps are running.
You do not have the required permissions to view the files attached to this post.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.