[Sam Treadway]

Can you just go to the weight tag and delete that bone from the list?

…not sure what you mean by “proper color”. Each point can be weighted to multiple joints and will blend between the joint colors.

[Sam Treadway]

There is an error in C4D importing the UV’s (script console reporting turned on).
It may be that other apps can read the UV’s and overlook or disregard the errors while C4D has a stricter policy and simply cancels reading in the UV’s when it finds bad data.

Meshlab is good to have in the workflow when dealing with scans like this.
I’d just continue with that as a means to import, clean, verify, export.

The ‘strange dark jagged lines’ you see are due to the more linear way textures are scaled in C4D and the way they were created in the other app with hard edges and a black background. It’s aliasing the hard edges against the BG causing a sort of ‘drop shadow’ effect. An auto-erode feature would be nice to have.
With the material selected: Editor tab > Texture Preview Size = “No Scaling” should fix that.

[Sam Treadway]

Most of what you actually see in glass with a high transparency is reflections. Add a reflection map to the glass material…something as abstract as the scene and high contrast.

[Sam Treadway]

If I understand correctly what you are attempting, then you will need two versions of the mesh.
One version that is static (and hidden) to use as the attachment object for the cloner and a copy that is ‘morphed’ by the clone positions using XPresso.
Here’s a quick setup I made:
13892_deformmeshusingcloner.c4d.zip

[Sam Treadway]

No idea if this will work with you setup without first seeing the full clips but you could try rendering a motion vector pass from the real flow melting effect and use that for displacement/flow map in your compositing app.

[Sam Treadway]

Put the sphere and moText under a connect object and displace the connect object instead?

[Sam Treadway]

Just a hunch: try dividing the motion vector image by a power of 10 (10, 100, 1000)

[Sam Treadway]

Does it appear in the final render or just in the viewport?

Try changing the texture preview resolution to no scaling or a high value and see what happens:
Material Attributes > Editor > Texture Preview Size

[Sam Treadway]

This is all possible using xPresso. If you have the data to start with then you can manipulate it any way you want – sort it, iterate through it, offset it, clamp it, etc.
The MatrixMulVector node could come in handy if you have three points in the each dataset.

[Sam Treadway]

In your [user directory]/GPURenderer there should be a folder with a log file in it…a good place to start troubleshooting.
The very first time you start using ProRender it will need some time to compile the kernels agains your hardware.
This can take some time depending on how beefy your system is.

If this has already been done but it crashes then maybe something went wrong. Try deleting the “derived.cache” folder from your user directory and restarting C4D.

What version of C4D?
What hardware?
What OS?

Was it helpful?