Also, not from the 343 forum.
Those are the screens I was talking about, they aren't leaked though. Here are Higher res official ones, located under artwork. (warning 50mb each)
I have only posted this work on polycount, neogaf and here.
Printable View
Also, not from the 343 forum.
Those are the screens I was talking about, they aren't leaked though. Here are Higher res official ones, located under artwork. (warning 50mb each)
I have only posted this work on polycount, neogaf and here.
Thanks for the kind words.
I don't post on Modacity much, and if you look at this thread, its pretty evident why.
A lot of sentences written to disclaim previous pretentiousness. Very few sentences with legitimate criticism.
You can slowly see this thread devolve.
Why does anyone here talk as though they are the "final word" on anything?
It seems to me that if its necessary to disclaim every other sentence, there is a problem with the community.
I think YOUR work looks awesome Nuero, but what is the purpose of saying anything like that on any subjective matter? Let words stand on their own merit.
Now i'm :smith:.
I think it looks great (as a Halo 4 BR can), but I can hardly model a box.
The vets here have spent the better part of 10 years modding this engine, they know what needs to be done and how it needs to be done. So that kinda goes to their heads, which is unfortunate because this is probably the only modding community I know of where potential new talent is greeted with hostility instead of (legitimate) critique and advice.
You should probably spend more time modeling less terrible source material though. Or at least take some artistic liberties and fix the dumb grip. Alos move the scope forward about 3 notches on the "rail" so it's in the "correct" position for best eye relief.
Maybe its the fact that I worked on the BR for a few days, but I like the design.
I'm not really all that gun literate, so the ergonomics don't really make themselves evident as they do with other people that are bothered by them.
There is still room for improvement though. :downs:
I have to spoke to you somewhere and seen a thread, other than Polycount, must of been neogaf :S
Anyway, looking back at your wireframe your topology does look rather messy and actually rather awkward. The topology CAN sometimes affect the model, not by causing errors but due to how TurboSmooth sub divides the polygons.
Also, at the argument about who should have the final say, I will just let you know that neuro is a 3d artist for a living... nuff said.
And Computron, look at my wireframe. It's nice and neat (To a point) and makes sense. But I will say I really do like your grip, really nice.
Not the point, I said I liked his work, he sounds reasonable. I don't want this to be misconstrued.
Saying your "word is final" is just not constructive for a subjective matter or conducive to good discussion.
Just like t3h m00kz was saying when he was comparing this forum to polycount. The whole mood is different.
You got some clean wires.
I understand what n-gons can do to your model, but as previously said, I incorporated a lot of shapes and (what would normally be accomplished through floaters) straight into the mesh for practice. N-gons can be a nice tool as well.
This whole area would be pretty hard to incorporate with clean topo, which I presume is why you decided to float it:
Here's mine:
Concept:
I could spend more time and get it perfect, but in the end, that's what n-gons are for. As long as you got no artifacts or smoothing errors.
You got a nice model, can you post a non wireframe, lit version?
You've got talent. I see a lot of Halo weapons, but I barely see any Mass Effect weapons. Try taking a crack at those, the Mattock rifle and Eviscerator shotgun immediately come to mind for me.
I never mentioned n-gons. They are fine in some cases, zBrush doesn't like them really. But the area you pointed out is pretty simple to add into the mesh with clean topology, I just couldnt be bothered :P As how ive done the bake will come out more or less the same.