[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/3/ - 3DCG


View post   

File: 142 KB, 750x620, sprytile_example_gif.gif [View same] [iqdb] [saucenao] [google]
572332 No.572332 [Reply] [Original]

Post low poly, talk low poly. If it's something you're working on then cool, if it's not then also cool.

To kick this off:
-I'm looking for good examples of low res/low poly or "pixel art on 3D' type models. Looking to see how other artists do it.

>> No.572340
File: 604 KB, 1292x686, dead_head_fred_by_lubu.jpg [View same] [iqdb] [saucenao] [google]
572340

>>572332
This too many polygons?

>> No.572341
File: 66 KB, 640x537, tronbonnecar.jpg [View same] [iqdb] [saucenao] [google]
572341

wish we had the models ripped from the misadventures of tron bonne, they're really good

>> No.572342

>>572340
looks awesome

>> No.572344
File: 114 KB, 928x702, megaman x8 layer.jpg [View same] [iqdb] [saucenao] [google]
572344

>> No.572356
File: 100 KB, 948x755, 543.png [View same] [iqdb] [saucenao] [google]
572356

the gran turismo 1 and 2 cars were beautiful

>> No.572358
File: 255 KB, 1600x1200, ws_Bloody_Roar_3_1600x1200.jpg [View same] [iqdb] [saucenao] [google]
572358

from bloody roar

>> No.572703
File: 2.19 MB, 1920x900, dragon___low_poly_by_pixaner-d9it0zr.png [View same] [iqdb] [saucenao] [google]
572703

>>572332
I made this some time ago.

>> No.572713

>>572703
That's not low poly that's faux poly.

>> No.572720

>anything with less polygons than the average zbrush sculpt is now low poly
I want all normies to die

>> No.572764
File: 811 KB, 2217x1159, burtman.png [View same] [iqdb] [saucenao] [google]
572764

>>572720
Lowpoly this fucker.

>> No.572767
File: 492 KB, 320x240, bruh.gif [View same] [iqdb] [saucenao] [google]
572767

>>572720
Nah bruh get this bruh now that the standards for high poly have changed that means the standards for low poly change too!
*conveniently ignores the fact that this would make "low poly" a near irrelevant distinction in modern realtime graphics since everything has a varying poly budget to hit and uses the same workflow otherwise*

>> No.572769

>>572340
That's sick

>> No.572787
File: 39 KB, 1000x750, 1252102-166202_dragon_ball__origins_2.jpg [View same] [iqdb] [saucenao] [google]
572787

Some of my favourite ones

>> No.572789
File: 31 KB, 650x487, dragon_ball_origins_conceptart_6VeEC.jpg [View same] [iqdb] [saucenao] [google]
572789

>>572787

>> No.572790

>>572356
those unfiltered textures and baked in highlights are sooooo good

<3

>> No.572791
File: 18 KB, 650x487, dragon_ball_origins_conceptart_F0XF1.jpg [View same] [iqdb] [saucenao] [google]
572791

>>572789
Those were in the Dragon Ball Origins games, for Nintendo DS.

>> No.572792
File: 16 KB, 650x487, dragon_ball_origins_conceptart_fRvGn.jpg [View same] [iqdb] [saucenao] [google]
572792

>>572791

>> No.572793
File: 25 KB, 650x487, dragon_ball_origins_conceptart_kD5en.jpg [View same] [iqdb] [saucenao] [google]
572793

>>572792

>> No.572794

>>572713
what is the difference

>> No.572795
File: 15 KB, 650x487, dragon_ball_origins_conceptart_mprgH.jpg [View same] [iqdb] [saucenao] [google]
572795

>>572793

>> No.572796
File: 20 KB, 650x487, dragon_ball_origins_conceptart_p2Jtx.jpg [View same] [iqdb] [saucenao] [google]
572796

>>572795

>> No.572797
File: 31 KB, 650x487, dragon_ball_origins_conceptart_SkGqp.jpg [View same] [iqdb] [saucenao] [google]
572797

>>572796

>> No.572799
File: 36 KB, 650x487, dragon_ball_origins_conceptart_xXZz8.jpg [View same] [iqdb] [saucenao] [google]
572799

>>572797

>> No.572800
File: 28 KB, 650x487, dragon_ball_origins_conceptart_Zw3K6.jpg [View same] [iqdb] [saucenao] [google]
572800

>>572799

>> No.572801
File: 78 KB, 1280x960, dragon-ball-origin-4e26469a44c32.jpg [View same] [iqdb] [saucenao] [google]
572801

>>572800

>> No.572802
File: 74 KB, 1280x960, dragon-ball-origin-4e26469b8d195.jpg [View same] [iqdb] [saucenao] [google]
572802

>>572801

>> No.572803
File: 82 KB, 1280x960, dragon-ball-origin-4e26469b20571.jpg [View same] [iqdb] [saucenao] [google]
572803

>>572802

>> No.572804
File: 110 KB, 1280x1040, dragon-ball-origin-4e2646969d84f.jpg [View same] [iqdb] [saucenao] [google]
572804

>>572803

>> No.572805
File: 78 KB, 1280x927, JackieChunSpecial(O1).jpg [View same] [iqdb] [saucenao] [google]
572805

>>572804

>> No.572806
File: 125 KB, 1049x1377, Launch(O1).jpg [View same] [iqdb] [saucenao] [google]
572806

>>572805

>> No.572807
File: 149 KB, 1073x1440, O1Krillin.jpg [View same] [iqdb] [saucenao] [google]
572807

>>572806

>> No.572811
File: 103 KB, 1280x960, O1Yamcha.jpg [View same] [iqdb] [saucenao] [google]
572811

>>572807

>> No.572814
File: 26 KB, 961x720, O2Android8.jpg [View same] [iqdb] [saucenao] [google]
572814

>>572811

>> No.572815
File: 28 KB, 730x548, O2Arale.jpg [View same] [iqdb] [saucenao] [google]
572815

>>572814

>> No.572816
File: 35 KB, 961x720, O2Bulma.jpg [View same] [iqdb] [saucenao] [google]
572816

>>572815

>> No.572818
File: 22 KB, 730x548, O2Devilman.jpg [View same] [iqdb] [saucenao] [google]
572818

>>572816

>> No.572819
File: 26 KB, 730x548, O2Draculaman.jpg [View same] [iqdb] [saucenao] [google]
572819

>>572818

>> No.572820
File: 22 KB, 730x548, O2Invisibleman.jpg [View same] [iqdb] [saucenao] [google]
572820

>>572819

>> No.572822
File: 28 KB, 730x548, O2Korin.jpg [View same] [iqdb] [saucenao] [google]
572822

>>572820

>> No.572823
File: 29 KB, 961x720, O2Krillin.jpg [View same] [iqdb] [saucenao] [google]
572823

>>572822

>> No.572824
File: 42 KB, 961x720, O2Metallitron.jpg [View same] [iqdb] [saucenao] [google]
572824

>>572823

>> No.572826
File: 30 KB, 730x548, O2Mummy.jpg [View same] [iqdb] [saucenao] [google]
572826

>>572824

>> No.572827
File: 29 KB, 961x720, O2Murasaki.jpg [View same] [iqdb] [saucenao] [google]
572827

>>572826

>> No.572831
File: 41 KB, 961x720, O2PirateRobot.jpg [View same] [iqdb] [saucenao] [google]
572831

>>572827

>> No.572832
File: 29 KB, 961x720, O2Yamcha.jpg [View same] [iqdb] [saucenao] [google]
572832

>>572831

>> No.572833
File: 134 KB, 1280x965, OolongCar(O1).jpg [View same] [iqdb] [saucenao] [google]
572833

>>572832

>> No.572834
File: 163 KB, 900x1425, Toninjinka(O1).jpg [View same] [iqdb] [saucenao] [google]
572834

>>572833

>> No.572835
File: 1020 KB, 512x384, 62DxNhG.gif [View same] [iqdb] [saucenao] [google]
572835

>>572834
Now some from DB Kai Ultimate Butouden.

>> No.572837
File: 107 KB, 1024x768, 2iq45xR.png [View same] [iqdb] [saucenao] [google]
572837

>>572835

>> No.572839
File: 1.20 MB, 256x384, 4YcxB4i.gif [View same] [iqdb] [saucenao] [google]
572839

>>572837

>> No.572841
File: 1.21 MB, 256x384, 98bxwGx.gif [View same] [iqdb] [saucenao] [google]
572841

>>572839

>> No.572843
File: 892 KB, 256x384, cWxilxY.gif [View same] [iqdb] [saucenao] [google]
572843

>>572841

>> No.572844
File: 3.84 MB, 512x384, gUUEkEe.gif [View same] [iqdb] [saucenao] [google]
572844

>>572843

>> No.572850
File: 798 KB, 256x384, kusbhTg.gif [View same] [iqdb] [saucenao] [google]
572850

>>572844

>> No.572852
File: 1.56 MB, 512x384, Lj8eNq8.gif [View same] [iqdb] [saucenao] [google]
572852

>>572850

>> No.572853
File: 1.77 MB, 512x384, WmC8xen.gif [View same] [iqdb] [saucenao] [google]
572853

>>572852

>> No.572854

>>572839
Are friezas arms not attached? Looks like the meshes are intersecting

>> No.572855

>>572854
Yeah, most models are built like this. Look at Boo and Goku's arms >>572844 >>572837

>> No.572857

Wish there were more tutorials out there for looks like this but I guess it's kind of a niche thing to go for that 'true' lo poly look that isn't just a reduced mesh.

>> No.572858

>>572855
Thats neat, I like how they sort of 'hid' the separation by making part of gokus gi part of the arm instead. Keeps it looking good when it moves

>> No.572859
File: 736 KB, 1920x827, LEgends.jpg [View same] [iqdb] [saucenao] [google]
572859

I've always enjoyed the style of the Legends games and I think a big part of that is because it seems the concept artist was pretty well aware of what was technologically possible when designing the characters.

>> No.572860
File: 577 KB, 1920x1080, LoPolyTron.jpg [View same] [iqdb] [saucenao] [google]
572860

>> No.572861
File: 407 KB, 1188x642, ServrBotLoPoly.jpg [View same] [iqdb] [saucenao] [google]
572861

>> No.572862
File: 253 KB, 987x642, CaskettLoPoly.jpg [View same] [iqdb] [saucenao] [google]
572862

>> No.572863
File: 714 KB, 1883x1351, GlydeLoPoly.jpg [View same] [iqdb] [saucenao] [google]
572863

>> No.572864
File: 607 KB, 1883x1172, TeiselLoPoly.jpg [View same] [iqdb] [saucenao] [google]
572864

>> No.572866
File: 855 KB, 1883x1146, BonLoPoly.jpg [View same] [iqdb] [saucenao] [google]
572866

>> No.572867
File: 738 KB, 1883x1146, BolaLoPoly.jpg [View same] [iqdb] [saucenao] [google]
572867

>> No.572869
File: 664 KB, 1883x1064, KlaymourLoPoly.jpg [View same] [iqdb] [saucenao] [google]
572869

>> No.572870
File: 1.10 MB, 1920x1080, PSOGL2_032.png [View same] [iqdb] [saucenao] [google]
572870

We had an amazing low poly thread on /vr/
https://desuarchive.org/vr/thread/4061145/

>>572857
What I find hard isn't the modeling, and not even the texturing, but the UV unwrapping.

>> No.572871

>>572870
Oh man you mean in comparison to regular models? I was actually thinking of finally learning UV unwrapping with this kind of stuff because I assumed it would be simpler.

>> No.572874
File: 28 KB, 277x128, tomaash.png [View same] [iqdb] [saucenao] [google]
572874

>>572871
Most indie trash developers and amateur modelers just unwrap as usual, texture it in high resolution then shrink the textures, but this isn't how it was done in the past. Most textures were painted in low resolution to keep details sharp. Some were even drawn in pixel art.
Meanwhile, you need to be careful with the UV isles sizes to compensate for the small texture size, the low geometry and the low resolution and make it all look consistent. Areas like faces get bigger isles.
But which techniques use? How to conciliate texture distortions in a 128x128 texture map for a 500 poly model? Everything needs to be tweaked by hand.

It doesn't look that hard. Until you try it.

>> No.572880
File: 292 KB, 1788x1069, vagrant story.png [View same] [iqdb] [saucenao] [google]
572880

Lowpoly this motherfucker!

>> No.572931
File: 9 KB, 443x422, fbl2yp.jpg [View same] [iqdb] [saucenao] [google]
572931

>> No.573611

>>572713
just because it has flat shading and vertex painting doesn't mean that the poly count is any lower anon

>> No.573617
File: 202 KB, 598x842, thing.jpg [View same] [iqdb] [saucenao] [google]
573617

>>572863

>> No.573635
File: 96 KB, 616x652, Bahamut_ff7.png [View same] [iqdb] [saucenao] [google]
573635

>>573611
Can that model be rendered on a PS1? Nope, here's what an actual low poly dragon looks like nigga.

>> No.573640

>>573635
honestly does that model even have that many less tris than the other dragon? the "memepoly" dragon has a couple useless edge loops but otherwise id say its low enough

>> No.573664
File: 243 KB, 905x562, taria_model_by_eelgod-d7m23eb.jpg [View same] [iqdb] [saucenao] [google]
573664

>>573640
Depends on the game and limitations of the system you're trying to replicate. If you're trying to aim for a lowpoly style you have a pretty strict budget to work with if you want to capture the integrity as well as aesthetic of low poly.

>> No.575350
File: 42 KB, 400x293, doit.jpg [View same] [iqdb] [saucenao] [google]
575350

>>572931
Awesome. I'm having trouble getting hips and shoulders done on all my lo poly shit. If you guys have tutorials or experience, I'd love to hear your takes on dat shit.

>> No.575473

>>572787
how the hell are these textures made?

>> No.575477

>>575473
Pixel art
The key is in the texel density distribution. You make the face and other high detail areas take up a lot of the UV while less detail intensive areas get small

>> No.575487

What programs do you guys use for modeling and texturing?

>> No.575495

>>575487
maya and photoshop

>> No.575517
File: 927 KB, 1336x798, im10-2.png [View same] [iqdb] [saucenao] [google]
575517

>>575487
CLIP PAINT STUDIO , blender
this is semi low poly too, for webgl(slow realtime render) presentation

>> No.575530
File: 16 KB, 326x326, 1501474170451.jpg [View same] [iqdb] [saucenao] [google]
575530

>>575517
>this is semi low poly

>> No.575610

>>575517
why do you keep posting this shit everywhere, this is a cluttered unappealing mess

>> No.576168
File: 406 KB, 1906x1033, file.png [View same] [iqdb] [saucenao] [google]
576168

>>572791
>>572792
>>572793
>>etc
I've been trying to rip models from DS games myself but my results are extremely hit and miss. For instance, I was able to get through Bravely Default's just fine, but Animal Crossing and Eternal Oasis I absolutely cannot find the NPC models for after decryption.

do you know of anywhere that I can just download low poly models from these fucking games (e.g. animal crossing)

>> No.576208

>>576168
https://www.models-resource.com/3ds/animalcrossingnewleaf/

>> No.576214

>>576208
thanks m8

>> No.576265

>>572720
>implying everything above your comment isn't low poly

>> No.576678
File: 125 KB, 1286x770, corrupted miniknight.png [View same] [iqdb] [saucenao] [google]
576678

I'm currently working this corrupted knight
my low poly is pretty weak though

>> No.576681

Daily reminder that simple model rips aren't enough

Early 3d consoles did graphics very differently from modern day consoles and pcs, and most people designed their models with these limitations in mind

>> No.576966

>>576681
What sort of limitations?

>> No.576970

Not OP here. Do you guys have any good tutorials/tips on how to make textures like in
>>572340
or those dragon ball meshes?

>> No.578107

>>576966
First off, must counsels outputted at very low resolutions, pixelating/blurring everything

The ps1 spyro games would swap out models with lower poly variants when they were far enough away from the camera

On an emulator that renders everything at your computer's native resolution, this is really obvious, but on actual hardware, it's way too pixelated for you to really be able to tell

Second, consoles of that era had some really funky texturing

The n64 had really crappy bilinear filtering that used three samples instead of four, the playstation didn't render textures in perspective, instead skewing them to the shape of the polygon, and the sega saturn (lol) couldn't do transparency

>> No.578117

>>576678
I would have gone with a large amount of tiny tentacles spewing out of the helmet like a beard.
That way you don't need to animate a tentacle.

>> No.578147

Anyone here experienced in lowpoly environment?

How do I make a modular low poly dungeon? How many polys per mesh? What the texture resolution should be? Do I include normal maps and PBR related maps?

>> No.578167

>>578147
First, do you mean lowpoly or stylized?
Because stuff like WoW, League of Legends, does not really count as lowpoly anymore.

>> No.578204

>>578167
I mean lowpoly. I don't think my other questions correlate with stylized.

>> No.578221

Any tricks for managing low poly deformations?

https://www.youtube.com/watch?v=ON3gsB5AxII

>> No.578226
File: 44 KB, 725x503, 1324401266954.gif [View same] [iqdb] [saucenao] [google]
578226

>>578221

>> No.578228

>>578226
Shorten the inner faces as the animation goes along?

>> No.578234

>>576966

Old consoles you have to limit polycount to keep frame rate high. The more poly the slower the rendering the lower the fps. A ps1 had 1 to 2k polygons on screen on average. They also had to fit the whole thing on 2mb of vram. So there you go. Make a scene that's less than 2mb and has no more than 2k polygons that includes textures for models sprites. And make it good enough to look good on old TV resolution.

Also this is very limited generalization. You'd have to dig up a ps1 Dev kit and hardware to get a good feel for developing art for it.

>> No.578277

>>578234
>You'll have to dig up a PS1 Dev Kit
Got you covered, Anon.
http://ffhacktics.com/wiki/PSX_SDK

>> No.578319

>>578204
Yeah, fair enough.

You're asking technical questions with an artistic goal. There's no target polycount because your polycount will depend on the size, complexity of your meshes. How you use your polys matters a lot more than how many you use - just look at low poly environment art you like and take notice of how they use their geometry.
The same applies for textures, resolution will vary a lot though you could always UV with a pixel grid to see the size of your pixels, since pixel size is probably something you wanna hit a certain spot for, rather than minimize as much as possible like in modern texturing.

The nicest lowpoly art I've seen uses diffuse maps only, you can try to include normals and PBR maps but they're probably gonna look like ass with that style.

>> No.578356

>>578319
ok thx, anon.

>> No.578823

>>578226
This technique is also great when making wrinkles in clothing. In blender just use alt+S to scale along the normals on the medial edge to create a convincing wrinkle, then UV your shades accordingly for a nifty cel shaded effect.

>> No.578830

>>572332
This pic could have been a 10/10 satire (from the thumbnail I thought it was) if it was just a plain wireframe.

>> No.579000

how do i git gud at low poly texturing

>> No.579029
File: 18 KB, 589x97, Capture.png [View same] [iqdb] [saucenao] [google]
579029

low poly you say?

>> No.580735

I'd like to learn about hip and shoulder deformation on low poly models. Does anyone have any good pics or guides?

>> No.580818
File: 65 KB, 917x705, ant_bebe.png [View same] [iqdb] [saucenao] [google]
580818

>>578226
I sure could have used this info 5 days ago, thanks though, I'll save this for sure.

BTW fellow anons, making a low poly ant. I can't seem to avoid triangles in the tessellation. Is this fine? Is there a better way I could do something like this?

I want to have a shitload of these in a game at once. I'll have to play around with it but I'm hoping 612 tri isn't too much for it.

>> No.580819

>>580818
all game engines convert geometry to triangles for rendering. keeping it at quads is good for edge flow and easier modelling. There is nothing wrong with triangles if it doesn't fuck up your normals, deformation.

>> No.580828

>>580819
so you're basically saying the only reason to keep things in quads is to make modelling easier and keep animations smoother? That's honestly pretty reassuring, I was always worried some engine would fuck up try to do something like insert quads into my tris to convert into more tris.

Maya's crashed so many times I'm starting to give up hope in computers.

I guess I got memed on pretty hard by people shitposting about NO TRIS shit.

>> No.580829

>>580828
it's not shitposting. Only use tris if you have to, but there's nothing actually incorrect about using them. Best practice is to always keep quads if you can.
>maya crashes
welcome to the club. If you haven't learned to ctrl+s after every action you soon will.

>> No.580831

>>580818
What, you can't add the support loops in now?

>> No.580837

>>580831
>support loops
edge loops you mean? I could but I dont see any better ways to lower tri count

>> No.581323
File: 361 KB, 1920x1080, volcano0001.png [View same] [iqdb] [saucenao] [google]
581323

beginner here, i suck :/

>> No.581703

>>580818
This looks really bad and wasteful. You should take a look on some Playstation models.

>> No.581758

>>581323
this is not low poly, it's faux-poly

>> No.581763

>low poly modeling is super fun and i love it
>hate unwrapping
>be absolute shit in texturing
>don't even know how to rig stuff
fuck me

>> No.581825

>>575610
He's excited about what he's doing, don't be rude.

>> No.581826

>>575517

>59k tris
>as many polygons as a hero character mesh in a modern AAA videogame
>semi lowpoly

>> No.581832

Is a human mesh with 512 polygons low poly? Or should I aim for 256?

>> No.581835

>>581832
polys mean nothing. How many TRIS?

>> No.581898

>>581835
shit dude how do i find out?
Cinema 4D -> Object Information only lists polys and points

>> No.581902

>>581832
Depends on which platform, generation and game type you base your standards. I don't know jack about low poly but you should try to look for the polycounts of characters from known games (PS1 era like Metal Gear Solid).

>>581898
Triangulate your model and look at the number again?

>> No.581962
File: 132 KB, 749x544, Screen Shot 2017-09-12 at 23.03.38.png [View same] [iqdb] [saucenao] [google]
581962

>>581902
>Triangulate your model and look at the number again?
ok so left: 530 triangles, right: 290 triangles
both are still WIP

>> No.581978

>>581962

>beeg lowpoly teetees

my dude!

>> No.582007
File: 159 KB, 1167x850, attachme1nt.jpg [View same] [iqdb] [saucenao] [google]
582007

Is there anywhere a topology guide like the left face but even more lowpoly and has side views too? Because most stuff like this is already triangulated or lacking in side views

>> No.582021
File: 43 KB, 640x448, 424_2001-11-12screen6_large.jpg [View same] [iqdb] [saucenao] [google]
582021

Is there a term for early 00s realtime visuals? The sort that aren't quite classic low poly but don't use bump/normal maps or anything newer than that and still stick to only using the bare minimum polygons required to make stuff look decent.

>> No.582027

>>581978
thanks m8
i always start doing normal bodies but always end up with exaggerated THIQQ models

>> No.582070

>>582021

I mean, its still technically lowpoly by todays standards. Early PS2 era graphics I guess? I remember those looking better than PS1 yet still markedly worse than something near the end or even middle of the systems lifetime

>> No.582118

>>582007
By the point you start putting edgeloops on a mesh you left low poly territory, best advice is to go look at ripped game models and study the topology.

https://www.models-resource.com/

>> No.582178
File: 53 KB, 256x256, HIGH DEFINITION 1080P THINKING.png [View same] [iqdb] [saucenao] [google]
582178

>>582070
>its still technically lowpoly by todays standards
>>582118
>By the point you start putting edgeloops on a mesh you left low poly territory

Who's most right, then?

>> No.582375

>>582021
>bare minimum polygons required to make stuff look decent
This is the key to low poly. Make a model that looks like something and do it with as few polygons as you can manage with the style you're going for.
Most of the detail is in the textures.

>> No.582400

>>582375
What's the limit? Is something like the models UT2k4 shipped with applicable now?

I think lowpoly's a bit of a busted definition if it's going to be pushed beyond really early 3D. It's worthwhile making a distinction between the workflow that involves traditional modeling/diffuse texturing and post-normalmapping/sculpting workflows since there's major differences between the two and having a name for it would definitely be useful but it sort of has to stop being lowpoly at some point. It's really hard to consider something like Half-Life 2 low poly, for example, despite the workflow being so radically different to today's realtime 3D.

>> No.582466

>>582400
The problem is the poly count needed for a low poly model is completely dependent on the object being made and the style being used. So there can't really be some number limit to define low poly.
A blade of grass with 200 polys would be considered high poly. But a human with 200 polys would be low poly. Trying to make something realistic vs making it highly stylized can also affect how many polys need to be used to get the desired model.
Half life 2 isn't low poly because of how it's modeled or textured. It's not low poly because the models use more polys than they need too to be recognizable. Those models could still lose several polys and be recognizable.

>> No.582471
File: 998 KB, 1891x1887, Props.png [View same] [iqdb] [saucenao] [google]
582471

Rate mine

>> No.582473

>>582471
8/10

>> No.582481

>>582471
comfy / 10

>> No.582483

>>582466
I'm not trying to start a debate on whether or not Half-Life 2 is low poly, just saying that there's a lot of artstyles and modeling methods from that era that sit somewhere between low-poly and modern realtime that share more in common with low poly (rendering methods & workflows) than modern graphics since they're essentially the same methods extended to a higher polycount. That's the term/classification I'm trying to figure out.
Also, PS2 era graphics are 100% using polygons that aren't necessary for the style to be "recognizable", extra polygons are present in these games for the sake of fidelity. Like I said, where's the line drawn on what can and can't be claimed to be a necessary polygon? If it's any polygon that is placed deliberately to have a noticeable effect on the shape/deformation of the model then suddenly obviously not low-poly stuff like Half-Life 2 becomes applicable. If it isn't, then you can safely drop the entirety of the PS2 library off the "low poly" classification since they're all deliberately adding polygons for fidelity. That's why I think it's busted to apply to the term to styles that aren't, at least in spirit, trying for *really* early 3D.

>> No.582484

>>582471
Not sure if the small, cylindrical details needed that many verts. But pretty good.

>> No.582486

>>582471
EXPAND DONG

>> No.582868

>>572340
Possible to do this stuff in C4D? This is one of my favorite things I've seen on here.

>> No.582870

>>582868
This is just box modelling. If your program can place vertices, make boxes and planes, extrude, and uv map, then you can make things like this.

>> No.582872

>>582870
Where do you even start with things like this?

>> No.582873

I hope that this is not too out of place to ask, but I am trying to understand topology more since I am new to modeling. I have heard that it's imperative to keep quads, but I see in these models some triangles instead. When would it be best to use triangles? Topology is hard to wrap my head around.

>> No.582876

>>582872
You start with appropriate primitives, which are basic shapes like cylinders and cubes and spheres.

We can see some basic shapes in the model right here: The torso is basically a cylinder with maybe 12 sides, the legs are cylinders with maybe 8 sides, the head is a cylinder with maybe 8 sides.

So for the leg you'd take a cylinder and, by this model's topology, add three loop cuts around the knee. Then you would pull the back of the knee in a little. Then some more edge loops add to the bottom of the legs so you can pull it around a bit for where the fabric bunches up at his shoes.

For the arm it's the same deal essentially, except without the fabric bunching up at the end.

Now you may have noticed on the arm that you only see two loops. Loop closer and you'll see that there's a triangle on the back where the third loop was. This is so that when the arm bends there's still a sharp point, and the edges of that center loop were removed from the inside of the arm so that when the arm bends there's one single flat plane. This was also done on the knees.

With the torso you add edge loops to pull in or drag out the shape to make the waist, hips, chest, and back.

From there it's lining the parts together and cutting in holes for them to fit into, which you can see screenshots of in the later link.

Look up character modelling / character box modelling. They'll typically be intended for subdivision modelling realistic figures but the principles for the base mesh are the same.

https://cgi.tutsplus.com/articles/game-character-creation-series-kila-chapter-1-high-resolution-modeling--cg-24776 This one looks nice.

>> No.582879

>>582873
Quads are ideal in modelling only for subdivision, which low poly doesn't use. The catmull-clark smoothing is better at following edges when it's quads.

It doesn't matter for low poly. Use triangles all you want if it helps you create the shape, all that matters is that the model can still deform properly when it animates, which won't be too difficult with low poly since it's not going to look realistic.

>> No.582880

>>582879
Oh, I see! So, quads are ideal for models that are higher poly. Thank you very much for answering my question. I'll continue to practice and try to understand more.

>> No.582906

>>576168
THICCpoly

>> No.582907

>>582880
You can also model in quads and collapse vertexes to optimize the low poly mesh.

Also polycount has taught a great deal of game artists over years, it was and still is a great resource. Specially the forums.
http://wiki.polycount.com/wiki/Polycount

>> No.583255

>>572356
There any more of these?

>> No.583298

>>578107
>The ps1 spyro games would swap out models with lower poly variants when they were far enough away from the camera
You mean LoD? The thing that everyone uses?

Anyway
>this thread
>low poly
Am I too old or something?

>> No.583368

>>583298
>You mean LoD? The thing that everyone uses?
PS1 Spyro games were one of the first games to use LODs. It's why the PS1 Spyro games actually looked pretty good compared to a lot of other PS1 games.

>> No.583690

>>583368
eh that's pretty basic 3d optimization for games.
Spyro games looked great cause they exploited vertex coloring to push the ps1 rendering capabilities. As in vertex colors are cheap and dont take space like textured do.

>> No.583699
File: 615 KB, 3200x2400, bOmijwI.jpg [View same] [iqdb] [saucenao] [google]
583699

>> No.583700

>>583368
>PS1 Spyro games were one of the first games to use LODs.
Virtua Fighter was the first to use LOD, way before Spyro.

>> No.583702

>>583699
if there was ever a series that needed a remake or mmo. fuck

>> No.583715

>>583700
That's why I said one of the first, not the very first.

>> No.583733

>>583715
Spyro was released in 1998, Virtua Fighter in 1993. Most 3D games had LOD before Spyro, so dozens of games.

>> No.583740

Is texturing and coloring shit hard? What is the workflow from design, texture, model?

>> No.586156

>>572340
He reminds me of Con Carne from Grim & Evil. That and he looks like he belongs in a TimeSplitters game. Very good.

>> No.586318

>>580818
Take a look at Global Defense Force on the Ps2 for good examples of how to make low quality ants that can take up the entire screen.
If you can make the framerate chug due to how many ants there are you've done good.

>> No.586325

Reposting from another thread, some genuine retro 3D tutorials I've saved.

https://mega.nz/#!VpVjgShL!iYF1U-NMGaRxZKDaQx4fXkHjlwkEE0_aWwimGSa98ks

And Paul Steed's book http://36.82.106.167:8484/bahanajar/download/ebooks_komputer/Modeling%20a%20Character%20in%203DS%20Max%20-%20fly.pdf

Paul Steed is the Quake 1/2/3 3D artist.

If you're down for a challenge then try to find Quake modelling tutorials and sift through broken websites and barely functioning Archive.org backups until you get some real information.

>> No.586340

>>586325

Pal, you've got a pass to heaven.

>> No.586367

>>578226

So basically put elbow pads with straps on all joints

>> No.586377
File: 1.90 MB, 540x540, tree-stump.gif [View same] [iqdb] [saucenao] [google]
586377

posted in other thread, but trying to git gud @ painting

>> No.586384

>>586377
Low poly doesn't mean no smoothing groups and the roots' ends shouldn't be squares but collapsed into triangles.

>> No.586466

>>586384

Is it okay if i use maya auto triangles or should i do it manually?

>> No.586476

>>586466
I think he means it should come to a point, not that it should be triangulated.

>> No.586513
File: 1.19 MB, 1920x1080, GeudBuey Animal Friends.jpg [View same] [iqdb] [saucenao] [google]
586513

The bird on the left, rabbits, chickens, and polar bear are not mine, everything else is

>> No.586583

>>586513
I'm not really a fan of high poly models that are flat shaded and then called low poly because you can see polygons.

>> No.586594

>>586513
This ain't low poly nigga.

>> No.586597

Why do you like low-poly so much, anons?

Hard mode: don't say it is "comfy".

I see stuff in WIP threads and almost everything is some stylized, low-poly game meme with handpainted textures. I'd like to see some photorealistic stuff for a change.

>> No.586616

>>586597

Because it makes them feel better about their shitty rigs.

>> No.586620

>>586597
From a gamedev perspective low poly is really the only way any 3D indie games can get done. Not many people have the resources for photorealistic game art. And it's just quicker to make low poly models. Also I just prefer stylized art over realistic art. Although stylized doesn't necessarily mean low poly, it just seems like a lot of people that make high poly models end up going for a more realistic style.

>> No.586622

>>586597
I'm already a 2D artist, meaning I already paint and already have a painting style. That painting style carries over best to low-spec (won't say low-poly because idgaf about polycounts, really) models. I can employ stylization and "cartoon" animation tricks to low-poly/painterly models without any of it looking out of place.
It's also more appropriate than realism for solo projects, since it generally takes less time to make. Next to just liking stylized low-poly as a visual style, I'd imagine this is the reason most people are using it. I could make a scene look like something from an AAA game or movie in reasonable time but making an entire game/short film like that as a solo effort would be a real pain in the ass.
Also I consider any time spent away from ZBrush's interface to be a blessing.

