New DoomEdit CleanMaterials pak file download

eskimo roll · **Posted:** Mon Sep 20, 2004 12:01 pm

Cheers for all the effort thats gone into this, esp to Jafo & Eutectic, can't even begin to think about how many man hours this is going to save.

demonspawn · **Joined:** Wed Sep 18, 2002 10:47 pm **Posts:** 153

Great work Eutectic, on behalf of all the D3 mappers.....thanks

Masher · **Posted:** Mon Sep 20, 2004 4:53 pm

Regardless the fact it has been said numerous times before: Thanx alot for your work guys. This makes everything alot more fun :!:

- Mash

TodT7 · **Posted:** Mon Sep 20, 2004 6:29 pm

THANKS A LOT!!!
I can barely imagine the amount of work has been done. :shock:

It will save a fair amount of time for all of us who uses the editor.

indianajonesilm · **Joined:** Thu Sep 16, 2004 7:41 am **Posts:** 31

Thank you again for all your hard work. I did notice however that the hell/crystal1 texture doesn't work anymore. It used to show this neat effect that would change colors depending on the angle you would view it, but now after the using your pk4 it just shows up black:

Before on top, with materials pak on bottom.
Also some other strange things pop up on my map:

Before on top, with materials pak on bottom. Usualy after killing an imp nearby.
I still use your awesome pak while editing, but just disable it when playing the game.

Eutectic · **Posted:** Mon Sep 20, 2004 9:36 pm

Are you sure? Here's the original material code for textures/hell/crystal1 as written by Id software:

Code:

textures/hell/crystal1
{
   translucent
   noshadows
   glass
//   qer_editorimage      textures/hell/crystal1_s
   {
      blend         gl_dst_color,gl_one_minus_src_alpha
      map            textures/hell/crystal1
   }
   {
      blend    add
      cubeMap   env/reactor 
      texgen   reflect
   }
   specularmap         textures/hell/crystal1_s
}

I checked the contents of the game's pak000.pk4 and pak004.pk4 and none of the textures (including env/reactor) refered to by this material exist. It's 100% broken from the start. I also did a search in all of Id's game maps and this material is not used in ANY of their maps.

The problem is that you used a broken material in your map. If it "used to produce a cool effect" then that's a fluke. It should not display anything at all. And it should not be used in maps.

rich_is_bored · **Posted:** Mon Sep 20, 2004 9:52 pm

I think this is the part that does that "pseudo-iridecent" effect...

Code:

{
      blend    add
      cubeMap   env/reactor
      texgen   reflect
   } 

Dr Evanzan · **Posted:** Mon Sep 20, 2004 9:53 pm

Thanks for this, I've just completed Doom 3 and I'm about to start level creation in earnest, so I'm sure this will be very helpful.

However, I've come across a problem. The pentagram that appears (and then burns into the floor) when an imp or somesuch teleports in does not seem to display properly with the pk4. Instead it overlays badly for a while before disappearing, as per:

If you have an autosave for Central Processing handy then there is some handy examples right at the start of this level (at least on 'Marine' skill).

I'm afraid pointing you towards the specific shader is a bit beyond me at the moment! :oops:

Thanks again for all your work!

Eutectic · **Posted:** Mon Sep 20, 2004 10:05 pm

Ok I uploaded a new fix: Version 3.

Thanks cold_Fusion for his precious feedback. A silly oversight on my part, I had forgotten to uncomment the material textures/decals/spawndecal in decals.mtr which is used by the game during demon spawns (but must not be used for texturing map geometry however).

If you're comfortable with WinZip, you can do the fix yourself easily without having to download a new version (assuming you already have V2). Here's how:

- rename the pk4 to .zip and double-click on it to open the file in WinZip
- scroll to the file decals.mtr, right-click on it and select "view with NOTEPAD.EXE"
- scroll down to where the material textures/decals/spawndecal is located
- remove the // double-slashes at the beginning of every line of that shader/material
- edit the qer_editorimage parameter to textures/editor/dontuse.tga

It should look like this when you're done:

Code:

textures/decals/spawndecal
{
   qer_editorimage textures/editor/dontuse.tga
   noselfShadow
    noshadows   
   translucent
   discrete
   nonsolid
   noimpact
   twosided

   DECAL_MACRO
   decalInfo 0.75 10 ( 1 1 1 10 ) ( -5 -5 -5 0 )
   
   {       
      
         blend      gl_zero, gl_one_minus_src_alpha
      map         makealpha(textures/decals/spawndecal_burn)
      clamp      // we don't want it to tile if the projection extends past the bounds
      //rgb         decalFade[(time - Parm3)/(parm4 - parm3)]
      vertexColor   // oblique projections will be slightly faded down
   }

   {
         blend   add  
      map      textures/decals/spawndecal
      //rgb      fireballtable[ time * .5 ]
      vertexColor   // oblique projections will be slightly faded down
   }
}

- save the file and close it, Winzip will notice the file has changed and ask you if you want to update the archive. Choose YES.
- that's it, your pak file is fixed. Just rename it to .pk4 again and you're ready to go.

But if you have a broadband connection and don't mind DL'ing a 13MB file, then simply go to the top post of this thread to download V3

Dr Evanzan · **Posted:** Mon Sep 20, 2004 11:01 pm

Hey, cool, fixed already!

Thanks!

Eutectic · **Posted:** Tue Sep 21, 2004 12:00 am

NP , thanks for your feedback Dr Evanzan

MNeMiC · **Posted:** Tue Sep 21, 2004 7:40 am

