Character/Flag Lighting Problem

[Kaveman Profile]

I've been having bit of a problem with custom mapping and was hoping somebody here could help. I have looked around the internet for a solution but haven't been able to find anything.



As you can see from above, character models and flags are lit strangely. The hue of the character lighting is at about 0 when facing west and increases as you rotate counter-clockwise. My map contains no lights.

My worldspawn settings are as follows:

Code: Select all

_color           .75 .84 1
ambient          0.05
classname        worldspawn
diffusefraction  0.35
northyaw         45
spawnflags       20
suncolor         1 .9 .9
sundiffusecolor  .75 .84 1
sundirection     35 300 0
sunlight         .8


... and my compiler settings:

Code: Select all

Compile BSP        Yes
Compile -vis       Yes
Compile Lighting   Yes
Connect Paths      Yes
Run Map When Done  No

fast               No
extra              Yes
verbose            Yes
ModelShadow        Yes
NoModelShadow      No
DumpOptions        No


Note: The problem was not visible on my brothers' computers. All other maps look fine on my computer.

[MajorFullWood Profile Website]

There's a few things you can try.
-The only difference between your settings and stock would be the sun direction. All stock start - (negative) but yours is positive. Add a minus symbol in front.
-Add a light to the map.
-Try making a grid: http://modsonline.com/Tutorials-read-341.html(you'll need to replace your file in cod2\bin though with this file when doing a grid, then replace it with the original when you do your next compile: http://halo.anarchic-x.net/fullwood/cod2compiletools_grid.bat)

Also, while you're testing, full setting aren't needed. http://modsonline.com/Tutorials-read-321.html

[Cornrow Wallace Profile]

-Try making a grid

I'd start there. The rainbow colors mean the compiler didn't have enough lighting info, creating a grid & compiling it in with your .map will fix it.

[MajorFullWood Profile Website]

That was my best guess since he doesn't have any lights, I just figured he could start small.

[Kaveman Profile]

Followed PrivateFullwood's links to make a grid. Worked beautifully. Thanks for the help guys!

[Cornrow Wallace Profile]

Yeah, he's good for something every once in a while.

Congrats on resolving the issue, now make an awesome map.

[MajorFullWood Profile Website]

Congrats on resolving the issue, now make an awesome map.

[Kaveman Profile]

I hate to be a pest, but it seems I have ran into another problem:



Reinstalling both COD2 and Radiant didn't fix anything. I can't find this "images" folder it talks about (I did find a "Docs/TechHelp/images", but I don't think it's talking about that).

[Cornrow Wallace Profile]

Is your Call of Duty 2/main folder clean? "Clean" meaning only stock files? That file doesn't seem to be a stock file.

[Kaveman Profile]

Aside from some Anarchic X .iwds, yes. Though I did clean out some maps from servers I don't visit anymore a couple of days ago. Is it looking for a texture that was in one of those .iwds that I deleted?

[Cornrow Wallace Profile]

It's possible. Radiant is searching for the image (iwi) but isn't finding it, so that means there must be a material file somewhere that's telling Radiant to find the corresponding image.

Can you show me a printscreen of your Call of Duty 2 folder (not main) or write a list of folders in it?

[GER-Iceman Profile]

Aside from some Anarchic X .iwds, yes. Though I did clean out some maps from servers I don't visit anymore a couple of days ago. Is it looking for a texture that was in one of those .iwds that I deleted?

remove the custom IWD's from your folder, there are some textures in custom maps that crash the radiant, unfortunately also in some of the custom maps on our server , The error you post above is cause by q8.iwd.

an additional point of removing all custom files before mapping is that only this way you have nothing more then the pure CoD2 textures and don't run in missing texture problems or unpure files later

[MajorFullWood Profile Website]

I might be one of the few who do it, but I recommend making a second folder solely dedicated to mapping. That is, if you're a frequent enough gamer.

[GER-Iceman Profile]

I might be one of the few who do it, but I recommend making a second folder solely dedicated to mapping. That is, if you're a frequent enough gamer.

I simply created a folder "custom_maps" in my main folder and move all custom maps to it before I open radiant. When I want to play I simply move them back. 1 mouse click and done in seconds without using additional hdd space for a second install of the game.

[Kaveman Profile]

The error you post above is cause by q8.iwd.

Thanks Iceman, removed q8.iwd and it works fine now.

Can you show me a printscreen of your Call of Duty 2 folder (not main) or write a list of folders in it?

Just in case you still want it...

I simply created a folder "custom_maps" in my main folder and move all custom maps to it before I open radiant. When I want to play I simply move them back. 1 mouse click and done in seconds without using additional hdd space for a second install of the game.

I like that idea, I'll try it.

[Cornrow Wallace Profile]

removed q8.iwd and it works fine now.

This is what I meant about making sure your /main is kept clean. Having custom stuff in there can cause these kinds of problems, it's best to work without anything but your materials being loaded, that way it's much easier to track down problems such as this.

[MajorFullWood Profile Website]

Maybe I was confused on something. Does Radiant only go through your Main folder? I thought it went through the whole CoD2 folder.

[GER-Iceman Profile]

Maybe I was confused on something. Does Radiant only go through your Main folder? I thought it went through the whole CoD2 folder.

it don't reads all subfolders so mod folders and also additional folders inside the mainfolder are ignored

[MajorFullWood Profile Website]

Hey, I learned something new, too!