>> No.586636

>>586513
>memepoly

>> No.586642

>>586597
I've always enjoyed a more illustrative style in all mediums and lo-poly just seems more functional in the long run, especially since I consider myself an animator first and foremost.

>> No.586651
File: 436 KB, 1051x808, Claude_Monet,_Impression,_soleil_levant,_1872.jpg [View same] [iqdb] [saucenao] [google]
586651

>>586597
I would assume it's the same reason people like Impressionism. Sure you could paint a more realistic and detailed scene but realism is a dime a dozen. It's also much harder to distinguish yourself as an artist when your goal is to replicate rather than express. There's a certain skill and craft that comes with capturing the essence of something without simply replicating it and the stronger the artist can express this connection the more it resonates with the viewer. Also while I can't prove this I do think that the abstract nature of lowpoly stimulates the viewer's mind which is what makes it visually appealing.

>> No.587450

>>580818
Hey man, u can have the antennae and legs and even the jaws as separate things. Getting them out of the same geometry is just unorthodox

>> No.587451

>>582471
It's good man

>> No.587452

>>586513
>>586583
>harden edge
>call it low poly

just why

>> No.587454

>>572340
how do you get these textures? can anyone post a tutorial or share something on this matter?

>> No.587471

>>586513
Pick a style and be consistent please

