Oh definitely 3rd Eye—but as they say (at least in the US), “when in Rome” (pun intended).
The terrain module is just a pipe dream–thought I’d throw it in there since we were talking about what we’d like to see.
If just ONE of the many items we’ve listed makes it into R9, it would be a good thing.
Don’t get me wrong, i’d love to see a terrain generator, or better a sea generator like Maya fluids, but i’d like to see ngons before any other thing because i think they’re more basic and necessary if compared to a terrain generator. :wavey:
Originally posted by ThirdEye_01
Don’t get me wrong, i’d love to see a terrain generator, or better a sea generator like Maya fluids, but i’d like to see ngons before any other thing because i think they’re more basic and necessary if compared to a terrain generator. :wavey:
yup, screw the fancy stuff… for now 
I’m tired of c4d just creating tris wherever it pleases :annoyed:
i tend to agree with you guys…more focus to the requests we make of maxon and what i feel are the basics to radically improve our experience of it…
personally i hope maxon take it seriously…and i like the idea of people being able to select what they want and sign etc…would be even slicker if it could auto complete the form on maxons site as it sounds like this is the only method of changing program input!
here are some minor/major improvements that I would love to see.
REALTIME FEEDBACK OF ACTIVE TOOL TEXT - Let there be feedback between the extrude family (ie all the tools that build faces upon faces like bevel, extrude inner etc.) and the text input box of the active tool window. So that if you extrude in the viewport, you see the numbers change in the requester.
This should be progam-wide… the weight tool would benefit from this as well. Imagine weighting visually and looking at the value, and then being able to type that value for other objects for that must have the same amount of weighting.
NGONS - definitely ngons. coming from lightwave , it drives me crazy to have to be so careful to not mistakenly generate tris as that takes forever.
VIEWPORT HEADER - PLEASE can we see in the view header the name of the view, ie top/ right/ front. When scenes get complex , (at least for me) it sometimes gets irritating to check which view I am working on.
Not a biggy, but I dont think it should be that hard to add. Even extreme 3d had it 
MIRROR OBJECT- like has been said earlier.
MAGNET RADIUS DISPLAY - It would be nice in the viewport to see a range where tool like magnet would exert influence. ie when you use the magnet tool, you see blue outlines showing radius/ shape/width.
Other tools would benefit from things like this. So in order not to make this list too long. A program wide implementation of strong feedback between viewport and active tool box.
cheers folks
Alfred
Zoogie Vision
thirdeye brought up an important note for all of you actually, the more focused users are on one or two features, the more likelymaxon might go for it, I meanif evryone asks for ten features then maxon might go for a few of the easier ones just because they look good for providing as many as possible, users seem happy for a short while because of so many new features, but then they are still disapointed that there are no ngons for example. beter everyone focus on the two they feel most essential, and don’tforget when each point release comes out, some thing many change, and thus your feature requests may change as well.
I think the compiled list thats eventually sent to Maxon should be short and sweet–but if there are specific things users would like to see implemented–and those things would be helpful to their particular workflow–then they should be posted here.
No one ever asked for TP or expecxted it to be included–but it turned out to be a powerful addition to the program.
But yes–the modelling tools could be improved upon.
My simplified list:
Object joining/smoothing,
N-Gons,
and better global texture editiing would be my top 3.
remeber rather than a fancy list, you should all submit this, its quantity over quality guys, the more people that submit a certain feature to maxon through their form the better, don’t send one request five times though, what maxon takes into account I think when looking at new features (this is my opinion not necessairly true) is that they look for what would be the features that would help the majority of users.
I would like to see.
Ngons
A more intuitive knife.
Colour balancing like you can do in Photoshop
A history brush type set up,with snap shots etc
Curves
And maybe a preview system like Viper for LW for both C4d and BP3d
Ability to take a snap shot of your image as opposed to create outlines.
Stu.
local rotation of points, edges or polys…i honestly don’t know if this can be done, but i haven’t found a way, unless i’m totally missin’ something.
if i select points, say, to rotate the jaw, i would like to rotate it at the jaw, not at the center of my selection…does that make sense? anyways, lightwave has it and i really enjoy it and i haven’t found a way to do that in c4d…if it can be done, please share…if not, then put it in, maxon!
here comes the complete list, tell me if it’s ok or not
MODELING
MATERIALS AND RENDERING
INTERFACE AND WORKFLOW
BODYPAINT 3D
SIMPLER, MORE ACCURATE AND FASTER DYNAMICS MODULE
NEW VOXELS MODULE THAT CAN USE CINEMA4D MATERIAL SYSTEM AND CAN INTEGRATE WITH THINKING PARTICLES (like Lightwave Hypervoxels, Maya Fluids…)
:wavey:
Awesome , Third Eye!
Since you mention a request for Renderman comptibility, would Lightwave Export be something Maxon could implement–or would that be a Newtek thing?
As some of us have found, being a cinema user can make it harder to get freelance jobs with studios that have an all Lightwave, Maya or Max pipeline. If there was smoother export to other apps it would mean more jobs for us.
For instance, (as I’ve been ranting about here and elsewhere ), building a model in c4d, then texturing and exporting to OBJ may insure that the model data is able to smoothly transfer from C4d to lightwave, but getting the textures and selections to transfer is a different story.
Originally posted by JoelD
[B]Awesome , Third Eye!Since you mention a Renderman comptibility, would Lightwave Export be something Maxon could implement–or would that be a Newtek thing?
As some of us have found, being a cinema user can make it harder to get freelance jobs with studios that have an all Lightwave, Maya or Max pipeline. If there was smoother export to other apps it would mean more jobs for us.
For instance, (as I’ve been ranting about here and elsewhere
), building a model in c4d, then texturing and exporting to OBJ may insure that the model data is able to smoothly transfer from C4d to lightwave, but getting the textures and selections to transfer is a different story. [/B]
The FBX support is just for that, don’t worry 
Wow that was quick. I think I blinked after posting the message and you replied!
OK now–what is this FBX thing I’ve been hearing about? i thought it was a camera data export/import thing.
Thanks Third Eye.
I rememebr reading that a while back but it wasnt clear to me then what level of compatibility it would provide. Would one need to purchase Kaydara Filmbox as well in order to export to, say Lightwave or Maya, or do all these apps now have an FBX module that allows for the import of projects in FBX format?
Maybe Srek or Mash can provide an FBX for dummies explanation.
Has this feature been added to C4d yet?