In the next release you should fix the mirror texture, since it's pretty fucked up for some of the releases, in some versions it works fine, but in some (mine), it shows as a normal mirror, BUT! with a black text over it saying: MIRROR, really annoying =/

goliathvt · **Joined:** Sun Jan 18, 2004 9:41 pm **Posts:** 2143

That already has been fixed. The problem is that an image remains from V1 that shouldn't be there at all:

base/textures/common/mirror.tga

V2 and V3 have fixed this by using a mirror_editor.tga image (or something like that) that is used only by the editor. The material file(s) from V2 and V3 still point to "base/textures/common/mirror", but, like I said, there shouldn't be an actual image called mirror.tga in the common directory at all.

When you updated to newer versions, there was no way to delete this unnecessary image (mirror.tga) so you have to do it yourself. Leave the mirror_editor.tga one alone though.

Goliath

Eutectic · **Posted:** Wed Sep 22, 2004 1:58 am

Ok let me explain in better detail to make this perfectly clear. This problem was caused by a series of circumstances which have to be described in their chronoligical order to understand what happened. Id's original code for the material textures/common/mirror (materials/invisible.mtr) is as follows:

Code:

textures/common/mirror
{
   discrete      // never merge with other surfaces
   qer_editorimage textures/common/qer_mirror.tga
   solid
   mirror
   {
      blend add
      map textures/common/qer_mirror.tga
   }
}

Now the file textures/common/qer_mirror.tga does not exist in Id's standard pak004.pk4. So when Jafo first worked on his clean shader PAK, he must have noticed that DoomEdit's Texture view only displayed an empty black square for it. So he created that 64x64 pixel texture with the word Mirror in black letters on it. He named it qer_mirror.tga and put it in the "common" folder inside his d3weditor PAK file.

So now in DoomEdit's texture view, you see this custom qer_mirror.tga texture instead of a small black square and life is good right?.... Wrong!

By doing this, he accidentally broke the shader. Why? Because if you look at the code above, the blend add stage calls for the same texture: textures/common/qer_mirror.tga . And this is the reason why the word Mirror in black letters appears on the game mirrors. Now the game does find the texture (which it shouldn't in order to work properly).

You see, the mirror material is an exeptional case: it doesn't need an actual texture to work. In fact it must NOT use one. But for some reason, perhaps a "dummy" blend add stage is required to make it work properly. But the thing that really makes it a mirror is the "mirror" property in the material code.

My fault was that I didn't try applying the mirror texture on a patch and compile the map to see what it looks like in the game. I just assumed it worked properly and I didn't check the shader code either. IOW, my mistake was that I failed to spot Jafo's mistake. I realized the above particularity about the mirror material only after someone else spotted it for me (and I thank him for that).

Now. In order to fix it, qer_mirror.tga must not exist. But at the same time, I didn't want the Texture view in DoomEdit to display a black square as a result of not finding it. So the solution is to assign a different texture to the qer_editorimage parameter than the one that's called in the blend add stage of the material (which must not exist).

Since I won't change anything in the actual material code by principle (anything else than the qer_editorimage parameter IOW), I renamed the qer_mirror.tga texture created by Jafo to qer_mirror_editor.tga and I edited the qer_editorimage parameter in the material to point to THAT file instead.

Code:

textures/common/mirror
{
   discrete      // never merge with other surfaces
   qer_editorimage textures/common/qer_mirror_editor.tga
   solid
   mirror
   {
      blend add
      map textures/common/qer_mirror.tga
   }
}

So now, everybody's happy. The material is happy because it DOESN'T find qer_mirror.tga and mirrors works perfectly in the game. And the map designer is happy because DoomEdit's Texture window DOES find and display the 64x64 symbolic qer_mirror_editor.tga texture. Then I rebuilt a new PAK file and distributed it as Version 2.

Mnemic:

If you see the word Mirror in black letters on mirrors in the game, that's due to one of the following 3 possibilities:

1. You're using Jafo's PAK instead of mine (some people may have these 2 confused). With all due respect and IMHO, nobody should use that PAK because there are many errors in it (119 to be exact, apart from the mirror thing).

2. You're using Version 1 of my PAK since this problem was fixed in Version 2 (and later)

3. You're using Version 2 or later but you have extracted the content of my PAK to your hard drive (against the specific recommendation in my readme file to NOT extract the content of the PAK). By extracting, you overwrote the invisible.mtr file and extracted qer_mirror_editor.tga but qer_mirror.tga did NOT get deleted as it should have. Thus, the shader STILL finds the texture that it should not find and remains broken. By keeping stuff inside PAK files and simply using new PAK's, you avoid any possiblity of such a problem occuring.

NOTE:
If you want to extract stuff to look at it, go ahead but don't extract it in the game's base folder! That's asking for trouble.

Jafo · **Posted:** Wed Sep 22, 2004 4:45 am

My bad on the mirror, I missed that it was using the same image as an alpha blend, kind of hard to do without an alpha channel:) So when the game didn't report a missing texture I did think life was good, as usual I should have looked in the mirror:) Thanks Eutectic for taking this to it's final step, I got pretty burnned out trying to clean up what seemed like 500 + shaders. PS, damn easy to break the alpha on some of those decals, might want to check the UAC decal too, I think I horked that one in the beginning. You ran into the same problems I did, env folder having odds and ends, like one of the id guys smoked a bowl then started dropping textures wherever he felt like it

Also the BFG_wallmark (IT?) had me boggled cause I kept getting an error but it was fine. I did comment out some shaders that actually worked... even though I thought they did not, but I never found them being used in any of the maps. Well, great job, thanks for the final effort in this.