>> No.587483

>>587452
>>587471
It was at least consistent, until the person I made it for wanted the main character to be "Smoother"

Worth noting several of the animals I modeled here are 500-600 tris. And the terrain? Come on. I'm proud of that terrain. But anyways, I now understand the zero tolerance policy in this thread and will leave in shame

>> No.587529

>>587454
By knowing how to paint and photomanipulate.
You've used Photoshop, right? The clothes are just a texture with effect layers + stuff drawn on top. It's hard to get perfect, but it's not *that* hard to do.

>> No.587537
File: 34 KB, 400x400, expand_dong.png [View same] [iqdb] [saucenao] [google]
587537

>>582471

>> No.587547

>>580818
There's nothing wrong with clipping through, you know. You don't need to connect the eyeball to the head in way, for instance.

>> No.587586

>>572344
This is excellent. I love the minimalistic texturing. Tell me, how did you start? How long did it take to get the basic model ready? How did you texture it, which are the source textures..? Do you have progress pics?

I work in 3d for my job and don't generally do anything at home but this made me want to model and texture something (that's not my job as well) and this style kind of makes my balls tingle.

>>572789
>>572791
>>572793
Every time I see this kind of characters it makes me want to do something.

Maybe doing some nice spaceships for shooter game? Technical looking, enough detail but still cutesy somehow. Bright clean textures but still having greebles and stuff.

