Jump to content

An open letter to MAXON CEO McGavran


Intenditore

Do you feel Maxon is taking an Adobe route?  

70 members have voted

  1. 1. Do you feel Maxon is taking an Adobe route?

    • Yes
      59
    • No
      11

This poll is closed to new votes


Recommended Posts

4 hours ago, Marander said:

 

Yes I agree. Xpresso with new Node system would be nice and it will come.

 

Of course it's nice to have features built-in but for UV mapping MAXON is way too late. I guess most users already have RizomUV which is hard to beat - or similar tools. Same for Bodypaint, how can they catch up with defacto standard tools like Substance.

Bodypaint is way too old to be relevant today, even with updates, I agree. Unless MAXON pulls a miracle here and basically creates another Substance Painter inside C4D it's not going to be used much. UV on the other hand is still important. I don't have RizomUV and never felt like I needed it, but the tools inside C4D are still lacking. They're just not comfortable to use.

Visit my Portfolio on Artstation.com & Follow me on Instagram

Link to comment

It would be nice if xpresso could get some sort of miltiprocessor support. I am aware that this is complicated for functions that somehow interact, but I always have parts that are independend and even a manual swich in the xpresso tag to use a certain core would be verry helpfull.

Nodes that would help to controll the amound of verteces of a object without the need to script would be nice to. I am shure that I can find some more ideas for xpresso when I come home from holidays 😉

Link to comment
28 minutes ago, Jops said:

It would be nice if xpresso could get some sort of miltiprocessor support. I am aware that this is complicated for functions that somehow interact, but I always have parts that are independend and even a manual swich in the xpresso tag to use a certain core would be verry helpfull.

Nodes that would help to controll the amound of verteces of a object without the need to script would be nice to. I am shure that I can find some more ideas for xpresso when I come home from holidays 😉

Multithreading is less an issue of Xpresso than the object system. Changing the structure of geometry objects need to be done in generators, this can’t really be done in expressions, again more a restriction of the object system. Xpresso as it is can only be based on the current object system, fundamentally different approaches have to wait for later.

Link to comment
11 hours ago, srek said:

I would be interested in what nodes you, or others, think are missing.

Cinema 4D could have a lot more procedural modelling type stuff if there were modelling nodes e.g. extrude. Even some limited stuff like a "Merge meshes" node where you hook up multiple objects to the Merge Mesh node either by wires or the node has a list function where you drag and drop objects. The Merge Mesh node then behaves like a procedural Combine function combing all of the source meshes / objects into one object. You can then apply booleans etc to the merged mesh object. And then a Boolean node where one object can be subtracted from a lot of other objects. Hooked up by XPresso rather than in the Object Manager.

 

Maybe things have changed since I was using CInema 4D but having nodes for render settings could be useful. Maybe the new nodal shading does this?

Link to comment
3 minutes ago, 3DKiwi said:

Cinema 4D could have a lot more procedural modelling type stuff if there were modelling nodes e.g. extrude. Even some limited stuff like a "Merge meshes" node where you hook up multiple objects to the Merge Mesh node either by wires or the node has a list function where you drag and drop objects. The Merge Mesh node then behaves like a procedural Combine function combing all of the source meshes / objects into one object. You can then apply booleans etc to the merged mesh object. And then a Boolean node where one object can be subtracted from a lot of other objects. Hooked up by XPresso rather than in the Object Manager.

 

Maybe things have changed since I was using CInema 4D but having nodes for render settings could be useful. Maybe the new nodal shading does this?

The first part goes well beyond expressions, but is certainly interesting. The second part is an own topic but something i personally would like to see, just like an at least basic compositing node system.

Both not really Xpresso features though.

Link to comment
17 hours ago, srek said:

The first part goes well beyond expressions, but is certainly interesting. The second part is an own topic but something i personally would like to see, just like an at least basic compositing node system.

Both not really Xpresso features though.

+1 for compositing 😉

Link to comment
18 hours ago, 3DKiwi said:

Cinema 4D could have a lot more procedural modelling type stuff if there were modelling nodes e.g. extrude. Even some limited stuff like a "Merge meshes" node where you hook up multiple objects to the Merge Mesh node either by wires or the node has a list function where you drag and drop objects. The Merge Mesh node then behaves like a procedural Combine function combing all of the source meshes / objects into one object. You can then apply booleans etc to the merged mesh object. And then a Boolean node where one object can be subtracted from a lot of other objects. Hooked up by XPresso rather than in the Object Manager.

 

Maybe things have changed since I was using CInema 4D but having nodes for render settings could be useful. Maybe the new nodal shading does this?

The procedural modeling thing is interesting but there always was an issue with parametrization. For example, to define an extrude you needed to define the faces that you want to extrude. Now if you procedurally change the object you extrude from, your previous manual polygon selection becomes invalid as it's now totally different polygons (bot the index and the count) that need to be extruded. So the old method of selection cannot be used.

 

With the advent of Fields, a selection can be made by using another object, which solves that issue - for polygons at least. Still, there are other types of parameters that would make a fully procedural workflow difficult. I wonder how other programs do it...

 

As C4D does its procedural modeling (as far as it exists) through the object tree hierarchy, I wonder whether extending XPresso is the way to go... of course you can use XPresso as alternative view to the objects in the tree, which sounds fairly interesting but maybe needs an adaption in the general paradigm here.

 

Link to comment
7 hours ago, Cairyn said:

The procedural modeling thing is interesting but there always was an issue with parametrization. For example, to define an extrude you needed to define the faces that you want to extrude. Now if you procedurally change the object you extrude from, your previous manual polygon selection becomes invalid as it's now totally different polygons (bot the index and the count) that need to be extruded. So the old method of selection cannot be used.

 

With the advent of Fields, a selection can be made by using another object, which solves that issue - for polygons at least. Still, there are other types of parameters that would make a fully procedural workflow difficult. I wonder how other programs do it...

 

As C4D does its procedural modeling (as far as it exists) through the object tree hierarchy, I wonder whether extending XPresso is the way to go... of course you can use XPresso as alternative view to the objects in the tree, which sounds fairly interesting but maybe needs an adaption in the general paradigm here.

 

There are ways around this. Modo has procedural modelling and while you can make selections in the normal way, these do get messed up if you change something earlier on. There's a whole swag of procedural selection options e.g. select by previous operation and then subsets of that, select by angle etc etc. Then of course the selection you made can be updated by reselecting / updating. I do a lot of my modelling now starting off with a procedural model. I can then experiment with various mesh densities. Much better than doing a whole heap of undo's and losing your modelling.

Link to comment
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • LATEST ACTIVITIES

    1. 220

      Scene Nodes | Capsules file pit

    2. 3

      Flipped clones in multi-segments curve

    3. 2

      How to create continuous UV texture for irregular wall like shapes ?

    4. 52

      Looking forward to the next C4D release

    5. 3

      3DTOOLS.INFO | SUMMER Special - 30% OFF!

×
×
  • Create New...

Copyright Core 4D © 2023 Powered by Invision Community