srek

You have two options. Either add a bitmap into your existing material and treat the to be painted texture as one of the layers of your material, or layer a second material over your existing material and paint in that. Your idea of just painting doesn't work because you need a bitmap to paint on.

Create an object. Create a material. Choose Create New Texture from the Color slots context menu. Apply the material to the object. Switch to Paint layout Open Material Manager Click on the red cross to enable painting Paint

The wizard is there to start you up with a new material to paint on. Don't use the wizard if you want to paint on an existing bitmap in an existing material.

You need, preferably non overlapping, UVs to paint. However, depending on what you want to do, you can get away with simple optimal mapping.

We have quite a few harsh critics on the team, they are a lot more helpful than fanboys would be.

It is important to understand how active and default selections work. In the selection string active refers to the currently selected elements, this can be whatever you selected manually or what was selected by any selection modifier. The default selection is similar, but different to active it behaves as if every element is selected when none are. Any modifier operation you do will work on these seleceted elements and after the operation the selection will be the result of it. I.e. after a simple subdivision of a single selected polygon you will have the resulting two polygons selected and every following geo modifier will act on them. If you only use named selections you partly bypass this, the active selection remains unchanged then. You correctly determined how to use stored selections to be able to switch between different selections within the modeling stack. The Newly Created asset can't work in the OM because it requires two geometries as inputs, something that is simply not possible in the linear list of the modeling stack.

I am not aware of a single Maxonian moonlighting as a Betatester. Of course we all participate in testing and reporting, but this is not an extra effort but part of our work. We do have an internal team that does structured testing, but our Betatesters are needed to test in real world scenarios. You can't make up for that in house. The number of issues reported is not a reliable indicator. Especially reports from the public are often based on other issues than actual bugs, more often then not user errors, where reports can be useful as well just not as bugs, or other unrelated things.

The Beta team is our first stop when it comes to giving feedback and proposing changes/ideas.

Betatesting is not paid in any way. It does require some time and effort. Some people come with the impression that it's all about being the first to play with cool new stuff, but while this is certainly sometimes true, most of the time will be spent trying and documenting things that don't work as they should. Usually only very late in development can Beta versions be used for any productive work, so working on actual production scenes is usually a no go. It can be quite frustrating at times, but Cinema wouldn't be where it currently is without the enormous help we received from our testers.

In the past, when i was head of QA, it was invite only. I don't know how exactly it works now, but i am not aware of any application process.

Sorry, i forgot to tell you that you don't need the Geometry Op anymore, it just complicates things if you switch the Cube node. The difference is that Op nodes are meant to build object hierarchies.

This would be a job for Loop Carried Value node

It still works the same, but in 2023 you get the primitive by default instead of the Op. Right click on the Cube node and switch it to Op mode. Alternatively you can add a Matrix Op and Color Op after the Geometry Op and feed the color and Matrix there.

If you want to use parametric text you have to solve this via the material projection. You can of course convert any text to polys and do a UV mapping by hand that matches your needs, but the effort is quite high. The Triplanar solution i posted is close to what you imagine with "rolling" over the edge.

The one thing that pops in my mind is an adjusted triplanar projection. Check the attached file for aquick and dirty example Triplanar Offset 01.c4d

Points 1,3 and 4 are on a line. Simple float rounding errors make it highly likely that point 4 is located within the triangle defined by the other points. This means that the triangulation of the polygon produces coplanar tris, more or less a 180° crease. This is a special case of non planar polygons. You can make this visible by triangulating the polygon.

In your example the pixels aren't pixels, they don't have an individual color each but are basically cutouts. Do you want pixels or cutouts?

Not by material, but you can split it by polygon selections, which in many cases results in the same thing. Split Poly Selections 02.c4d

Keep in mind that on modern windows versions a simple application can't crash to BOD. This is only possible for near hardware software (drivers, BIOS etc.) or hardware errors.

You can not change the hierarchy in the OM using Xpresso. You can control the matrix of any object to make it follow a different object as if it were a child of it.

In Scene Nodes that would be Transform Matrices (or Arithmetic:Multiply (Matrix)), in Xpresso Math:Multiply (Matrix) will do it.

Scene Node modifier capsules can only modify the geometry of an object, but not their matrix. For that you would need Xpresso. This is a core difference of the two systems.

If you don't know what makes a setup slow it often helps to enable the heat map. In this case it will show you that roughly half the computational time is used in the subdivide node. I fear there isn't much you can do to speed this up.

Sorry, I’m not in the position to talk about future plans.

Xpresso is over 20 years old. Quite a few resources on it are printed books or otherwise not as easy to find as YouTube videos. Regardless its age it is still a premiere tool in Cinema 4D and there to stay.