>> No.587587

>>582471
Neat job. Two things I would have changed, but overall excellent work.
>bbq grid base can be substitutes with fewer planes and a grid texture
>bottom of the cell has two tris I would convert into a single quad

>> No.587643
File: 388 KB, 1500x1500, polybreno_1500.jpg [View same] [iqdb] [saucenao] [google]
587643

>>587483
The terrain is fine, I just get irrationally mad at high poly models that people call low poly just because it's flat shaded.
Because I really love actual low poly models, old PS1, Vita, and DS game models. There's something magical about them.

There's nothing wrong with high poly models, I just think they look real bad when they're flat shaded when they're meant to be smooth.

At least you made 3D art and not that god damn 2D vectorized photo art that people call low poly. God, I hate that shit more than anything. Pic related.

>> No.587732

>really want to be able to do sick mograph and 3d animation
>screw around with it off and on for a while
>eventually lose interest because I suck and it's complicated as fuck
>bunker down and start watching tuts again
>getting grasp on some shit
>tuts are so long and dry
>desire to create overwhelming
it's happening again, lads. too fucking intelligent to stick to anything long enough to become good.

>> No.587761

>>587732
You are not too intelligent you are too fucking lazy.
But that is ok, the best pleb-filter there is. Just revel in your laziness and never push to get better. You deserve it.

