Must be single case - I’m working with a lot of .obj and .fbx models and there’s no any issues. Could be nice move to send it to Maxon Support\Open Ticket to resolve it.
So, C4D… where next?
zeden
#108
If you want to see what comes next just open the Node Editor and have a look what you find there. Than go to the Maxon News page and see for what they just spent unbelievable 70 Millionen and than you know: Compositig Tool. Than go to jobs section and you see: something like Kinect mocap implemented most likely and some AR stuff.
Which means there won’t be massiv changes on Cloth, liquids and fluids, Particles etc anytime soon.
infograph
#109
3Dkiwi always used to say Maxon never tinker with old code if they have plans to replace it completely in a future release.
I don’t think there are any plans for an Xpresso or Thinking Particles replacement, the Field Forces stuff was plonked down on the standard particle system. It looks to me like Fields will extend the very basic Standard Particle system and that will be the TP replacement. I see absolutely no sign that C4D will get a deep nodal multithreaded programming environment either so the best you can expect is if Xpresso gets a facelift with the new shader node system.
For anyone needing fluids, cloth and a more powerful particle system Insydium will continue to bail out Maxon with Xparticles at a price though!
The more I think about Fields this was Maxon’s answer to a nodal workflow by eschewing it completely and bringing in the layer based Fields workflow. They probably decided it fitted more with the AE crowd’s worldview which is arguably their target market.
Having monitored the process of development of Blender’s new nodal particle system I have a fair idea how long it takes to implement a new system. The first iteration is due in August and has be solely developed by one developer in about 18 months which also included the foundations of the Function Nodes system. Maxon could’ve delivered an new particle system several times over since R16 when the new core went into C4D.
EricM
#110
Maxon’s development pace is glacial for sure, but it doesn’t really have anything to do with “nodes” vs “Layers”.
Layers do have their place too. And in many case, they are much quicker and efficient to work with than nodes.
Nodes only start to make sense when there’s a certain level of complexity and, especially, the need to REUSE certain data over and over again, aka when there’s internal referencing. Otherwise a nodal setup can be less effective than a simple layer system, where some things are implicit (stacking, order, length…).
For instance, I recently made an experiment and tried to replicate a motion design piece in After Effects and Davinci Resolve/Fusion.
Imagine a simple text animation with 4 words entering one after the other…
In AE : it’s a stack of 4 layers, clean and simple.
In Fusion/Nodes : you need around 14 nodes to replicate the same setup
- 1 background node
- 4 text input nodes
- 4 transform nodes
- 4 merge nodes in series
- 1 output node
And that’s incremental, for “n” layers you need “3n+2” nodes. So for 10 words you need 32 nodes vs 10 simple layers.
So as much as I love Resolve and nodes, and dislike AE, for certain things, layers are clearly the way to go.
Some goes for an uber material vs a full node setup. Sometimes, less is more.
The reflectance system in C4D on the other hand might be a great example of how NOT to do it… shoehorn a layer system inside another layer system referencing outside data with duplicates (transparency, bump etc…).
infograph
#111
I never said it was.
In my opinion nodes win out in complex projects, in Houdini it’s much easier to keep a handle on things than to chase your tail trying to keep a tab on the Fields settings that are buried out of sight. It’s especially noticeable when you return to a project and have forgotten how all the Fields link together.
For small projects C4D is much the faster tool but on complex projects Houdini runs rings around it. It’s horses for courses, I personally wouldn’t use Resolve for Mograph, it’s ill suited but as a compositor it blows AE away. I have a gut feeling Resolve will get an AE style page for Mograph type jobs.
Maxon’s glacial development speed is independent of features and is ingrained in the company ethos. They’ve provided the minimum level of updates for years and told themselves it needs to be this way to maintain stability. It’s going to be tough for them to accelerate development from a standing start.
sartana
#112
Maxon’s glacial development speed is independent of features and is ingrained in the company ethos.
Nah, they were getting praise here for the speed of their updates - obviously many years ago - until they decided to chain their legs to a big heavy iron ball with their core rewrite, which we’re told eventually came out in R16. Assuming it took a few years to chuck that together - and that they’ve sometimes had stuff just about done nearly a year before it ships - then you can see C4D features slow up just as they dived into the beginning of that core rewrite, which was probably on their minds when R12 and R13 were rolling out.
Your idea that Maxon intentionally has a go-slow ethos, rather than them doing what Kiwi has said, not updating code which they know is going to be chucked, and not updating features which they know need to be allocated to development after various further parts of the core are done, just comes out of your usual bile and rancour rather than any evidence.
McGavran this morning on Twitter.
Hmmmm Universe, Cineware, Darker Colors, SP2, Maxon Moves… what’s next?
and Marc Zwaneveld
Modern UV tools, unified modern physics, multi-threaded s&t, Redshift working completely in the nodes context, modern rigging tools, updated xpresso UI, viewport performance with many objects, priority system overhaul? Just a few off the top of my head.
and EJ
What Marc said x1000000000
E2GO
#113
So… You’re not working at C4D… But know everything where Maxon fails and where Blender is better… We got it… Thanks.
May be at least some of your work examples could show how much you’re in Industry?
It could be a great step forward for people who’re trying to read your comments, to understand who’re you - troll or a professional, please? I’m asking not because I completely disagree with you but if you’ll make it more constructive - it’ll be more usefull and less offensive. TY
simonfarussell
#118
The level of debate on this forum is really not great.
Some of the points made are good but this kind of discourse is bad for everyone.
Many good people have left the forum and don’t contribute any more in large part because of the general tone here. I really don’t know what the solution is apart from people to simply be if not nice to each other, at least civil.
Srek
#121
Moderation might not always have been popular, but it cut stuff like this a lot shorter. I am all for a firey debate, but what happens here is just plain useless.
bullit2
#124
The Move app in IOS ecosystem only is another sign that Maxon wants to be tied to Apple universe and probably depends on it. If Maxon was company interested to service most common users they would have released an Android version too.