Eutectic · **Posted:** Wed Sep 22, 2004 8:16 am

Jafo wrote:

My bad on the mirror, I missed that it was using the same image as an alpha blend, kind of hard to do without an alpha channel

Actually, it's an additive blendmap. Those don't require textures with an alpha channel. All this does is add the RGB value of every pixel in the texture to the RGB value of the pixels in texture underneath it. It's often used for the "illumination area" of light fixture textures.

Quote:

Thanks Eutectic for taking this to it's final step, I got pretty burnned out trying to clean up what seemed like 500 + shaders.

Uhh... More like 3700+ (look at the file named stats.txt inside the zip file). And I'm not counting the model, particle and gui, etc materials...

Quote:

PS, damn easy to break the alpha on some of those decals, might want to check the UAC decal too, I think I horked that one in the beginning.

Which one? There are several "UAC decals". How about a material name please? I hope you don't mean that you tried to modify the shader code itself (other than qer_editorimage) in the attempt to "make them work". Gaaawd please tell me it ain't so because if it is, then I'm in deep doodoo since I used your modified files as a starting point for the job. :shock:

Quote:

You ran into the same problems I did, env folder having odds and ends, like one of the id guys smoked a bowl then started dropping textures wherever he felt like it

I don't really follow you here. The enviroment map textures in the env/ folder was the least of my worries. There was only a handful of them and they seemed fine to me.

Quote:

Also the BFG_wallmark (IT?) had me boggled cause I kept getting an error but it was fine.

Do a search on the keyword "vertexcolor" and filter by poster name Eutectic. I bogged down on those too until someone explained to me what the "vertexcolor" shader parameter is for (meant for models only, not map brushes and patches). The textures/decals/bfg_wallmark material is one of those I call "naming convention offender materials". One of many that should never have been named textures/something but rather something like models/weapons/something for eg.

Quote:

I did comment out some shaders that actually worked... even though I thought they did not

Yes, 66 to be exact. Not too bad considering theres 3700+ textures/something materials in the game's .mtr files

Quote:

... but I never found them being used in any of the maps.

They didn't break anything in the game then. However, it did take away 66 good shaders from the map designer's "texture palette". Not a biggie perhaps but I wanted to make sure the mappers get the most out of the Doom Editor.

Quote:

Well, great job, thanks for the final effort in this.

You're welcome. I would appreciate if you clarified your UAC decal comment above. It's a rather burning question for me.

Eutectic · **Posted:** Thu Sep 16, 2004 10:06 pm

[EDIT] New URL

http://www.pcgamemods.com/mod/9082.html

==============================

It's done.

This is a follow-up of Jafo's d3weditor clean shaders/materials pk4 file which served as a starting base for this new PAK. I won't print the complete stats here since those are included in the zip file (along with a readme file). However, here's a quick overlook:

66 materials commented out in Jafo's PAK were in fact good.
53 materials in Jafo's PAK were in fact broken.
These materials were uncommented/commented out accordingly.

But the main difference lies in the fact tht this new PAK has 193 new TGA's to provide for qer_editorimages that were either missing or did not adequately depict what the texture really looks like in the game. Some of you who are currently designing maps in DoomEdit may think this PAK is just eye candy. If so, then consider these figures (compiled at the end of this project):

//=========== Global textures/_ materials stats==============
//
// Total # of textures/_ materials : 3708
// Total # of working shaders: 1950 (approx. 52.5%)
// Total # of Broken/CommentedOut shaders: 1614 (approx. 43.5%)
// Total # of shaders which can't be used for map texturing and kept by necessity: 144 (approx. 4%)
//==============================================

Now I noticed that many of the materials in the original .mtr files can be misleading. Those may seem to be working but are really broken because the material code calls for a single non-existent TGA. The result is a texture that will display on your brush/patch in the game but won't look right (for eg. a material in which only the specularmap parameter refers to a TGA file that doesn't exist while the bump and diffuse map TGA's do exist).

That means there's a significant chance that you might unknowingly be using broken materials to texture your map's geometry. So this PAK not only improves the look and ease of use of DoomEdit's texture window, it also ensures that you use only 100% working materials to texture your maps.

DoomEdit CleanMaterials Version 5
(approx 13MB download)

Notes:
- Version 2 has fix for qer_mirror texture appearing on mirrors in game.
- Version 3 fixes the demon spawndecal not appearing in game.
- Version 4 adds the 6 new materials in the V1.1 game patch plus a cosmetic issue with the editorimage textures/editor/redge.tga. Please note that these new materials are not meant to be used for map texturing. They were added so that my PAK won't break the new chat and lag icons in the V1.1 patched game when playing in MP mode. That's the ONLY real change in the V4 CleanMats.
- Version 5 is the final cleanup phase. All the remaining materials have now been cleaned up (models, light, fog, fx's, gui's, particles, etc.). I also improved the qer_editorimage for model based entities in CAM view while in skinned mode. Most monsters/NPC's displayed their displacement map as the editorimage by default. Static models often used their addblend map by default (which made them appear pitch black). Most now use the _local bumpmap which improves visibility and clarity in skinned mode.

- There are no new TGA files in this pak so it's the same size as the last version.

A few broken materials for the sentry character reside in the sentry.def file so you need to download my latest Clean def's PAK to make this 100% complete. Please check the "Editing resources" sticky post in this forum for the URL of the "Clean def's" thread

PS: Mods please update links in other posts to point to this one (if required). Thanks.
[EDIT]new url. kat

zeh · **Posted:** Thu Sep 16, 2004 10:08 pm