>> No.587765

>>587732
>too fucking intelligent to stick to anything long enough to become good.

what is this bullshit?

>> No.587788
File: 1.99 MB, 283x360, GreenRob2_FD_SS.gif [View same] [iqdb] [saucenao] [google]
587788

>> No.587789
File: 1.74 MB, 391x557, tumblr_or7dm83mGR1usc8qto1_400.gif [View same] [iqdb] [saucenao] [google]
587789

>>587788

>> No.587790
File: 1.10 MB, 391x456, tumblr_ormkkg1Zh01usc8qto1_400.gif [View same] [iqdb] [saucenao] [google]
587790

>>587789

>> No.587792
File: 1.62 MB, 391x372, tumblr_oqwclgVQ7r1usc8qto2_r1_400.gif [View same] [iqdb] [saucenao] [google]
587792

>>587790

>> No.587793
File: 919 KB, 391x345, tumblr_or0cktBvDJ1usc8qto1_400.gif [View same] [iqdb] [saucenao] [google]
587793

>>587792

>> No.587795
File: 749 KB, 606x550, Shotgun_Reload_FD_x2.gif [View same] [iqdb] [saucenao] [google]
587795

>>587793

>> No.587797
File: 1.40 MB, 311x360, Rob_Wh_Hair1.gif [View same] [iqdb] [saucenao] [google]
587797

>>587795

>> No.587798
File: 1.66 MB, 944x720, Rifle_NR1_FD_x2.gif [View same] [iqdb] [saucenao] [google]
587798

>>587797

>> No.587799
File: 1.56 MB, 420x384, OrangeKnight_FD_x2.gif [View same] [iqdb] [saucenao] [google]
587799

>>587798

>> No.587800
File: 23 KB, 288x281, GunTest_Back1.gif [View same] [iqdb] [saucenao] [google]
587800

>>587799

>> No.587801
File: 1.96 MB, 500x541, tumblr_oui7p9LBpC1usc8qto1_500.gif [View same] [iqdb] [saucenao] [google]
587801

>>587797

Damaged version

>> No.587802
File: 2.06 MB, 484x442, tumblr_oqcamb27vm1usc8qto2_500.gif [View same] [iqdb] [saucenao] [google]
587802

>>587801

>> No.587803
File: 1.28 MB, 391x462, tumblr_oqfzkkB8xc1usc8qto2_400.gif [View same] [iqdb] [saucenao] [google]
587803

>>587802

>> No.587804
File: 1.61 MB, 458x394, tumblr_oney31QQHt1usc8qto1_500.gif [View same] [iqdb] [saucenao] [google]
587804

>>587803

>> No.587805
File: 2.29 MB, 500x410, tumblr_onb7afuBJY1usc8qto2_r1_500.gif [View same] [iqdb] [saucenao] [google]
587805

>>587804

>> No.587806
File: 1.98 MB, 500x443, tumblr_ol56n6AaOr1usc8qto1_500.gif [View same] [iqdb] [saucenao] [google]
587806

>>587805

>> No.587807
File: 1.97 MB, 438x792, tumblr_oml36m3jEZ1usc8qto1_540.gif [View same] [iqdb] [saucenao] [google]
587807

>>587806

>> No.587808
File: 915 KB, 206x400, tumblr_olmkfc0ohF1usc8qto2_r1_250.gif [View same] [iqdb] [saucenao] [google]
587808

>>587807

>> No.587809
File: 1.56 MB, 422x624, tumblr_olejwpYwnG1usc8qto1_500.gif [View same] [iqdb] [saucenao] [google]
587809

>>587808

>> No.587810
File: 1.87 MB, 612x406, tumblr_olrg85zOmA1usc8qto1_1280.gif [View same] [iqdb] [saucenao] [google]
587810

>>587809

>> No.587811
File: 1.07 MB, 424x287, tumblr_oiii00ulJI1usc8qto6_r1_500.gif [View same] [iqdb] [saucenao] [google]
587811

>>587810

>> No.587812
File: 1.74 MB, 568x480, tumblr_ojg3eySDqT1usc8qto1_1280.gif [View same] [iqdb] [saucenao] [google]
587812

>>587811

>> No.587813
File: 1.65 MB, 446x628, LizardMan_Suit1_FD_x2.gif [View same] [iqdb] [saucenao] [google]
587813

>>587812

