Image Compression for Image Texture Very Unstable

Forums: Image Compression for Image Texture Very Unstable
Sub forum for bug reports

Moderator: aoktar

Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.

All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).

Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.

Image Compression for Image Texture Very Unstable

Postby Seun116_1 » Fri Feb 05, 2021 3:01 pm

Seun116_1 Fri Feb 05, 2021 3:01 pm
This was a topic that I originally posted about in the Octane Render Facebook group, but I've been forgetting to bring it up here. In short, I'm very confident in saying that using the image texture compression causes octane to be very unstable and makes it vulnerable to loads of crashes. It's been over a month and since I've eliminated the image texture compressions from our workflow, we haven't experience any Octane.dll crashes on our machines (a total of 3) which used to be multiple times a day. I'll post the Facebook post below for context. I'm not sure if this has been addressed in recent Octane updates, but this has been my experience on Octane 2020.1.5-R4:

From the Facebook group:

For the last 3 weeks, I’ve been able to run Octane on 3 separate machines with 0 crashes. This is absolutely crazy considering having to deal with crashes multiple times a day on Octane was the norm. I’m on Octane 2020.1.5-R4 on C4D R21.207 (but I suspect this can apply to any version of Octane and C4D). The two fixes I found that radically improved stability was:

1. Disabling Denoiser on certain cards. My 1200W PSU was not sufficient enough to have AI Denoiser enabled on 3x RTX 2080 Ti. Having this config would cause my computer to blue screen and shut down, specially when I would render to Picture Viewer/use Render Queue. The solution was to check Octane settings and disable AI Denoiser on 2/3 RTX 2080 Ti cards before I would send to render. On a machine with 1200W PSU and a 1080 Ti and 2080 Ti, BSOD was never an issue.

2. Disable all image compression for image textures by leaving it at default setting of “Automatic”. This was a recent solve I learned from David Baril (Thank you!). It felt like the elusive issue that’s plagued all my projects and causes a seemingly stable project to all of a sudden crash repeatedly. I always used this option to save VRAM, and it’s really good, but it turned out to result in Octane being very very very unstable. The moment I reset all image textures back to automatic, my projects immediately became stable and has remained so these last few weeks.

It would be nice to see this get resolved because the VRAM saved from the image texture compression is really nice haha
Licensed Customer
Licensed Customer
Posts: 50
Joined: Thu Dec 13, 2018 9:33 pm

Return to Bug Reports

Who is online

Users browsing this forum: No registered users and 3 guests

Sun Apr 18, 2021 5:23 am [ UTC ]