Hi Luey and welcome to our forum!

Sure, best place on bugreports is forum simply because it's better structured. Don't hesitate and send you messages here.
Next version we will try to imrpove materials.

We use Cinema 4D image reader to get HDR pixels but probably missed some parameters (probably the order of channels and some exposure). Please, can you send me HDR which are loaded with problems (e.g. red and black) so we can make fixes with samples. If you need, we can sign an agreement not to distribute it to others, of course we don't want to distribute it.

Best regards,
Kirill

Actually there is some texture caching system in CentiLeo which exploits the disk space and assumes there is a lof of disk space (better if it is SSD, but working from USB is also ok). So, the idea of this cache is to create once and store prepared texture data for potentially out-of-core texture access from RAM and later from GPU renderer. If there is enough disk space then everything should be fine even if we have 500-700MB of texture cache inside GPU and 4GB on RAM. The scene amount of textures can be very high in this case (100s of GBs). It also saves and limit RAM size for other tasks. And the other good thing is that if texture cache .mctx is built once then texture parsing is not repeated again after later program launches.

The problem of this method is that it pollutes the disk, creates raw uncompressed bitmaps out of even jpegs and so on. And we still have no utility/accounting manager to clean this thing if they become unnecessary. We plan to make compressor for this in the future and some asset manager.

Btw, the behavior you describe can be the reason of wrong HDR rendering (just the part of file is missing).