http://www.doom3world.org/phpbb2/viewtopic.php?t=6012

Eutectic · **Posted:** Thu Sep 16, 2004 10:14 pm

Oops... missed that completely. Looks like BNA beat me to the punch :wink:

AEon · **Joined:** Mon Aug 18, 2003 4:05 am **Posts:** 127

Eutectic,
first off wonderful job...

One thing I have been wondering is this.

How will maps using this pack work on a clean (non-development) install of D3. In Q3A there where several special textures provided with GTKradiant editing, that where not part of the clean retail install, thus missing on those machines.

I guess all the preview images you created from scratch will not be the problem, since these are editor only. But did some of the shaders e.g. have to be changed to differ from the originals?

funcrusher · **Joined:** Sat Aug 21, 2004 7:22 pm **Posts:** 238

AEON - if this works as it should, there should be no problem with distributing a map created with the help of these files. If I understand correctly this pak shouldnt alter the paths to the textures in the .map file - and qer_editorimage images dont matter for final output - they are never displayed in game.

bb_matt · **Posted:** Fri Sep 17, 2004 7:49 am

I've sticky-fied this thread !

Eutectic · **Posted:** Fri Sep 17, 2004 8:23 am

AEon wrote:

Eutectic,
first off wonderful job...

One thing I have been wondering is this.

How will maps using this pack work on a clean (non-development) install of D3. In Q3A there where several special textures provided with GTKradiant editing, that where not part of the clean retail install, thus missing on those machines.

Thanks

Maps made while having this PAK enabled will work just fine in the standard plain-jane Doom3 game. I did not add any new shaders/materials in the mtr files. All I (and Jafo) did was to comment out the broken materials so they don't get parsed by the editor, that's all.

Quote:

I guess all the preview images you created from scratch will not be the problem, since these are editor only.

That's right. The TGA file that the qer_editorimage parameter points to affects only what you see in the editor's texture window and in the CAM view. It has no effect on the the material in the game itself.

Quote:

But did some of the shaders e.g. have to be changed to differ from the originals?

Absolutely not. That would have been the worst thing to do and I made it a point to never do that. All the shaders' code were left intact and original. My goal was not to "repair" anything. My goal was simply to sort out which materials really work and which ones don't work. The ones that don't work were commented out, the ones that DO work were left untouched except for the qer_editorimage to improve how it looks in the Texture window. And that's all there is to it.

Brain Trepaning · **Posted:** Fri Sep 17, 2004 3:48 pm

Thanks a lot, this will be very helpful for many mappers. I know I have my copy!

weak · **Posted:** Fri Sep 17, 2004 4:16 pm

thx a lot!

[--TeK--] · **Posted:** Fri Sep 17, 2004 4:34 pm

A big thx to you and Jafo for the good job...very helpful

RonHiler · **Posted:** Fri Sep 17, 2004 4:48 pm

Question:

I have D3 completely unpacked for mapping purposes. I downloaded the pk4 and put it into base, but the editor is not reading it.

