bezo

You could apply texture for part of selection in case you use thicken generator.
(Using this way you will not loose abbility of variable thickness like it happend in case you convert generator to polyobject and use standard selections/textures)
 

Turn off Isoline editing for viewport

Use Restriction tag. Apply it on deformer and drag your polyselection into it...
 

Its possible you´re in "redshift render mode" and want to choose standard c4d camera?

In Move/Scale/Rotate component mode just double left click on single point will give you coord. for currently selected single point. For more points you could open Structure manager. Shift+F9 and switch it to point mode

Hi Brandon,
 
I know you play a lot with complex/huge scenes with a lot of geometry, animation etc...
(remember your engine animation, looks like you still stick with the same company)
 
So, what I expect? In your scene with battery open view menu/Options/Level Of Details and check settings. If you have "medium/low", set it back to "high".
Personally I always use Gouraud Shading (Lines) mode where you could directly see interpolation/segmentation/flow of the mesh
 
I was right? 🙂

Other objects you can drag? Try to check filter if not show animated only.
 

Here is updated file. Remain just single setup and for example is used also build-in spline node primitive for checking. Is that what you mean to achieve?
(for "dense" detection you need to have more points on spline, that´s the reason why increasing number of intermediate points is needed)
scene file :  Test Slice_0003.c4d
 

 

 

 
 

I think problem is with n-gon and its representation as UV map.
Please, why you´re using n-gons for it. With Remesh function you could create perfect geometry/nice looking UV map with 2 clicks...
 

 
crazy_remeshed.zip
 
 
 
 

Maybe should be issue with priorities. When you turn of SDS, wertex map works as expected

Use matrix honeycomb mode as source for distribution...
(with effectors applied on matrix can be created nice effects, f.e. " live" creation of hexagons etc...)
 
VF_hexagons.c4d
 

Points are projected correctly, overshooting what you see is made by tangents. You need selectec each points with these "broken" tangents and adjust them manually...
 

 

César Vonc plugin pack works fine fine selection pattern (especially select n-th). Screenshot is from latest R2023 version, tested right now...
(selected loop, applied plugin)
 
https://code.vonc.fr/selections
 

Scale object in object mode not model mode...
 

For adding "something" behind the numbers just use adding in string mode as said @MJV.
Here is simple example with existing/known number line. Using this way no matter if your numbers are integers/reals with few decimal places, "m" will be always added at the end of number. If you need one empty place before m (offset m by one empty place), simply change constant string  value to " m" (empty place, then m)
 
add_string_mode_scene.c4d

...and its disabled in render settings. Enable it and use button "Copy from IRR" to recieve automatic IRR size
 

Did you tried fix it this way?
 

btw, FFD not change point count of deformed object. It simply deform geometry. If you use "current state to object" command, intermediate points/spline settings becames reality. This is the real reason why your spline has increased point count after conversion.
 
For example if you set intermediate points to Uniform with number 1

 
your spline after "current state to object" will have only 259 points and still looks enough for using in animation or as path for sweep.

...or hide bones/joints in whole mixamo rig (selecting by "none")
 

There´s a python effector directly for this, but not updated to latest version used in latest c4d releases.
 
https://aturtur.com/pile-up-effector/

Use Selection filter for viewport. (then no matter if live or rectangle selection tool used)
 

 

something like this?
 

 
Clones rotation_bezo.zip

- select all childs of fracture object
- press and hold Alt and click on icon for adding null object.