Model this???
-
I'm in the same position Dale is in, I cannot participate in the challenges that have a pretty extensive amount of modeling due to time constraints. I love the idea of smaller objects that will create a challenge. I really could use some challenges to help me with my modeling skills. Truth be told I'm not that great of a modeler
-
Good points. Ditto the last 2 posts.
-
Would others consider/agree that the general consensus seems to be.......
-
No texturing
-
Hidden Geometry 'On'
-
Clay Render [Optional]
-
Useful Models but not complex [due to time constraints/User ability]
Does this sound reasonable? I'm just trying to summarize the overall mood of the responses so far and in no way coerce the discussion away from those that think it should be more challenging and concept orientated.
Maybe Beginner/Intermediate/Advanced Challenges that would neatly tie into 'Render This' Challenge? Or is this too confusing?
-
-
I think texturing can be optional, it does IMO add to the overall model as well as being an integral part of the whole SU experience.
I believe that one can show model as you feel, be it rendered, clay, SU output, but as well as a line enabled view too.
Useful would be nice, however in some cases the challenge may be more based on creating a certain shape which may not always be useful, then again are we calling useful for archvis, gaming or hobbyist?
I do understand that they should not be to complexed and time consuming, however some may well be, depending on ones ability to find a solution I guess, and if one is using a ruby or straight vanilla SU (there can be many hours saved with ruby)
I do not believe we should categorise it in experience levels, regardless of ones skill level the model may be more challenging to less experienced users or easier, depending on the approach, the good thing is it's all a learning process and what is not known in the beginning will have a clear solution in the end.
-
@solo said:
I do understand that they should not be to complexed and time consuming, however some may well be, depending on ones ability to find a solution I guess, and if one is using a ruby or straight vanilla SU (there can be many hours saved with ruby)
just using a bike for an example.. there's nothing stopping anyone that wants to be involved to just do part of it.. like:
'hey, check out this technique i used for doing the seat' etc.. you might not win that thousand dollar prize by only submitting the seat but it would still be a helpful contribution to the exercise and a chance for you to practice something you might not normally draw.. (imo) -
IMO I don't think rendering should be part of it. A basic SU and a wireframe/hidden geometry output should be the max required, texturing should be optional. If we want to tie it in to "Render This:", perhaps a vote for everyone's favorite model from the "Model This:" challenge could be used to pick a "winner" and that model moves on to be a "Render this:" item. Or, rendering could be done on a separate thread like "Model this #5: Rendered".
Just ideas.
-
OK....count me. Let's pick an object and get going...is it a bike or....?
-
Nah, the bike shouldn't be it.
The screwdriver picture or something along those lines might be a good start? -
I got the first item, I will post it tomorrow morning (Monday).
-
Sounds good. I wasn't too keen on the bike either...
Advertisement