Thank you for scene! Will check it and get back to you. Currently I don't have installed Blender, but will analyze the situation with the icecubes.
I would like to share some specific thing that can be relevant to this scene as well. Have a look at Maxwell Render documentation last figure:
https://nextlimitsupport.atlassian.net/wiki/spaces/maxwell/pages/22684680/Nested+dielectrics I hope they don't mind )
So looking at the last figure you may see that a good way of modeling the overlapping refractive objects like bottle glass and water object is to use the concept of nested dielectrics. According to this concept the water object borders (see red line on the figure) overlap the glass object. Both are refractive and have different IORs. To resolve this physically some renderers use the priorities but CentiLeo uses "Is Liquid" setting in Transmission Tab. Is Liquid should be set On for liquids like water in this case in case of overlap and it will help to make correct refractions.
The other nice thing is the ability to set IOR smaller than 1. In this case you can use not the overlap but model the bottle-water objects as one object with the borders between glass and water mediums. And on the interface (the surface) between both mediums the IOR of material should be relative IOR equal to IOR(glass) / IOR(water). This can take some computations, but it will result in another way of correct modelling. However the "Is Liquid" concept is simpler Sure I will describe all of this in a documentation with examples

May you drop a scene to me to info@centileo.com for experiments with icecubes? With HDR texture, maybe using dropbox or google drive or some other filesharer.
Probably we can start with Transmission and/or Absorption = white and then start changing to get where it become different.
Also there seems to be the difference with gamma on rendered image or HDR itself. Or with expsure that you multiply for CentiLeo to get less dark, but still there is a difference.

Actually I see some reftaction pattern similarities in CentiLeo and RPR. But the lighting direction and highlights are differernt! Even the blue paper cover around the bottle have different highlights for both engines. At first try to make the lighting exact everywhere. For example start with identical HDR or Area rectangle or Directional light sources for both engines.
Another thing is that you have the ice cubes and water droplets on the bottle. These objects overlap with other refractive surfaces: with the water around and with the bottle plastic object. I would recommend to set and test "Is Liquid" for water in the bottle and the water around.

thrimanakatha, in CentiLeo refraction works the same way as in any other renderer: same values, same behavior. Refraction is managed in Transmission tab of material. So you have to enable Transmission toggle in the list of material layers, by default this toggle is off and you may see it black because of this. IOR is working the same way as everywhere. For example to make the water, you can switch On Reflection1 and Transmission in the list of material layers, set IOR = 1.4 for both Reflection1 and Transmission layers, leave weight = 1 and colors white and make roughness = 0 for both reflection and refraction.
If the shape of your object is complex the refaction may produce some black regions on image and to fix it you need more ray bounces. By default there are 8 ray bounces, they can be changed in render settings.
Also one other reason why you don't see refraction may be very high value for Reflection1 IOR if you use it. Usually refraction and reflection are combined, just make some 1.4 or 1.5 or something like that IOR for both and test results

thrimanakatha, sure! All you tell about is what I am also thinking. Actually CentiLeo output node doesn't expose the viewport color to the node in that node area. This viewport color port is one of the ports in output node parameters, and you can connect from there. The idea was to add the ability to connect any texture to this slot (diffuse, reflection textures, roughness, many others) just for tests and modeling purposes. But it's better to start with diffuse texture by default for viewport color and change it for different if something is connected.
Sure more render passes are in short term passes, they are very much needed.
Also the current development version has large accelerations especially for scene geometry compilation that happens between modeling and rendering passes.

Yes I think to make default diffuse to avoid this confusion. However my original goal was to encourage all to use IPR output more than viewport for uvw and texture modifications

thrimanakatha, as I already said you can setup the viewport color or texture in CentiLeo Output node, there is a viewport color slot there

Check the settings of the viewport. Non-node CentiLeo materials show textures in the viewport, I see them right now. As for the node materials just make connections. Working with connections in node space is very simple, it's just like nesting your textures to do a lot of complex operations