Is it true that the editor cannot mix unpacked with packed? I ran into this same problem with .def files (I had D3 packed and it wasn't reading my custom .def files, which is what prompted me to unpack them in the first place). Once I had unpacked the D3 files, my own def files read fine. It seems like I've hit this issue again.

So bascially the question is, do I have to unpack the clean materials in my unpacked directory for them to read?

Ron

rich_is_bored · **Posted:** Fri Sep 17, 2004 5:43 pm

That may work.

But, I'd advise that if you need to extract the vanilla pk4s for reference then you extract them to somewhere outside the Doom 3 folder. This way you don't have to worry about problems like this where something that should work doesn't.

goliathvt · **Joined:** Sun Jan 18, 2004 9:41 pm **Posts:** 2103

Outstanding work!

Thanks guys!

G

Origin73 · **Posted:** Fri Sep 17, 2004 6:24 pm

This is awesome!

Thank you!

Wiebo de Wit · **Joined:** Mon Aug 09, 2004 7:51 am **Posts:** 9

You, sir, are a life saver. Downloading now and eager to get to work with it!!!!

Techx · **Joined:** Sat Sep 20, 2003 11:35 pm **Posts:** 78

This is great, thanks for putting the time into making it!

Docgalaad · **Posted:** Sat Sep 18, 2004 3:28 am

Amazing, i have two things to say:
- The lighting in the render view is now true, like ingame, awesome
- The visportals and other formerly black textures are now colored and this is great

I just had an issue with mirrors. Ingame there is the word mirror on all the mirror surfaces of my maps. So i have to disable ZZ-xxx.pk4 to see the final map properly.

A huge *thank you* for the massive work achieved.
I can imagine the task, so many notepad openings.

Cheers.

Eutectic · **Posted:** Sat Sep 18, 2004 6:22 am

Docgalaad wrote:

Amazing, i have two things to say:
- The lighting in the render view is now true, like ingame, awesome
- The visportals and other formerly black textures are now colored and this is great

I just had an issue with mirrors. Ingame there is the word mirror on all the mirror surfaces of my maps. So i have to disable ZZ-xxx.pk4 to see the final map properly.

A huge *thank you* for the massive work achieved.
I can imagine the task, so many notepad openings.

Cheers.

You're very welcome. About the textures/common/mirror material, I found the reason why. Here's the material code:

Code:

textures/common/mirror
{
   discrete      // never merge with other surfaces
   qer_editorimage textures/common/qer_mirror.tga
   solid
   mirror
   {
      blend add
      map textures/common/qer_mirror.tga
   }
}

The TGA file "textures/common/qer_mirror.tga" is not present in the original game's pak004.pk4 , therefore you don't get this problem in the original game. The problem with this material is that that TGA image is used as a blendmap in the original code. It's not the qer_editorimage that causes this but the blend add stage.

Incidentally, I didn't create this image, my predecessor did. But ultimately it's my fault. I didn't test the textures/common materials thoroughly enough assuming there couldn't be anything wrong about those since they're so simple and straighforward.

I will fix that by renaming the qer_mirror.tga to something else and edit the qer_editorimage line to point to the renamed image instead. I won't change the blend add stage of course - the idea is that it must NOT find the TGA file it points to. The shader probably needs a blend add stage pointing to an inexistent texture to work properly (at least that's what I'm guessing). In any case, I musn't change the original shader code, I have to work around it.

The only downside is that you will get a "warning: textures/common/qer_mirror.tga not found" message when you load the material in the editor. But you won't see a "mirror" texture in your compiled maps anymore.

Oh well.... that's why I gave that editing pack Version numbers. Thanks for pointing out the booboo Docgalad. I will test all the textures/common materials throroughly this time and post a Version 2 ASAP.

UPDATE:

I checked all the textures/common and textures/editor materials in a compiled map and they all work. I uploaded the fixed Version 2 and updated the link in the top post.

indianajonesilm · **Joined:** Thu Sep 16, 2004 7:41 am **Posts:** 31

WOW!!!!

I would just like to say THANK YOU to all involved in making this. I now know why my Bloody Bootprints were not showing up in game! Thank you for all your hard work. WOW!

Did I forget to say "WOW"!!!

Eutectic · **Posted:** Thu Sep 16, 2004 10:06 pm

[EDIT] New URL

http://www.pcgamemods.com/mod/9082.html

==============================

It's done.

This is a follow-up of Jafo's d3weditor clean shaders/materials pk4 file which served as a starting base for this new PAK. I won't print the complete stats here since those are included in the zip file (along with a readme file). However, here's a quick overlook:

66 materials commented out in Jafo's PAK were in fact good.
53 materials in Jafo's PAK were in fact broken.
These materials were uncommented/commented out accordingly.

But the main difference lies in the fact tht this new PAK has 193 new TGA's to provide for qer_editorimages that were either missing or did not adequately depict what the texture really looks like in the game. Some of you who are currently designing maps in DoomEdit may think this PAK is just eye candy. If so, then consider these figures (compiled at the end of this project):

//=========== Global textures/_ materials stats==============
//
// Total # of textures/_ materials : 3708
// Total # of working shaders: 1950 (approx. 52.5%)
// Total # of Broken/CommentedOut shaders: 1614 (approx. 43.5%)
// Total # of shaders which can't be used for map texturing and kept by necessity: 144 (approx. 4%)
//==============================================

Now I noticed that many of the materials in the original .mtr files can be misleading. Those may seem to be working but are really broken because the material code calls for a single non-existent TGA. The result is a texture that will display on your brush/patch in the game but won't look right (for eg. a material in which only the specularmap parameter refers to a TGA file that doesn't exist while the bump and diffuse map TGA's do exist).

That means there's a significant chance that you might unknowingly be using broken materials to texture your map's geometry. So this PAK not only improves the look and ease of use of DoomEdit's texture window, it also ensures that you use only 100% working materials to texture your maps.

DoomEdit CleanMaterials Version 5
(approx 13MB download)

Notes:
- Version 2 has fix for qer_mirror texture appearing on mirrors in game.
- Version 3 fixes the demon spawndecal not appearing in game.
- Version 4 adds the 6 new materials in the V1.1 game patch plus a cosmetic issue with the editorimage textures/editor/redge.tga. Please note that these new materials are not meant to be used for map texturing. They were added so that my PAK won't break the new chat and lag icons in the V1.1 patched game when playing in MP mode. That's the ONLY real change in the V4 CleanMats.
- Version 5 is the final cleanup phase. All the remaining materials have now been cleaned up (models, light, fog, fx's, gui's, particles, etc.). I also improved the qer_editorimage for model based entities in CAM view while in skinned mode. Most monsters/NPC's displayed their displacement map as the editorimage by default. Static models often used their addblend map by default (which made them appear pitch black). Most now use the _local bumpmap which improves visibility and clarity in skinned mode.

- There are no new TGA files in this pak so it's the same size as the last version.

A few broken materials for the sentry character reside in the sentry.def file so you need to download my latest Clean def's PAK to make this 100% complete. Please check the "Editing resources" sticky post in this forum for the URL of the "Clean def's" thread

PS: Mods please update links in other posts to point to this one (if required). Thanks.
[EDIT]new url. kat

zeh · **Posted:** Thu Sep 16, 2004 10:08 pm

http://www.doom3world.org/phpbb2/viewtopic.php?t=6012

Eutectic · **Posted:** Thu Sep 16, 2004 10:14 pm

Oops... missed that completely. Looks like BNA beat me to the punch :wink:

AEon · **Joined:** Mon Aug 18, 2003 4:05 am **Posts:** 127

Eutectic,
first off wonderful job...

One thing I have been wondering is this.

How will maps using this pack work on a clean (non-development) install of D3. In Q3A there where several special textures provided with GTKradiant editing, that where not part of the clean retail install, thus missing on those machines.

I guess all the preview images you created from scratch will not be the problem, since these are editor only. But did some of the shaders e.g. have to be changed to differ from the originals?

funcrusher · **Joined:** Sat Aug 21, 2004 7:22 pm **Posts:** 238

AEON - if this works as it should, there should be no problem with distributing a map created with the help of these files. If I understand correctly this pak shouldnt alter the paths to the textures in the .map file - and qer_editorimage images dont matter for final output - they are never displayed in game.

bb_matt · **Posted:** Fri Sep 17, 2004 7:49 am

I've sticky-fied this thread !

Eutectic · **Posted:** Fri Sep 17, 2004 8:23 am

AEon wrote:

Eutectic,
first off wonderful job...

One thing I have been wondering is this.

How will maps using this pack work on a clean (non-development) install of D3. In Q3A there where several special textures provided with GTKradiant editing, that where not part of the clean retail install, thus missing on those machines.

Thanks

Maps made while having this PAK enabled will work just fine in the standard plain-jane Doom3 game. I did not add any new shaders/materials in the mtr files. All I (and Jafo) did was to comment out the broken materials so they don't get parsed by the editor, that's all.

Quote:

I guess all the preview images you created from scratch will not be the problem, since these are editor only.

That's right. The TGA file that the qer_editorimage parameter points to affects only what you see in the editor's texture window and in the CAM view. It has no effect on the the material in the game itself.

Quote:

But did some of the shaders e.g. have to be changed to differ from the originals?

Absolutely not. That would have been the worst thing to do and I made it a point to never do that. All the shaders' code were left intact and original. My goal was not to "repair" anything. My goal was simply to sort out which materials really work and which ones don't work. The ones that don't work were commented out, the ones that DO work were left untouched except for the qer_editorimage to improve how it looks in the Texture window. And that's all there is to it.

Brain Trepaning · **Posted:** Fri Sep 17, 2004 3:48 pm

Thanks a lot, this will be very helpful for many mappers. I know I have my copy!

weak · **Posted:** Fri Sep 17, 2004 4:16 pm

thx a lot!

[--TeK--] · **Posted:** Fri Sep 17, 2004 4:34 pm

A big thx to you and Jafo for the good job...very helpful

RonHiler · **Posted:** Fri Sep 17, 2004 4:48 pm

Question:

I have D3 completely unpacked for mapping purposes. I downloaded the pk4 and put it into base, but the editor is not reading it.

Is it true that the editor cannot mix unpacked with packed? I ran into this same problem with .def files (I had D3 packed and it wasn't reading my custom .def files, which is what prompted me to unpack them in the first place). Once I had unpacked the D3 files, my own def files read fine. It seems like I've hit this issue again.

So bascially the question is, do I have to unpack the clean materials in my unpacked directory for them to read?

Ron

rich_is_bored · **Posted:** Fri Sep 17, 2004 5:43 pm

That may work.

But, I'd advise that if you need to extract the vanilla pk4s for reference then you extract them to somewhere outside the Doom 3 folder. This way you don't have to worry about problems like this where something that should work doesn't.

goliathvt · **Joined:** Sun Jan 18, 2004 9:41 pm **Posts:** 2108

Outstanding work!

Thanks guys!

G

Origin73 · **Posted:** Fri Sep 17, 2004 6:24 pm

This is awesome!

Thank you!

Wiebo de Wit · **Joined:** Mon Aug 09, 2004 7:51 am **Posts:** 9

You, sir, are a life saver. Downloading now and eager to get to work with it!!!!

Techx · **Joined:** Sat Sep 20, 2003 11:35 pm **Posts:** 78

This is great, thanks for putting the time into making it!

Docgalaad · **Posted:** Sat Sep 18, 2004 3:28 am

Amazing, i have two things to say:
- The lighting in the render view is now true, like ingame, awesome
- The visportals and other formerly black textures are now colored and this is great

I just had an issue with mirrors. Ingame there is the word mirror on all the mirror surfaces of my maps. So i have to disable ZZ-xxx.pk4 to see the final map properly.

A huge *thank you* for the massive work achieved.
I can imagine the task, so many notepad openings.

Cheers.

Eutectic · **Posted:** Sat Sep 18, 2004 6:22 am

Docgalaad wrote:

Amazing, i have two things to say:
- The lighting in the render view is now true, like ingame, awesome
- The visportals and other formerly black textures are now colored and this is great

I just had an issue with mirrors. Ingame there is the word mirror on all the mirror surfaces of my maps. So i have to disable ZZ-xxx.pk4 to see the final map properly.

A huge *thank you* for the massive work achieved.
I can imagine the task, so many notepad openings.

Cheers.

You're very welcome. About the textures/common/mirror material, I found the reason why. Here's the material code:

Code:

textures/common/mirror
{
   discrete      // never merge with other surfaces
   qer_editorimage textures/common/qer_mirror.tga
   solid
   mirror
   {
      blend add
      map textures/common/qer_mirror.tga
   }
}

The TGA file "textures/common/qer_mirror.tga" is not present in the original game's pak004.pk4 , therefore you don't get this problem in the original game. The problem with this material is that that TGA image is used as a blendmap in the original code. It's not the qer_editorimage that causes this but the blend add stage.

Incidentally, I didn't create this image, my predecessor did. But ultimately it's my fault. I didn't test the textures/common materials thoroughly enough assuming there couldn't be anything wrong about those since they're so simple and straighforward.

I will fix that by renaming the qer_mirror.tga to something else and edit the qer_editorimage line to point to the renamed image instead. I won't change the blend add stage of course - the idea is that it must NOT find the TGA file it points to. The shader probably needs a blend add stage pointing to an inexistent texture to work properly (at least that's what I'm guessing). In any case, I musn't change the original shader code, I have to work around it.

The only downside is that you will get a "warning: textures/common/qer_mirror.tga not found" message when you load the material in the editor. But you won't see a "mirror" texture in your compiled maps anymore.

Oh well.... that's why I gave that editing pack Version numbers. Thanks for pointing out the booboo Docgalad. I will test all the textures/common materials throroughly this time and post a Version 2 ASAP.

UPDATE:

I checked all the textures/common and textures/editor materials in a compiled map and they all work. I uploaded the fixed Version 2 and updated the link in the top post.

indianajonesilm · **Joined:** Thu Sep 16, 2004 7:41 am **Posts:** 31

WOW!!!!

I would just like to say THANK YOU to all involved in making this. I now know why my Bloody Bootprints were not showing up in game! Thank you for all your hard work. WOW!

Did I forget to say "WOW"!!!

Eutectic · **Posted:** Thu Sep 16, 2004 10:06 pm

[EDIT] New URL

http://www.pcgamemods.com/mod/9082.html

==============================

It's done.

This is a follow-up of Jafo's d3weditor clean shaders/materials pk4 file which served as a starting base for this new PAK. I won't print the complete stats here since those are included in the zip file (along with a readme file). However, here's a quick overlook:

66 materials commented out in Jafo's PAK were in fact good.
53 materials in Jafo's PAK were in fact broken.
These materials were uncommented/commented out accordingly.

But the main difference lies in the fact tht this new PAK has 193 new TGA's to provide for qer_editorimages that were either missing or did not adequately depict what the texture really looks like in the game. Some of you who are currently designing maps in DoomEdit may think this PAK is just eye candy. If so, then consider these figures (compiled at the end of this project):

//=========== Global textures/_ materials stats==============
//
// Total # of textures/_ materials : 3708
// Total # of working shaders: 1950 (approx. 52.5%)
// Total # of Broken/CommentedOut shaders: 1614 (approx. 43.5%)
// Total # of shaders which can't be used for map texturing and kept by necessity: 144 (approx. 4%)
//==============================================

Now I noticed that many of the materials in the original .mtr files can be misleading. Those may seem to be working but are really broken because the material code calls for a single non-existent TGA. The result is a texture that will display on your brush/patch in the game but won't look right (for eg. a material in which only the specularmap parameter refers to a TGA file that doesn't exist while the bump and diffuse map TGA's do exist).

That means there's a significant chance that you might unknowingly be using broken materials to texture your map's geometry. So this PAK not only improves the look and ease of use of DoomEdit's texture window, it also ensures that you use only 100% working materials to texture your maps.

DoomEdit CleanMaterials Version 5
(approx 13MB download)

Notes:
- Version 2 has fix for qer_mirror texture appearing on mirrors in game.
- Version 3 fixes the demon spawndecal not appearing in game.
- Version 4 adds the 6 new materials in the V1.1 game patch plus a cosmetic issue with the editorimage textures/editor/redge.tga. Please note that these new materials are not meant to be used for map texturing. They were added so that my PAK won't break the new chat and lag icons in the V1.1 patched game when playing in MP mode. That's the ONLY real change in the V4 CleanMats.
- Version 5 is the final cleanup phase. All the remaining materials have now been cleaned up (models, light, fog, fx's, gui's, particles, etc.). I also improved the qer_editorimage for model based entities in CAM view while in skinned mode. Most monsters/NPC's displayed their displacement map as the editorimage by default. Static models often used their addblend map by default (which made them appear pitch black). Most now use the _local bumpmap which improves visibility and clarity in skinned mode.

- There are no new TGA files in this pak so it's the same size as the last version.

A few broken materials for the sentry character reside in the sentry.def file so you need to download my latest Clean def's PAK to make this 100% complete. Please check the "Editing resources" sticky post in this forum for the URL of the "Clean def's" thread

PS: Mods please update links in other posts to point to this one (if required). Thanks.
[EDIT]new url. kat

zeh · **Posted:** Thu Sep 16, 2004 10:08 pm

http://www.doom3world.org/phpbb2/viewtopic.php?t=6012

Eutectic · **Posted:** Thu Sep 16, 2004 10:14 pm

Oops... missed that completely. Looks like BNA beat me to the punch :wink:

AEon · **Joined:** Mon Aug 18, 2003 4:05 am **Posts:** 127

Eutectic,
first off wonderful job...

One thing I have been wondering is this.

How will maps using this pack work on a clean (non-development) install of D3. In Q3A there where several special textures provided with GTKradiant editing, that where not part of the clean retail install, thus missing on those machines.

I guess all the preview images you created from scratch will not be the problem, since these are editor only. But did some of the shaders e.g. have to be changed to differ from the originals?

funcrusher · **Joined:** Sat Aug 21, 2004 7:22 pm **Posts:** 238

AEON - if this works as it should, there should be no problem with distributing a map created with the help of these files. If I understand correctly this pak shouldnt alter the paths to the textures in the .map file - and qer_editorimage images dont matter for final output - they are never displayed in game.

bb_matt · **Posted:** Fri Sep 17, 2004 7:49 am

I've sticky-fied this thread !

Eutectic · **Posted:** Fri Sep 17, 2004 8:23 am

AEon wrote:

Eutectic,
first off wonderful job...

One thing I have been wondering is this.

How will maps using this pack work on a clean (non-development) install of D3. In Q3A there where several special textures provided with GTKradiant editing, that where not part of the clean retail install, thus missing on those machines.

Thanks

Maps made while having this PAK enabled will work just fine in the standard plain-jane Doom3 game. I did not add any new shaders/materials in the mtr files. All I (and Jafo) did was to comment out the broken materials so they don't get parsed by the editor, that's all.

Quote:

I guess all the preview images you created from scratch will not be the problem, since these are editor only.

That's right. The TGA file that the qer_editorimage parameter points to affects only what you see in the editor's texture window and in the CAM view. It has no effect on the the material in the game itself.

Quote:

But did some of the shaders e.g. have to be changed to differ from the originals?

Absolutely not. That would have been the worst thing to do and I made it a point to never do that. All the shaders' code were left intact and original. My goal was not to "repair" anything. My goal was simply to sort out which materials really work and which ones don't work. The ones that don't work were commented out, the ones that DO work were left untouched except for the qer_editorimage to improve how it looks in the Texture window. And that's all there is to it.

Brain Trepaning · **Posted:** Fri Sep 17, 2004 3:48 pm

Thanks a lot, this will be very helpful for many mappers. I know I have my copy!

weak · **Posted:** Fri Sep 17, 2004 4:16 pm

thx a lot!

[--TeK--] · **Posted:** Fri Sep 17, 2004 4:34 pm

A big thx to you and Jafo for the good job...very helpful

RonHiler · **Posted:** Fri Sep 17, 2004 4:48 pm

Question:

I have D3 completely unpacked for mapping purposes. I downloaded the pk4 and put it into base, but the editor is not reading it.

Is it true that the editor cannot mix unpacked with packed? I ran into this same problem with .def files (I had D3 packed and it wasn't reading my custom .def files, which is what prompted me to unpack them in the first place). Once I had unpacked the D3 files, my own def files read fine. It seems like I've hit this issue again.

So bascially the question is, do I have to unpack the clean materials in my unpacked directory for them to read?

Ron

rich_is_bored · **Posted:** Fri Sep 17, 2004 5:43 pm

That may work.

But, I'd advise that if you need to extract the vanilla pk4s for reference then you extract them to somewhere outside the Doom 3 folder. This way you don't have to worry about problems like this where something that should work doesn't.

goliathvt · **Joined:** Sun Jan 18, 2004 9:41 pm **Posts:** 2116

Outstanding work!

Thanks guys!

G

Origin73 · **Posted:** Fri Sep 17, 2004 6:24 pm

This is awesome!

Thank you!

Wiebo de Wit · **Joined:** Mon Aug 09, 2004 7:51 am **Posts:** 9

You, sir, are a life saver. Downloading now and eager to get to work with it!!!!

Techx · **Joined:** Sat Sep 20, 2003 11:35 pm **Posts:** 78

This is great, thanks for putting the time into making it!

Docgalaad · **Posted:** Sat Sep 18, 2004 3:28 am

Amazing, i have two things to say:
- The lighting in the render view is now true, like ingame, awesome
- The visportals and other formerly black textures are now colored and this is great

I just had an issue with mirrors. Ingame there is the word mirror on all the mirror surfaces of my maps. So i have to disable ZZ-xxx.pk4 to see the final map properly.

A huge *thank you* for the massive work achieved.
I can imagine the task, so many notepad openings.

Cheers.

Eutectic · **Posted:** Sat Sep 18, 2004 6:22 am

Docgalaad wrote:

Amazing, i have two things to say:
- The lighting in the render view is now true, like ingame, awesome
- The visportals and other formerly black textures are now colored and this is great

I just had an issue with mirrors. Ingame there is the word mirror on all the mirror surfaces of my maps. So i have to disable ZZ-xxx.pk4 to see the final map properly.

A huge *thank you* for the massive work achieved.
I can imagine the task, so many notepad openings.

Cheers.

You're very welcome. About the textures/common/mirror material, I found the reason why. Here's the material code:

Code:

textures/common/mirror
{
   discrete      // never merge with other surfaces
   qer_editorimage textures/common/qer_mirror.tga
   solid
   mirror
   {
      blend add
      map textures/common/qer_mirror.tga
   }
}

The TGA file "textures/common/qer_mirror.tga" is not present in the original game's pak004.pk4 , therefore you don't get this problem in the original game. The problem with this material is that that TGA image is used as a blendmap in the original code. It's not the qer_editorimage that causes this but the blend add stage.

Incidentally, I didn't create this image, my predecessor did. But ultimately it's my fault. I didn't test the textures/common materials thoroughly enough assuming there couldn't be anything wrong about those since they're so simple and straighforward.

I will fix that by renaming the qer_mirror.tga to something else and edit the qer_editorimage line to point to the renamed image instead. I won't change the blend add stage of course - the idea is that it must NOT find the TGA file it points to. The shader probably needs a blend add stage pointing to an inexistent texture to work properly (at least that's what I'm guessing). In any case, I musn't change the original shader code, I have to work around it.

The only downside is that you will get a "warning: textures/common/qer_mirror.tga not found" message when you load the material in the editor. But you won't see a "mirror" texture in your compiled maps anymore.

Oh well.... that's why I gave that editing pack Version numbers. Thanks for pointing out the booboo Docgalad. I will test all the textures/common materials throroughly this time and post a Version 2 ASAP.

UPDATE:

I checked all the textures/common and textures/editor materials in a compiled map and they all work. I uploaded the fixed Version 2 and updated the link in the top post.

indianajonesilm · **Joined:** Thu Sep 16, 2004 7:41 am **Posts:** 31

WOW!!!!

I would just like to say THANK YOU to all involved in making this. I now know why my Bloody Bootprints were not showing up in game! Thank you for all your hard work. WOW!

Did I forget to say "WOW"!!!

Doom 3 world