What's the quickest way from retard to creator of this?Wing3D?
>>1017490
>>1017491why? whats wrong with wings3d?
>>1017490Literally any 3d modeling program will do
>>1017494how did they do it back in the day? and is there anything from that which is still useful?
>>1017490not sure why you'd use wings over blender considering the latter has a bigger community and more tutorials out there, but it's your choiceI think I've seen one other game use this flat texturing method, can't remember what it was if you look at the model, they made it so all the faces are facing the front or back of the camera so there's minimal stretching at the sides. after that they used the Project From View unwrap method and then likely painted over the UVs in their texture editor of choice for something like the hammer which would be perpendicular to the camera they'd just Project From View at whatever side would have the most space, in this case the side the main thing you need is a good understanding of silhouette and the ability to texture paint here's a nice little piece on the PS1 / Quake-era aesthetic: https://www.tumblr.com/spellfist-3d/615902900826390528/guide-to-that-elusive-ps1-pixelated-lowpolybutyou can take a closer look at the Quake models and textures here:https://models.spriters-resource.com/ms_dos/quake/https://textures.spriters-resource.com/ms_dos/quake/if you want to get started with blender: https://www.youtube.com/playlist?list=PL3GeP3YLZn5hhfaGRSmRia0OwPPMfJu0Vhttps://www.youtube.com/playlist?list=PL3GeP3YLZn5gZhJhyIQPKoz9Yrs9oKU9Ralso check this thread out: >>992953
>>1017503>if you look at the model, they made it so all the faces are facing the front or back of the camera so there's minimal stretching at the sides.Unironically how do you plan this?Do you like try to have only a single edge going on the sides? Do you pose it in some fashion before projecting UVs?
>>1017505>have only a single edge going on the sideslooking at the models, it seems that way yeah in terms of posing I imagine they tried to pose it in a way that you can see the most faces / largest surface areain the knight texture you can see that the arms are turned out to the front so you can see the bicep / ticep area as well as the palms and back of the hand, rather than facing the side as they normally would when resting if you use segmented limbs unlike Quake then the posing will be even easier since you won't have to mess with the mesh itself, just rotate it as you want it projected to texture on
>>1017507another example with the shambler here, with the way its hands are spread out for the purpose of texturing
>>10174963d studio or alias (specifically for quake). In the 80s/early 90s devs just made their own simple modelers. Again, any 3d modeler will do
>>1017505If you look at the runes specifically you'll see if they had edges that wouldn't show on such a projection they just unwrapped them for that view.
>>1017511this texture shows that too, looks very odd
>>1017513god damn that is some freaky unwrapping but the results are kino
>>1017513>>1017508>>1017507>>1017503>>1017490Unironically the best unwrapping technique I have seen for 2d artists
>>1017503same poster, I gave this style a quick test, seems easy enough also if the character is mirrored like the knight or the shambler you could split the texture / UV in half for optimization I can't texture paint for shit though sadly. this method is definitely best suited for competent 2D artists, although I guess it could just as easily be used for other less realistic methods of texturing, it's very easy and straight-forward
>>1017526also for anyone interested in trying it out, some tips: use blender's built-in texture painting to crudely draw the landmarks on the model, then take it into something like photoshop to finish. it's easier than guessing how exactly the parts will line up at the seams and suchexport the UV layout to 2560x2560 or whatever fits nicely into a multiple of whatever your target res is, like 128x128 or w/e. it's just easier to paint in higher res and then lower it in photoshop (use bicubic sharper)also don't forget to index the texture to 256 colors. you can find the Quake palette online and index it to that if you want to be fully authentic to that style
>>1017513Basically at the time they didn't have an easily refreshable real time textured preview, so having the unwrap resemble the final model made it a lot easier to paint.
Where.. is his neck? kek
>>1017503>not sure why you'd use wings over blenderBecause he's a troll
>>1017530The blender or wings?
>>1017490Wings wha?Low poly models favor texturing more than ANYTHING. So you should start with being able to set up your texture sheet first. The pic you provided doesn't even have side textures, just front and back so you can see texture stretching on the hammer. There's a process deeper than the pic you provided too. That texture in picrel is the end process of building the model texture. Each piece of material was preplanned. The model is probably the least important aspect of low poly.
>>1017531If you told me that OP created a bait thread, replied to himself with wings3d, and then replied to himself again with blender... I'd believe it That's how bad the board has been lately
>>1017544i didntWhat about Milkshape 3D?
bumping this because other threads are shit
bump
>>101749640 + anon here.Played Q1 after installing it from 30+ diskettes downloading the demo on dail up from a college 100 miles away.Anyway, I used to edit the (I think BMP but it might of been another format) files using software called DPAINT. The texture was unwrapped so it was a but of a shit show but it worked.You can grab this shit on archive.org or abandonnia https://en.wikipedia.org/wiki/Deluxe_Painthttps://winworldpc.com/product/deluxepaint/2xback when windows wasn't for faggots
What I wanna know is how they made textures for games like Quake or Unreal.
>>1017871According to the devlogs for Quake it was Adrian Carmack and Kevin Cloud who where the texture artists.They painted everything by hand in Photoshop 2.5/3.0 running on SGI and Windows NT workstations.There isn't anything magic or exotic to it but they restricted themselves to a 256 color palettehandled thru a custom tool written by John Carmack that handled that as well as saving to Quake's .wad format.The colors chosen was a range they knew would help ask the texture seams.Over at Epic it is stated it was Shane Caudle who painted nearly everything for the original Unreal.He used 1996 Photostop 4.0 on a PC. He had custom tools that packed the textures into the .utx format and generated mipmaps.He stated in interviews he painted his textures at higher resolution and downscaled to the res used by the game.You can do anything they did back then better in standard photoshop of today. If you wanna be early Quake 'Photoshop 2.5 authentic' just don't use any layers as you didn't have those until 1994 and 3.0
>>1017877>'ask' wtf*hide the texture seams.
>>1017877>He stated in interviews he painted his textures at higher resolution and downscaled to the res used by the game.this feels like blatant cheating
>>1017879retard
>>1017880use your big boy words
>>1017879it's the smartest and easiest way to do it and likely always will be; painting at 128x128 or 256x256 resolutions is a challenge because you can't get a clear read on values and what it is you're actually painting
>>1017879You mean the most common practice in game development?
>>1017879>>1017885Both Quake and Doom are ancient PBR, they're not pixelart. Proper way to do lowres PBR textures is to do highres (or even infiniteres, if you do it in node-based system as a composition of noise functions, distance fields, etc) PBR textures and downscale / render at target resolution. It doesn't work in true pixelart because there individual pixels encode complex features in implicit/implied stylized ways, and rich PBR texture detail don't work in pixelart because they muddy the abstraction pixelart heavily relies on.
I don't use blender but I started using claude.ai to shit me out shaders for unreal and I imagine it works much the same way for blender, so heres a python script and some basic instructions, ask grok or chatgpt if you have problems stillhttps://jumpshare.com/s/fwcE769dyldxUUOBfwe5
https://youtu.be/kARj4ERXtQ8https://filebin.net/mt5769kqey26m4h8pirate substance painter and dl this (i bought it so you dont have to)
>>1020837Shit out is the right word for that garbage lazy piece of code. If you don't know the answer let someone else answer it knowledgeably instead of using AI trash
>>1020860well it would take 5 minutes to figure out like it took me when I started using it, it gives you the product of what you would otherwise spend days fumbling around cobbling together with youtube videostheres real answers already above but the keyword is easy
>>1017544At least wings3d was mentioned, it's a great minimal UI for focusing on making stuff, where the tools are hotkeyable, and is easy to configure, and save prefrences, editing blenders hotkeys is a nightmare because there's 8 modes of hotkeys worth Already defined and you gotta clean up all the ones overlapping ... Wings3d is simple allowing rapid use of the commands
>>1020840>This bin is no longer available.do you have another link please?
>>1020840pixel8r is really dogshit next to using pixatool or literally any other dedicated plettizer software out there. it consistently churns out the crustiest pixels I've ever seen.
>traaaans lowpoly retro sovl.... le 1996 modeling
>>1021828You will never make or do anything interesting, and that is comforting.
>>1021842>"interesting" is when you do a poor imitation of what actually interesting people did 30 years ago
>>1022176>"interesting" is when you're an annoying turd who spams gibberish every few days
>>1017879>He stated in interviews he painted his textures at higher resolution and downscaled to the res used by the game.>this feels like blatant cheatingvery old gdev here started in '98downsample images is literally the trick to get authentic looking early 3d game texturesit feels like cheating because it's the secret.back in the very old days gdevs had the best hardware so we could generally manage larger files than consumerswhen people would try and replicate using asset size instead of source size they could never get results close,some could get really good results like actual pixel artists but these are rare breeds.a lot of us back in the day would use photos as a starting point.those photos would be cut up or painted over to create the textures.we'd either take them ourselves if our company allowed itthey would also buy CD libraries of photos and photo textures and multiple companies would use them. kind of like asset storefronts nowadaysone downsample step was in this using photos as a starting point stepyou'd clip some part of a photo out and scale it to fit, then paint over it until you're done.a lot of times we'd downsample the final texture again to fit on hardware/how it looked on a CRT, if it looked the same we'd use the smaller texturesome guys were so good at taking photos and turning them into textures you'd think they were hand painted or actual pixel art from the startIdk if /3/ knows about ben but he's got a metric fuck ton of tutorials in the early '00 style site: http://www.poopinmymouth.com/#tutorialsyoutube: https://www.youtube.com/channel/UC5CEtTewnSFYw-sOZdm2D_gif anyone else has other resources like this, please link them for others
i came over this guy on twitter, creator in filename
>>1022203he painted a greyscale before coloring, wich i found interesting
>>1022204
>>10174905-10 years of digital painting knowledge for texturing and anatomy study. Modeling isn't the hard part, good textures are>>1022196Another "secret" is using correlated RGB noise (multiplying the values instead of purely additive) over the texture to add color variation. This effect is noticeable in some PS1 texture atlases
>>1022176As if the projects made by AAA studios aren't entirely based on pre existing properties and concepts that have been inbreeding with each other for the past couple of decades.
>>1022203>>1022204oh nice! it's called greybasing, grayscale base and then later hue shifting Create one grayscale texture, then color shift it for variations (rust, wood types, different metals)This would often save tons of memory and you could get 5-10 textures from one base>>1022206oh great tip>tiling micro details over unique macroblend a tiling detail texture (noise, grain) over unique base textures during compositing. Breaks up repetition and adds depth.we had a program that would take an input pattern a small texture with full black and white pixels similar to opacity mapswhere it would tile the input pattern texture over your then you could apply various texture effects like noise, grain, hue shifts and other stuff.it was really neat you could control where some effect would be placed and choose how it was applied, ie multiplied/additive etcit was called cutout painter or something like thatsome othjer good ones are Vertex lighting baked into texture corners. pre lightmap era, you paint gradients into texture corners that aligned with vertex colors for fake ambient occlusion. made flat textures pop.some games went with limited palettes which meant desaturating everything then you'd pushing it toward one hue. Not just quake brown, some games went green, blue-grey, even yellow, remember the yellow era? that makes inconsistent source photos more cohesive.a metric fuck ton of what we had to do back then was dealing with limitations and finding ways over them.
>>1021827But pixel8r lets you see your results on the mesh in real time, which is a huge advantage.