>> No.587816
File: 660 KB, 250x246, tumblr_ogido0P2iC1usc8qto1_250.gif [View same] [iqdb] [saucenao] [google]
587816

>>587813

>> No.587817
File: 378 KB, 250x190, tumblr_ogz2vsqhUg1usc8qto4_250.gif [View same] [iqdb] [saucenao] [google]
587817

>>587816

>> No.587818
File: 1.47 MB, 420x566, tumblr_ohsh46KdaK1usc8qto1_r1_500.gif [View same] [iqdb] [saucenao] [google]
587818

>>587817

>> No.587820
File: 1.74 MB, 256x252, tumblr_ogrpi3KGXZ1usc8qto1_400.gif [View same] [iqdb] [saucenao] [google]
587820

>>587818

>> No.587821

>>587788
Hey I remember you from /agdg/.
I've always enjoyed seeing your models.

>> No.587822
File: 318 KB, 250x287, tumblr_og2qriCx6O1usc8qto2_r1_250.gif [View same] [iqdb] [saucenao] [google]
587822

>>587820

>> No.587823
File: 392 KB, 500x482, tumblr_oh2l3rtPAu1usc8qto1_500.gif [View same] [iqdb] [saucenao] [google]
587823

>>587821
Thanks, Anon!

Sorry if I'm spamming too much, by the way. Just ended up having fun browsing through my old stuff.

>> No.587824
File: 514 KB, 267x266, tumblr_ofkm0oIaax1usc8qto1_400.gif [View same] [iqdb] [saucenao] [google]
587824

>>587823

>> No.587825
File: 1.31 MB, 918x576, tumblr_oltabfVQDe1usc8qto1_1280.gif [View same] [iqdb] [saucenao] [google]
587825

>>587824

>> No.587826
File: 984 KB, 250x247, tumblr_ofa6sufMi91usc8qto1_250.gif [View same] [iqdb] [saucenao] [google]
587826

>> No.587830

>>587823

Woah, this is amazing, have any tips to share about making lowpoly models?

>> No.587834
File: 577 KB, 194x185, tumblr_omfixy6Zld1usc8qto1_250.gif [View same] [iqdb] [saucenao] [google]
587834

>>587830
Thanks a lot, man!

I'd say it's 90% texturing, really.
I made a shitty video tutorial on pixel spriting which could be helpful:
https://www.youtube.com/watch?v=8L7QIXIsrcc

I also have a couple of short videos showing how you can UV unwrap on a premade texture map:

https://www.youtube.com/watch?v=6A-xmR7cIwA

https://www.youtube.com/watch?v=ZjVMD-nR6ws

I also have some writeups on my tumblr, but they're pretty far back, and I don't have time to look them up right now.
You can see if you find them here, if you want:
theonian.tumblr.com

>> No.587843

>>587834

You're magic, hope the best.

>> No.587844
File: 2.75 MB, 245x263, 1506894789857.gif [View same] [iqdb] [saucenao] [google]
587844

>>587843
Thanks, me too... I have still yet to make any actual video game outside shitty jam entries.

>> No.587854

