Arnold seems unable to use the e5 series CPU

[south-cheng]

In c4d, Arnold seems unable to use the e5 series CPU, and no matter how I debug, only two threads are running. In Maya, Arnold can use all threads

[south-cheng]

We have solved the problem with tx textures. When using automatic tx textures, e5 will get stuck in infinite compilation and solve for tx textures. When rendering, manual compilation of tx textures can be used to achieve full core rendering

[thiago.ize]

The status message in your first image does say running maketx on your texture, so yes, this is the autotx. It's not stuck, but it can run slowly the first time you render if all the render threads are blocked waiting on the same texture to be generated. Once those tx files end up being generated and are on disk, autotx will not have to generate tx files and it will run much faster for the other frames.