News | Forum | People | FAQ | Links | Search | Register | Log in
Industrial Texture Pack
Now that I am finished with my Bridge Crane concept map I thought I would release the textures so all of you can go industrial nuts! I also released the PS 5.x source file, so if you want more stuff then you can create your own. The source file probably only works with the latest version of PS so don't moan at me if you can't load it!

Web page for texture packs:

The download files only have high resolution 1024x1024 textures and no Q3 shader file. I think by now most people understand how to create their own and will probably want to re-arrange the textures to suit their own projects anyway. If anyone does create a shader file and want to share, then post a link to this thread. I have posted on my website the size of the files, so don't be surprised if it takes a while to download them. I am sure my ISP is not going to be happy! :D

Here is some texture examples, more on my web page:

Screenshot of the Photoshop 5.x source file in use:
Sock you rock :) 
Awesome Work 
glad you released these! 
Awesome, I'll be making a Quake wad later. 
Hope I Did Not Screw Up (I will probably alter the readme later!)

Any suggestion how to best release the renamed full res files? Add a with just the 21 renamed files? Or leave it up to the mapper? 
They are 256 which as negke pointed out is too big, resizing to 128 now. 
The Zip Was Updated 
yikes, those blue and green ones did not respond well. :S
possible to run those through photoshop with some dithering maybe? (i would, but i don't have it atm, and gimp has less control over dithering). 
Yeah, this is a quick and dirty conversion just as placeholders to use with the high-res replacements. Would be ace if someone would make good looking mips from it. 
Q1 Wads 
I imagine the textures will not look great after 8x compression. It certainly would be better if they were reduced in PS. Let me get on the case. 
Q1 Scale

5.6Mb File, TGA format (all textures together)
Someone else will have to WAD them, I don't have the tools setup. 
Missed one of the textures, always good to double check stuff!

Same link, 4.96Mb Instead 
Misunderstanding! The problem is the conversion into the Quake palette. has some brainstorming 
Can the blue/orange/green be in a separate wad? or does everything have to be the same wad? 
They Can Be Separate 
More convenient to put everything in one, though, I think (unless there's an upper limit on the number of textures in a wad?). 
I have got all of the textures in one big page and I indexed the colours to a 240 palette. What is the top 16 colours in the Q1 palette? Does someone have a link to the top 16 colours in the palette? 
Ok I found an example of a Q1 palette :-

I assume the top 32 are not useable leaving me 224. Should I save all the images as GIF to preserve the colour table? Would a zip full of resized GIF's (all using the same palette) work? 
I'm pretty sure you can use all 256.

Here's a more accurate image. I used to have a .pal but I lost it... 
no, do not use 256.
the last 32 colours are fullbright. (in both images, that's the bottom couple of rows)

also, sock, i found when i was creating q1 editor textures that first shrinking 50% with bi-cubic or some interpolating algorithm, THEN shrinking with a nearest algorithm yielded better results than just shrinking 25% with interpolation.
the final reduction with nearest will give harder edges otherwise it looks a little blurred out.

finally, i'd recommend not converting all the different coloured textures together. esp. the green and blue ones would benefit from some heavy dithering while the concrete ones would probably be better off with none or very light dithering.

you might want to convert the layers separately in the case of concrete + metal overlay textures.

just my 0.02 anyway. 
and then there is the question if it would be worth the trouble at all

there was a photoshop palette somewhere I think 
So should I create a brown+yellow WAD and then put the blue/green/orange in separate WAD's? 
no, i think maybe i misunderstood?
i thought you meant you had every single texture (of all colours) on the same sheet and then you were running the whole thing through the shrink/palettization process.
everything should be in the same wad. i just meant you should palettize each coloured set separately so you can tune dithering settings for best results. 
honestly though... if you use these, you should just include the high res external textures. too much of the great details are lost in just native palette/res. :(
one of my favourite things about the trims are that the edges are not straight at all and wobble around like they are seriously busted up. adds a lot of character to them which gets lost at low res :( 
* re-sized all the textures through several phases (1024>512>256>128 different filters, bicubic first 3 and final hard edge)
* Converted to an optimized palette which I got from putting all the textures on to one page.
* Ran the textures through textures2quake program to create optimized versions. Look really good at the point.
* Imported them into wally and then they look like shit. All textures converted to the default Q1 palette.

I was under the impression that every texture in Q1 could have it's own unique 256 colour palette with the top 24 being the full-bright stuff. It seems not, wally wants all textures to be fixed Q1 default palette. Yuck!

I have all the files and palettes, will zip them up, maybe useful to someone else. 
yeah, that palette is *it*. nothing else. :S

that's why i was saying you'd want to fine tune the dithering settings for the blue and green ones separate from the rest. they will need heavy dithering to work with the quake palette (which does not have many greens or blues of that shade).

half life is the one that allows a palette for each texture, iirc. 
And textures2quake makes Half-Life ones too ;)

And the renaming convention allows using the origins as external texture replacements of the Q1 palette converted set. ;-) 
Color Settings 
Often times with quake conversions it's best to accept that there are some colours it can't render that well, and apply wholesale (consistent) colour filters to the set so that the starting point is at least close to a comfortable quake range. For example I'd take the blue metal set and drop saturation out a bit and reduce the green levels a tad so that it'll map to the icy blue range with just enough dithering to keep it busy and exciting.

One of the really lovely things about this texture set from a quake point of view is that the "base" set is already a very good fit to the quake palette. I tried some tester conversions and the results were really good - just the right level of grain from positional dithering with very little loss of colour fidelity.

I did run into the issues Necros mentioned about blurriness in some places with the fine detail. On the sample I just did some manual cloning from the sections that came out sharp to get a clean result, but it's good to hear there's a way to achieve it algorithmically, because it'd be a large undertaking to do all of that manually. 
Awesome Sock, These Look Great :) 
I tried a conversion to quake palette myself using imagemagick. Going down to 12.5% (128x128) killed too much detail, so I used 256x256. They look more detailed than standard quake textures, but I think the overall effect works. (is it likely one would run in to an engine limit using mostly 256x256 textures in a map?)

quakespasm shot:
winquake shot:

I just need to convert the coloured texture packs and I'll upload my wad. 
Oops, Last Post Was Me. 
Here's My 256x256 Wad Conversion

the blue and green didn't come out great; probably needs some pre-tinting as Preach suggests. 
I made 256� first but negke complained.

ericw, what are you doing with the filenames there? I am confused. You might have done it all in one line with mogrify if I understand it correctly. 
Because 256*256 is usually too big for a normal Q1 wall texture. You'd have to scale it down to 50% like in Q3A, which is somewhat beside the point. It may or may not look slightly better than a manually downscaled texture (though I'd argue that, if done properly, the 128 texture can look just as good), but it'll bump the texture data size unproportionally. 
So Many Wads 
There can be only one! CAGE MATCH! 
I tried to get the blue textures to look nice with a Q1 palette and they certainly look rough when squeezed down by a factor of 8. I like the idea to shift the palette from blue to purple or wizmetal blue. The Q1 palette is fine tuned for some colours better than others.

I did release the Photoshop (CS 5.x version) source file, so it will be very easy for someone to create their own coloured versions. Plus the source file will give people the chance to create or add more stuff to the basic tiles I generated for the packs. There is plenty of stuff buried in the source file I did not use. 
@eric, looks cool the textures in Q1, they seem very grey compared to the brown I made, but I think that is the conversion process because wally did the same for me as well. The brown/yellow parts of my set should certainly feel at home in Q1, for some reason I keep making brown stuff. 
Spirit: I just copied a bash script I found - it used to rename the files to jpg, so it is more complex than needed. For each file foo.tga in the current directory it writes the converted result to quake1/foo.tga. I suck at imagemagick and bash. I think you're right, it could be a one-liner with mogrify. 
get new 32bit color textureset -> force sock to resize and gimp the colors for Quake1 
i was thinking i'll give palletizing it a shot in a little bit later. :) 
Which Size? 
If we can decide on a size 128 or 256 then I could colour match the blue and green to an existing Q1 texture but got no idea what size people want! 
i don't know if it's a good idea to use them at 256.
the reason is that when you're using textures scaled at 50% globally in a q1 map, you are multiplying the amount of lightmaps needed by 4, meaning you'll run out much faster.

besides, not all editors default to 0.5 scaling (nor do they have an option to do so). 
oh also... i think i will hold off on the 300mb source file... i think my bandwidth is running out for this month. :x 
after messing with the blue/greens... i could find nothing i was satisfied with. i think this set is best off using crappy 128x128s as placeholders ONLY and relying on external textures. 
No Idea If You'll Find This Useful... 
Ages ago, I made a series of photoshop curves that, when applied to a greyscale image, map the greys to a certain line of colours in the q1 pallete, in a way that gives the most accurate possible colour preservation when the image is then reduced to the q1 pallete.

When applied wholesale to an image, of course that image will only use one colour line and be fairly boring - but when used on isolated elements of a texture in an overall composition that probably has different elements using different colour lines, it starts to look rather cool indeed!

Here are the curves:

It's pretty wonderful to have a greyscale image, with a brightness/contrast layer, and then one of these curves on top of that - and you just slide the brightness/contrast around and watch the quakey goodness dance perfectly in time to its tune :} 
I understand that the files are ACV (Adobe Curve files) but got no idea how to load them in CS5.5 I try to double click them and PS won't load them. Can't find any forum help either. Any clues? 
Ah Yes 
I use CS5:

Simply create a new curves layer, then in the curves edit window you should see a small drop-down button in the top right corner. Clicking that should lead to a "Load Curves Preset" option. 
While I Am Here 
these colour tables allow you to do the palette conversion in photoshop which i find is so much better than letting say TexMex have its wicked way:

There's a lot of different colour tables in there, all for subtley different uses (like if you want no brights, no red, no black etc.) The readme explains what all the different tables are for. 
Quake 1 Retextured 
Maybe this is the wrong place to ask but in any case :

where can I find high-res textures to change the default Quake 1 textures, to be used with QuakeSpasm ? 
HD Quake 
where can I find high-res textures to change the default Quake 1 textures, to be used with QuakeSpasm ?

Ewwwwwww. You could try asking around - I believe they have a penchant for...that sort of thing.

A very brief googling led me to here: I've no idea if any of that's any good. Although to be honest, "good" in the context of hi-res Quake textures is a bit like asking what's a "good" type of colon cancer to have. 
Yup ! 
Ok, I've found the way to change the default textures. Now I know what you mean by "good" type of colon cancer ! LOL

I may use just a few of the high res textures though, for the crates and items, water, lava and skies, but not all textures.

And the loading process is much slower with all the large textures anyway. Yuck ! 
You Know ... 
The contortions I see people do to convert textures ... like the 36 posts here ... or like what JPL did a while back with the Doom 3 texture set ... it is disturbing to me.

Really disturbing actually.

Converting textures shouldn't even be necessary.

I'd like to be able to map for Quake just having some folders of different textures.

Source included.

It isn't immediately obvious what this does, but it will blow your mind (about 3 or 4 times once I explain all the details and then you will probably laugh -- because most of our tools are frustrating as hell). When I get 3 more hours to polish up the output and harden it against oddball situations I'll start a new thread. And explain how it can be used.

Unfortunately, I have Memorial Day weekend stuff to do right now. Posting this just means I know the source code bundled up and on the internet. 
What does it do, Mister Mysterious? 
If we didn't have people attempting contortions to convert things to the quake palette the ikblue textures would never have been invented. 
One Generation's Limits Are The Next Generation's Aesthetics 
^^^ This 
Also, Baker 
Some description of what this actually does would be much more useful than a bunch of assumptions and assertions. 
SleepwalkR is right. In particular you run the risk of some jackass only looking through your source code for 2 minutes, then declaring that it just performs flat nearest-neighbour conversion - which skirts the core discussion in this thread. 
You can zing me. I don't care.

I was short on time when I did the post and had to leave in 5 minutes for being gone for 10 days but wanted the security of knowing my source code was uploaded.

I'm in the final stages of polishing this up completely. 20% chance I'm done tonight --- except I don't feel very motivated at the moment -- 80% chance this tool is part of a 2-part Friday release.

It's rather funny what it does and doesn't do what you think. But if I explain, then it would be anti-climatic. But most mappers will smile when they see it in action. 
you could have explained in one sentence but instead you made it worse. 
This can't be anything other than a let down at this point. 
This can't be anything other than a let down at this point.

Lately I've been kicking ass at underestimating time frames to polish up things how I want them while over-estimating my free time.

So perhaps you are right, from a certain point of view.

I join you in my displeasure with myself meeting my own time frames (I discovered a frustrating problem, which I certainly wasn't willing to release "as-is" once I noticed it.)

I may have been wrong to get excited about the tool's imminent release, but I still feel excited about the absurd thing the tool does.

Real-life seems to enjoy throwing me curve balls lately.

This kind of thing doesn't discourage me, I file it under "Ok that sucked, so I don't do it as fast at I wanted but I think the sun will still rise in the morning" department".

It does upset me some, but I am more than willing to rub life's face in the dirt the second it stops paying attention.

Is that worth anything today? No, not really. 
I Think 
you totally misunderstood Willem... 
Post A Reply:
Website copyright © 2002-2018 John Fitzgibbons. All posts are copyright their respective authors.