>>587825
( _( _( _( ´०w०`)

>> No.587860

>>587826
damn that ship if good.

>> No.587861

>>587844
Weren't you modelling for an fps 3ds hunters game?

>> No.587898
File: 1.10 MB, 1429x951, CityBlock1_WIP.png [View same] [iqdb] [saucenao] [google]
587898

>>587861
Yeah, but the programmer gave up...

>> No.587906

>>587898
Weren't you modeling for a Spyro like game with a griffin?

>> No.587907
File: 1.19 MB, 1280x802, tumblr_oiii00ulJI1usc8qto3_r2_1280.png [View same] [iqdb] [saucenao] [google]
587907

>>587906
Yup. That too was abandoned. Weehaw

>> No.587908

>>587854
Haha, wow

>>587860
Thanks!

>> No.587909

>>587898
>>587907
What happened to your game dude?? The 2d one. I remember seeing your progress last year

>> No.587910
File: 1.29 MB, 185x132, GameT9_S.gif [View same] [iqdb] [saucenao] [google]
587910

>>587909
Haha, yes, let's just list all my failed projects

I really should have pulled my shit together and learned some programming by now, so that i don't have to rely on other people to make use of my graphics, but I just keep pushing it away...

>> No.587911

>>587910
You know, GZDoom is fully GPL now. You could make a game using an updated Doom engine and sell it with no problem, plus it's easy to program Doom / Hexen / Duke Nukem esque games with a community that would love to help someone that can actually make their own graphics.

I wouldn't use it with (many) 3D models though, kinda chugs with it what with it not really being made for 3D models. For that there should be a GPL Quake sourceport you can sell games through, pretty sure that's what DUSK is doing, but I don't know how useful a community exists for that.

>> No.587912

>>587911
DUSK is unity with some sort of .bsp support added in.

>> No.587913

>>587911
>>587912
Also, Unity/Unreal are probably just as easy as G/ZDoom at this point if you're already well versed in 3D. You can turn the stock blueprint FPS into something competent just by wiki surfing like you would with G/ZDoom. You'd have to really want the Doom gamefeel to opt for it over a modern engine.

>> No.587914
File: 1.77 MB, 210x170, MarioMap_Ninjapose_O.gif [View same] [iqdb] [saucenao] [google]
587914

>>587911
>>587912
>>587913
Thanks for the advice. Might have a look at GZDoom. Have already considered Unity and Unreal for some time, but I've never taken the plunge.

Recently I've been toying around with SM64 ROMhacking, which is surprisingly easy (for basic alterations and level importing).

>> No.587916

>>587912
Oh, that's fucked up. I thought it was DarkPlaces.

As long as it runs good and plays better tho

>> No.587929
File: 258 KB, 1382x786, doomm.jpg [View same] [iqdb] [saucenao] [google]
587929

>>587914
GZDoom is really only worthwhile if you want to make a game exactly like Doom or exactly like a Doom mod. It chugs trying to render 3D models and has poor support for them so you'd need to render them to sprites most of the time, and it uses a technically 2.5D level format that severely restricts the sort of architecture you can get away with. It's not really a suitable engine for your everyday idea for an indie game, unless your idea for an indie game is an actual, literal Doom clone. Anything else and you're inevitably going to have to cut back your design to suit the limits of the engine.
Just so you get an idea of what you'll be working with, this is what a GZDoom level looks like. It's a bit like a floor plan or a planar view from any other 3D software, right? This is the only level information you can actually modify. This flat plane. Everything to do with level geometry can only be defined by its boundaries on this plane and its floor and ceiling height. If you do slopes or floor-over-a-floor, it has to use this information to do it, meaning that any floating or over-hanging geometry is even more restricted and has to be built using what amounts to engine hacks referencing "Sectors" placed outside of the level boundaries. Going with this engine means resigning to a "look" that involves walls that always go straight up and almost always attach to the floor/ceiling at a 90 degree angle.

>> No.587931
File: 959 KB, 1920x1080, Screenshot_Doom_20151213_153725.png [View same] [iqdb] [saucenao] [google]
587931

>>587929
Yeah, adding slopes, stacked sectors, portals, and really detailed areas isn't something you immediately dive into.

Well, 3D experience would probably help with detailed maps. That and copy and pasting.

>> No.587934
File: 1.46 MB, 1928x1048, poptart.png [View same] [iqdb] [saucenao] [google]
587934

>>587931
Check out this neat trick. This room has a floor in it and the floor is also rotated. None of the surfaces on this .bsp object can exist in Doom geometry. The engine dies if you try to slope a 3D reference sector two ways. You could import it as a model but you know how those perform and the collisions can only be represented as boxes.

>> No.587954

>>586597
I'm just interested in the solutions people come up with to make low poly figures look good.

>> No.588008
File: 167 KB, 1280x1024, evil twin.jpg [View same] [iqdb] [saucenao] [google]
588008

>>587812
>>587811
>>587808
>>587806

I just remembered what your stuff reminded me of. Evil Twin for the Dreamcast and PC. It's got that same grungy look.

>> No.588074

>>588008
Oh, that looks really cool! Never heard of it before!

>> No.588075

>low poly thread
>pretty much everything is low res
Does /3/ not understand the difference?

This is technically low-poly:

https://sketchfab.com/models/4e04e763221246288d21ed2e920e8633

>> No.588077

>>588075
>low poly thread
>pretty much everything is low res

>>572332
>To kick this off:
>-I'm looking for good examples of low res/low poly or "pixel art on 3D' type models.

>> No.588078

>>588075
You should probably end your life, little autismo

>> No.588086

>>588075
Poly count is 3d resolution so low poly is low res you idiot

>> No.588143

>>587844
It must have hurt pretty badly to smash his face right into the wet grass. I wonder if Fitz wore something like a blanket as a mask.

>> No.588149

>>588075
>Lowpoly
>17800 polygons
fucking idiot

>> No.588155

>>588149
Lowpoly is a relative term. On modern hardware, 17k can be considered lowpoly. But no one really uses that as the definition for lowpoly except for very smart posters that want to act superior on anonymous boards. I would consider those models to be "game models" or "medium poly".

Most people consider lowpoly to be models that use as few polygons as necessary to get the shape and style they want.

>> No.588214

>>588155
Our production team just uses the term game poly, or production ready models since it's a relative term that changes as technology advances. Lowpoly should have a definitive meaning in order to avoid confusion in cases such as this.

>> No.588228

>>588214
Yeah, this. Especially since you're using the exact same process to bake a current-gen model down to game ready polycounts regardless of your polygon budget, whereas the low poly being discussed in this thread has a radically different workflow. You know, something that defines it as different from an average game model. It's not a relative term because there's no real use for it if you make it a relative term.

>> No.588610

>>572340
I loved this game

>> No.588697
File: 67 KB, 544x470, sr suino arcade.png [View same] [iqdb] [saucenao] [google]
588697

>>587818
Your pigman vs my pigman, who would win?

My texture is a preliminary. I'm going for a Die Hard Arcade look (and that's pretty ugly).

I have been following your work for some time and you're really talented. Shame that the programmer gave up on the FPS game. I like your grungy, grimy style.

>> No.588750
File: 151 KB, 917x888, copy.jpg [View same] [iqdb] [saucenao] [google]
588750

I made this when I was 18 I think. Someone paid me $50 for it. I was so happy, it was my first job. 2000 triangles. A lot of animations.

>> No.588751

>>588750
Oh right, the guy showed me a concept art someone else made. It was a very professional picture but I didn't save it.

>> No.588754

>>588750
512x256 texture. It was a custom model for good old warcraft 3.

>> No.588886

>>578228
I think the extra 8 polygons would end up being less of a drag on the CPU than a vertex animation.

>> No.588888

Any tips on blocking out the shape without adding geometry?, I get the chest, the neck, the head and the legs but the arms and the hands become a pain.

>> No.589289

>>588888
Hands should pretty much just be a rectangle with a thumb maybe.

>> No.590209

what the fuck happened to shrapnelsoup??

>> No.590304
File: 478 KB, 960x540, Pico-Poly.png [View same] [iqdb] [saucenao] [google]
590304

First try at low-poly, as well as first try at modelling a human, and first try at rigging.

I wanted to have an army in the background of a picture I'm working on, so I tried to make the a model that consumed as few resources as possible.

Brutal criticism appreciated.

>> No.590307

>>590304
Kinda looks like N64/PS1 era model. Looks fine. Head could be a little more detailed if you want, instead of being a cube.
Also they're all in the exact same pose in the background, it should be more random.

>> No.590346

>>590304
That's not lowpoly. That's just lazy.
Take a look at the stuff posted ITT and try again.
Apply yourself.

>> No.591631
File: 64 KB, 960x540, untitled(1).png [View same] [iqdb] [saucenao] [google]
591631

Yay low poly

>> No.591632
File: 108 KB, 1122x777, f36c36177d2855d1e1f53639db13b66d.png [View same] [iqdb] [saucenao] [google]
591632

Started learning blender a week ago, this is as far as i can go without a tutorial. Have yet to do the hands and head. I'm thinking about doing it from scratch tho' because it's kinda shit.

>> No.591654
File: 86 KB, 1077x845, DGHEUIvW0AAVTo3.jpg large.jpg [View same] [iqdb] [saucenao] [google]
591654

pixel art + low poly is my favorite style.

>> No.591656

>>591632
Go through a good tutorial FFS!!! Why do people feel proud about not following and learning good practices and instead immediately want to figure out everything on their own? It will look like shit as long as you don't apply yourself and learn from a pro.

>> No.591694
File: 198 KB, 600x300, ConkersBadFurDay-3.png [View same] [iqdb] [saucenao] [google]
591694

>>590307
>Kinda looks like N64/
no.

>> No.591712

Are there good example of torso edge loop topology for low and medium poly models? I have been looking for some reference on that.

>> No.591730

>>572802
Nice bewbs

>> No.591737

Im looking for a specific low poly image i saw in a much older thread on /3/.

It was a low poly girl or woman, she was wearing a blue top and i think and black leggings and/or socks and was somewhat realistically proportioned
the thread also had a link to the creators deviantart and another image that showed a painting of the womans face
please help?

>> No.591741

>>591737
sorry, by thread i mean reply, the thread was a regular lowpoly thread

>> No.591747
File: 428 KB, 1012x682, mira_model_by_eelgod-d9fhsy9.jpg [View same] [iqdb] [saucenao] [google]
591747

>>591737
This?

>> No.591802
File: 55 KB, 1454x722, Capture4.png [View same] [iqdb] [saucenao] [google]
591802

luk at my low polie cuub

>> No.591805

>>591802
Hey that's a pretty nyc lighting! What renderer are you using?

>> No.591814
File: 63 KB, 702x720, goblendsomewhereelse.jpg [View same] [iqdb] [saucenao] [google]
591814

>>591802

>> No.591869
File: 109 KB, 800x680, 1437668146141.png [View same] [iqdb] [saucenao] [google]
591869

>>591747
Not that, but I did find it. Unfortunately I don't have any sauce on it.

>> No.591870

>>591869
>>/3/thread/483148

>> No.591876

Low poly is garbage and i wish it would die. It's the equivalent of painting with crayons. GJ you can do it, but it's still kiddie stuff and not very sophisticated.

>> No.591880
File: 224 KB, 1898x1002, ex.png [View same] [iqdb] [saucenao] [google]
591880

Here's mine. I've been hacking at it just today, I have a little experience with CGI. I am an above-average artist (the average of the average artistic ability across all humans, not across all artists). I started with a cube, and created rings and bevels and hammered out the head shape, some details accentuated for cartoonish purposes. i posted it earlier and, as a result, was reamed for my lack of skill. I took the criticism I got and cleaned up some polygons. I am currently in the process of redoing the ears.

I'm no artist but I like to contribute.

Sorry for bad English.

I'm not foreign or anything. Just a brainlet.

>> No.591882
File: 21 KB, 823x749, 3.png [View same] [iqdb] [saucenao] [google]
591882

same character, didn't realize facial features were missing.

Subtractions leading to eyes and mouth are a stylistic choice.

He's supposed to look afraid.

He doesn't want to exist.

>> No.591921

>>591876
if it's so trivial then why can't YOU do it?

>> No.591922

>>591921
What kind of argument is that? He didn't say that he can't do it, and no, criticizing something does not automatically mean that somebody is salty because he isn't good at it.

>> No.591923

>>591922
well i've never seen someone who was good at this claim it's easy. it's actually very hard to make this stuff look good. the only people who say it's easy have never tried it. i don't care if he likes the style or not but the actual claim he makes - that this is so easy that a child could do it - is moronic.

>> No.591937
File: 188 KB, 960x720, red tree complete.jpg [View same] [iqdb] [saucenao] [google]
591937

>>591876
Well, I guess this comes down to perspective. There's been plenty of oldie stuff posted in the thread that involved a brutal amount of forward thinking in regards to geometry count and UV layout. To even consider doing a full character model with less than something like 1000 faces, on maps that are even smaller than 512x512, you'd have to embrace the fact that you're going to hand-paint every single detail onto the color layer itself, so a decent amount of artistic skill is necessary in that regard.

Keep in mind most models were probably done on a schedule on top of having hardware constraints shoved on top of the 3D artists.

If anything, it should be much easier to do things without any sort of constraint in mind; no need to carefully consider where and how to place geometry when you can subdivide and model every detail in zBrush. No need to know anything about painting specific details by hand when you can just bake every map under the sun, slap it on your model and let the computer do the rest. Honestly, even painting with crayons at that point sounds like more of a challenge.

It's perfectly legitimate to not enjoy the low-poly-ish art style, but to say it's kiddie stuff and not very sophisticated is very short-sighted.

>> No.591941

>>591937
To be honest, some things like you mentioned are easier, but the challenges just shifted to something else and standards keep increasing on top of it.

Not that guy, but I also personally don't really like low-poly. I've seen some nice stuff, but I still prefer the advanced things that push the boundaries of 3DCG. Low poly happened just because of the inferior technology at the time anyway, didn't it? I get it that people can like the aesthetic of it (probably partly from nostalgia), but now that we have surpassed the limitations of technology, I don't see much point in it.

>> No.591946

>>591941
>I get it that people can like the aesthetic of it (probably partly from nostalgia), but now that we have surpassed the limitations of technology, I don't see much point in it.

whenever people say stuff like this i feel obliged to remind them that the second best-selling game in history (after tetris) is minecraft, a low-poly game played primarily by kids. you can't tell me millions of children who are younger than call of duty are just nostalgic for quake 1 or whatever. minecraft isn't even very good low-poly but the kids don't care, nor do they have any idea about the history of computer graphics or how minecraft relates to it. for them it's just one way a game can look. if they were articulate enough they would tell you that it's just a style and that it's appropriate for the task and that not seeing individual pores on the square pig is not something they would ever consider a problem.

see, it's actually your perspective that's obsolete, not low-poly. you lived in a period of rapid development of graphics technology so you can't think about this stuff in any way other than as a struggle to "surpass limitations" but that's just a rapidly disappearing historical aberration. subsequent generations do not and will not care about the technological origins of these art styles. they'll just play a game on its own terms without needing to relate it to some quest to create the holodeck or whatever.

>> No.591950 [DELETED] 

>>591946
I'm not talking about games, but 3D as an art itself. Of course it doesn't matter in Minecraft, where it's not the center of the attention. What do opinions of millions of children who don't care and "best-selling" status of some game have to do with 3D art? Are you looking at 3D exclusively through the prism of vidya?

>> No.591953
File: 117 KB, 1200x720, PokemonSunMoonAmazonJapan4.jpg [View same] [iqdb] [saucenao] [google]
591953

>>591941
Whether you make a 30k or 1k model nowadays does come down to personal preference, except in mobile markets where 3D still has constraints, and you have to create models that have to run well in a staggering gamut of phones, both crappy and godly. Games like the Etrian Odyssey series and Pokemon also still make very good use of this due to 3DS hardware constraints.

Yeah, the standards are changing, but the practice of only using as many polys and maps as you absolutely need to craft something in a certain art style, is certainly not pointless yet, and as standards change, it probably never will be, because it'll evolve together with the "high ceiling" of what we can do with this technology as well.

>>591946
The massive popularity that stems from Minecraft doesn't come down to its voxel-based approach to graphics, it's the creative freedom that it gives players, to build whatever they want within the constraints of its rules.

Whatever art style Minecraft has is actually completely inconsequential to its success. As long as it had blocks and you could stack them together, Minecraft would be successful, though admittedly having its colorful art style did help it break into a younger crowd more easily.

>> No.591960

>>591950
what a strange post. when's the last time you saw cgi "by itself", as opposed to serving as a visual tool for a game, a movie, a painting? how can the primary method of communicating with the player "not matter" in a video game? how can the fact that a whole generation of children is growing up with a certain style of cgi not be immensely relevant to cgi going forward?

the children aren't failing to notice the graphics of minecraft. they see them, they understand them and they like them. they don't voice any barely-coherent complaints about "limitations" not being "surpassed" (limitations to what?), because they enjoy the game they're playing right now. the children are smarter than you.

>>591953
you're arguing against the reverse of my point. it's irrelevant WHY minecraft is absurdly successful, but it unquestionably is. this means every child on earth is exposed to ubiquitous imagery of blocky character models with pixelated textures. they play the game, they watch thousands of hours of youtubers playing it, they surround themselves with minecraft toys and books and candy and pajamas and all of it carefully recreates the blockiness and the exact pixel patterns of the game's assets. this means that low-poly has already firmly established itself as simply a popular style of artwork, independent from the technical limitations that spawned it, from nostalgia for the 90s, and possibly even from video games. it's done, it has already happened, it's not going away. you're only going to see more of it as these kids grow up.

it's like it's 1964, all the teenage girls in america are experiencing their first orgasms from just looking at the beatles, and you idiots are sitting there going "i think the guitar is done as an instrument. SO DONE."

>> No.591961

>>572764
edge loop not decimate my niqqa

>> No.591983

>>591960
You say this as if kids know or are even interested about the intricacies of Minecraft graphics. The dumbasses probably don't even know what a polygon is.

Little Timmy is interested purely in stacking a bunch of TNT together under a mountain and watching it blow up like a nuke. It's not pixel art or low-poly that picked up from the success of Minecraft, it's voxel-based sandbox games, and that ship has sailed and sunk already.

>> No.592041

>>591983
the fact that you apparently despise children is beside the point. the children are smarter than you.

>> No.592044

>>587471
THIS, EXACTLY

>>586513
This is really bad - it lacks any sense of artistic direction, sensibility, or skill. Lowpoly can be great, but this is not

>> No.592045

>>588075
correct, this is technically low poly
..but people itt seem more focused on low poly "aesthetics". nobody cares precising which they're talking about

>> No.592046

>>588214
sounds fair
"game poly" makes more sense than "low poly" nowadays, or we just need to constantly keep updating what "low" means in our mind as technology evolves

>> No.592047

>>591880
>>591882
just give up m8
this board sucks, but you're finding new lows

>> No.592054

>>592047
I can see it as a /3/ meme in a near future.

>> No.592061

>>592041
Okay.

>> No.592064

>>592061
no, seriously. your bitter criticism of children is that when they play a video game they want to blow up a mountain instead of counting polygons and complaining. the children get it, you don't. you've worked and worked to get to your present state of willful idiocy and now you're stupider than a child.

>> No.592097

>>592064
I respect your opinion on this.

>> No.592135
File: 1.45 MB, 1920x1080, zom.png [View same] [iqdb] [saucenao] [google]
592135

>> No.592161

Any resources on 1990-2005 lowpoly models tutorials for games such as half life or quake?

>> No.592465

Got this dumb idea that I might use Maya live surfaces and quad draw to make low-poly by mashing primitives/more basic unconnected modeled shapes together to make the base that I build my topology ontop of.

Does that sound like *too* dumb of an idea to work? An alternative would be using zbrush sculpts as the base.

>> No.592583

>>592465
Isn't that basically how all models are made? Either mashing lots of primitives together or making a sculpt. Then making a clean low poly model based on it.

>> No.592595
File: 98 KB, 997x521, vertexes.jpg [View same] [iqdb] [saucenao] [google]
592595

>>592583
I've always modified primitives and then bridged them together for poly modeling, never actually used retopo tools to get a shape outside of retopologizing high poly meshes
I went and tried it after posting and the results weren't great, but that could just have been because it's a first attempt. Main thing I'm looking to work around is getting stuff to follow specific curves consistently, and managing vertexes so that the shape doesn't become a mess.

My... Edgeflow, I guess you'd call it? gets ugly doing any character poly modeling that isn't subdiv modeling. I've generally got organized topology, but if I was doing something like a hand or anything that has a lot of vertexes following a specific curve like an arm or something, they'll come out messy because it's difficult to organize so many vertexes. I thought maybe I'd be able to get around it by using primitives as a guideline for how those vertexes get placed, but I think I'll be looking for another solution to manage it. Possibly just attempting low poly from a sculpt.

Here's an example from a (non-low-poly, but poly-modeled) model I worked on ages ago. From most angles, it's hard to see how this vertex is out of place. It's also hard to manage the amount of vertexes that could be messing with the form like this, since I'm managing a lot of vertexes and the angle I'd have to view them from to even see the issue is hard to work from. There's another vertex a bit closer than the one I've circled, that is concave on the hand mesh, which is even harder to spot and correct. I want to minimize the potential for this sort of thing happening, or work out better ways to deal with it when it does.

>> No.593557

>>591880
Are you suggesting that being artistic is essential to a human?

>> No.593559

>>591953
>Games like the Etrian Odyssey series and Pokemon also still make very good use of this due to 3DS hardware constraints.
Maybe, but not in the pic you posted. Afaik they specifically made the models for HD screens and then threw them in the 3DS games so that they can recycle them in the future. All of the main 3DS Pokémon games lag a lot because of it.