Quake3World

I edited this topic and added description how to convert maps from Q4 and D3.
Notification!
It is not about EULA and such other questions. It's just description of a technology. It can be useful or not, but it works and it's enough for me. I did it for my amusement.

Instruments:

1. QuArK 6.6.0 Beta 6 from here http://quark.sourceforge.net/
2. GTKRadiant 1.6.3 (not 1.6.4, as its Surface Inspector works incorrectly) or a good old Q3Radiant 2.0.2
3. Q3MAP2 (q3map2_fs_20g or 2.5.17)
4. BSPC (2.1i)
5. Paint.NET

Algorithm:
1. Extract all files from all the *.pk4 files in <DOOM3>\base or <QUAKE4>\q4base
2. Open <yourmap>.map in QuArK and save it as 'QuArK map (*.qkm)' and further as 'Structured text for hand-editing (*.qkm)
3. Close the map in QuArK and open it in Notepad (or WordPad) and replace Game = "Quake 4" by Game = "Quake 3"
4. Re-open the map in QuArK (now it will be Quake3 game mode) and save it as 'Quake .map file (*.map)' into your work folder, for example, <QUAKE3>\baseq3\maps
5. Open the map with in Notepad (or WordPad) and remove all 'textures/' as Q3 uses short path for textures names (NB! as Q4 has folder 'textures/mptextures/' you should replace '/mptextures/' by '/mp/' previously and rename the folder 'textures/mptextures/' to 'textures/mp/' )
6. Compile the map with Q3MAP2 (with -bsp key only). It's just a raw compilation to get list of necessary textures (and shaders)
7. Search necessary shaders through <DOOM3>\base\materials or <QUAKE4>\q4base\materials to define layers to make necessary textures
8. How to make new textures see my manual below
9. Write shaders for complex textures and place it into <QUAKE3>\baseq3\scripts and insert the name of your shader file into shaderlist.txt
10. Open the map in GTKRadiant (NB! change default project settings to work with brush primitives) and edit it as you wish
11. Compile the map with Q3MAP2 (to make *.bsp) and BSPC (to make *.aas - for bots)

I want to share my experience how to adapt Q4 textures for Q3. I use Paint.NET for this.
Steps (see screenshots):

1. Open the chosen file <>_local.tga



2. Desaturate it



3. Invert colors


4. Add the file <>_d.tga as another layer




5. Adjust its properties - OVERLAY



6. Add the file <>_h.tga as another layer



7. Adjust its properties - OVERLAY



8. Add the file <>_s.tga as another layer



9. Adjust its properties - COLOR DODGE



10. Save the file <>.jpg (or with another necessary name)


NOTICE: This algorithm can be used to create *.jpg textures (without alpha channel).

This algorithm can be used for converting D3 files too, though its texture set is organized worse and in fact is composed from some different sets (it can be seen in different file mask for heightmap textures).

None of your pictures work.

V1979, better could be done if you use some of general image hosting sites (for example imgur.com) instead of using local hosting in your country... Most of people block russian domains as they are often source of malware.

I reduced pictures' size and uploaded them to imgur.com

This is a good tutorial, but not really necessary since ioquake3 supports normal/specular maps.

Thanks Andeh, not everyone use ioquake3 and q3map2 supports baking lightmap based on normalmap, which do not require to use ioquake3. For speculars, it is much worse as you have to make another stage that reflects the specular glares as environment map (tcGen environment).

It's really good, if ioquake3 supports normal/specular maps. Is there any example of such shaders?
Some thoughts:
1. Not everybody plays ioquake (I don't play it though I have it).
2. Converting textures (to *.jpg) allows to reduce *.pk3 size, though some visual effects are limited.
3. Some players set picmip >0, thus many efforts to improve visual aspects are useless.

nice!
going to try and make that process it into a script for imagemagick

Everyone should use ioquake3 since theres literally no drawbacks to using it. Also CZghost, normalmaps are different to lightmaps. q3map2 doesn't handle normalmaps. They are done purely through material (.mtr) files

Q3map2 does fake normals by baking the detail into the lightmap.

And ioq3 is buggy as hell sometimes, at least the forks I use. There's nothing enticing enough in stock ioq3 to convince me to get rid of my awesome features in my engine.

https://www.dropbox.com/s/acxgim6a3assx ... ormals.gif

I used to have an actual lightmap on my dropbox but idk where it is from my phone.

That's quite wrong, Andeh. First, Quake 3 does not have support for mtr (I do not count ioquake3) and last version of q3map2 can handle the normalmap to bake lights that wrap around the fake bumbs to create visual effect similar to the Q4 one. Sure you have to make finer lightgrid to allow this feature. Also, it's not so much known feature and it needs much tweaking, so it is not used so much by mappers.

Also, ioquake3 is quite buggy. I can't control the brightness to get rid of the overall darkness. The entire screen is too dark. Also it does not support the numpad.

I like what you're doing, but doesn't this violate the EULA of both quake 3 and quake 4?

ioquake3 isnt buggy at all for me, not sure what version you guys are using...

CZ - I know Quake 3 does not support mtr, I never said it did. ioquake3 does though, and I still think theres no benefit to sticking with vanilla Quake 3.

VolumetricSteve wrote:I like what you're doing, but doesn't this violate the EULA of both quake 3 and quake 4?

Yes indeed, and this is certainly frowned upon by the community. Maps and assets being shared that violate EULA's will be blacklisted here and on other networks like LvL.

LvL and Worldspawn Archive dont care for copyrights.

Everyone should though!

They don't care until someone report it.

AndehX wrote:ioquake3 isnt buggy at all for me, not sure what version you guys are using...

CZ - I know Quake 3 does not support mtr, I never said it did. ioquake3 does though, and I still think theres no benefit to sticking with vanilla Quake 3.

Well, I downloaded and tried out last version available for Windows 7. Running with nVidia GeForce 9800 GT videocard.

When I started this topic, I just wanted to share my experience how to make textures for Q3 from set of Q4 textures.
I didn't thought that it could provoke discussion about EULA, ioquake features etc.
My method allows to make textures for standard Q3 engine (v.1.32c), the most commonly used release. To use normal maps for Q3, I would suggest using q3bers engine, as it is compatible with other mods and has its own working shader syntax for bumpmapping.

I have no issue with this tutorial. This set of techniques can be applied for valid or personal situations which respect EULAs. What becomes questionable is distribution of assets. It's just a note bringing awareness to others about why this remains an important issue.

@V1979: don't convert normal maps using desaturation, that results in incorrectly interpreted grey-scale tonal values in the bump/height maps - light-blue is not synonymous with light-grey.

Kat, I am satisfied with my results. See screenshots or just repeat my steps.

V1979 wrote:Kat, I am satisfied with my results. See screenshots or just repeat my steps.

Will do... when wanting to know how NOT to do it