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. ;-) 

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. 

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: http://www.quaketastic.com/upload/files/screen_shots/tp_indust_base_ericw_test.jpg
winquake shot: http://www.quaketastic.com/upload/files/screen_shots/tp_indust_base_ericw_test2.jpg

I just need to convert the coloured texture packs and I'll upload my wad. 

 

http://www.quaketastic.com/upload/files/texture_wads/tp-indust-256.zip

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. 

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. :) 

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. 

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:

http://dl.dropbox.com/u/61424391/Temp/photoshop%20curves/photoshop%20curves.rar

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? 

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. 

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:

http://dl.dropbox.com/u/61424391/Temp/photoshop%20color%20tables.rar

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. 

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 ? 

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 QuakeOne.com - I believe they have a penchant for...that sort of thing.

A very brief googling led me to here: http://qrp.quakeone.com/retexture/ 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. 

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 ! 

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.

http://quake-1.com/docs/utils/highres4quake_beta_prerelease.zip

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.