Are you confused with Cinema node system or with CentiLeo node space in particular inside Cinema node system? CentiLeo nodes just copy the functionality of old-style menu materials and shaders. But the difference is with the node display with connections.
In old menu based materials the centileo materials should be outputed to the viewport with all textures by default as far as I remember. Maybe it's switched off by yourself in display settings of C4D viewport

Ha-ha! If you use node based materials then you need to connect any texture / node you like to the Viewport Color port of the Output material node. So this is organized this way just not to overload the viewport with textures and not to waste the memory resources. But if you need to see something you can make this connection.
Actually I haven't made this default texture output to the viewport only because we have it in IPR which shows the textures at full precision and in arbitrary resoultion and it's fast enough for working with UV editing.

CentiLeo has interactiv preview render mode (IPR) which allows to see what you edit for geometry, light sources, camera and materials. You don't need to render the animation upfront and then see results. With IPR you can see the ongoing work in real-time. Also CentiLeo material textures are displayed in the viewport as well, but in lower resolution.
The transparent could be not working because of IOR value, it refracts with IOR = 1.4 by default. However Alpha doesn't have IOR, it's the same as refraction with IOR = 1.
As for material converter then of course we need it so much

The transparency and alpha both work, you just need to toggle the checkbox enabling them in material settings. By default they are off. And also there is transmission weight for transparency. It works like multiplier. It's valuable when you use a lot of material channels

Luminance is Emission for CentiLeo. As for normal map CentiLeo has bitmap with "Is Normal Map" checkbox, select it (off by default) and connect it to the bump map slot of course

Vertex Map is a tag that stores the float values drawn by user on top of a surface. They can be accessed with centileo nodes. The screenshots from here may give an idea https://centileo.com/news/145/centileo-for-cinema4d-0610/ Of course we need to describe it in the manual more precisely

Quote
ssjenforcer wrote: I also tried rendering a frame to confirm it wasn't working. And a rendered frame also had no Jiggle deformation

That's probably because you need to render frame by frame from beginning. Not a selected frame. But just use cached simulation, that works well and it's the only solution for deformation motion blur

CentiLeo reads colors of native Cinema material, but not textures. That's why you got it that way.
Vertex Map is used, to access the values of vertex map you should have it on your object and to get it as a texture you should use CentiLeo Vertex Map node. Up to 10 vertex maps are supported per object.

It looks like no too many options to cheat volumetric light inside a renderer. Maybe it can be done in a compositing tool such as After Effects, but I don't use it.

I have wathed at the scene you sent me. Thanks a lot! Actually CentiLeo currently needs to use own materials like CentiLeo Material. And it uses own textures like CentiLeo bitmap. To use inside material you should click the checker black&white button to the right side of material property (such as diffuse color) and create Centileo bitmap.
Same story with CentiLeo node space. Only own shaders are used.
As for native Cinema materials and textures in your scene we need to implement a material converter, which is a task for near future. I know it's needed and I have always postponed it )

ssjenforcer, I have detected the issue with Jiggle. So it doesn't work in our case in IPR because CentiLeo is doing asynchronous scene evaluation for IPR in a background thread. I have made it for a good reason: to improve the smoothness of modeling and interactive rendering with asynchronous loads. It deals with a scene copy and Cinema 4D has a bug there in some simulation cases. I can get rid of the issue on CentiLeo side if I replace the asynchronous scene evaluation with synchronous, and all the modeling edits will launch as expected but the GUI can have some interruptes in "Auto Scene Update" IPR mode during modeling.
To avoid the issues just in the existing version you can cache the simulation of Jiggle deformer. Just go to the Cache Tab and click "Calculate" there. It will compute all the coordinates for all frames upfront. And next after it these cached coordinates of resulting object will run smoothly with currenct CentiLeo approach.
Actually I was talking once with a simulation plugin developer and he recommended to always use simulation caching during rendering to avoid all sorts of issues, there could be some others too.

Auto Scene updates are off in the IPR in your screen shot. Also you may manualy update the scene for IPR. Click the buttone with bend arrows in IPR