So I'm starting a map here using but have ran into a few problems that I can't figure out how to fix. The first is with fog. The two selected brushes here are fog
http://ohshi.dyndns.org/testingground/work/sewer1.jpg
Here is how the two are appearing in-game. I can't figure out what I'm supposed to do to the two sides to make them act as a single entity
http://ohshi.dyndns.org/testingground/work/sewer2.jpg
http://ohshi.dyndns.org/testingground/work/sewer3.jpg
And here is the last problem I'm having. I'm not sure what shader I'm supposed to apply to the side of this fence brush that will keep player from walking through it but will allow players to shoot through it. Is this possible?
http://ohshi.dyndns.org/testingground/work/sewer4.jpg
A couple simple problems I'm having
fog can only be one brush, can't be two brushes touching. There is much more detailed info in the manual of Gtk, and someone else could explain better...
As for the fence, put a player clip in the common folder over the fence...that should fix your problem.
As for the fence, put a player clip in the common folder over the fence...that should fix your problem.
Last edited by bork[e] on Thu Jun 30, 2005 9:44 pm, edited 1 time in total.
-
eepberries
- Posts: 1975
- Joined: Mon Jan 24, 2005 10:14 pm
I think the reason I gave up on shaders when I started this was because I tried to take the complete article in in one setting. I kinda wanted to get it out of the way and under my belt but after about 30 minutes of all those shader terms I didn't understand, I closed my browser and...here I am. 
I haven't even attempted to make/alter any so I might here soon hearing that.
I haven't even attempted to make/alter any so I might here soon hearing that.
I think there was a workaround... copy the nodraw shader and rename it to "nodrawfog". Then add surfaceparm fog. Then texture the faces between fog volumes with your new nodrawfog shader. I think that's the way it worked... haven't needed to do this in a while. There were still some limitations, IIRC - fog volumes still had to be axial and same height or something. Anyway, play around with it and see if it works.
Generally, you would just create a single large fog volume, but there are some cases where you need very localized fog where you would then need the special nodrawfog shader.
On learning how to write shaders, it's definitely easier than you think. It's certainly not like you need programming experience or anything. It's basically a list of parameters.
Download Q3ASE, and play around with it. It lets you see most of the changes that are caused by editing the shader in real-time. So you can add a directive like tcMod rotate and it will actually preview your shader with a rotating texture. Just note that Q3ASE is a little outdated and it's no longer in development. Some Q3Map2 features aren't available. Because of this, I write all my shaders directly in Textpad, but Q3ASE is still useful as a learning tool.
By the way, since you guys are new to shaders, any suggestions that you can recommend for the shader manual to make it easier for newbies?
Downloads:
Q3ASE
Textpad Syntax file I wrote (textpad_shader_040713.zip)
Generally, you would just create a single large fog volume, but there are some cases where you need very localized fog where you would then need the special nodrawfog shader.
On learning how to write shaders, it's definitely easier than you think. It's certainly not like you need programming experience or anything. It's basically a list of parameters.
Download Q3ASE, and play around with it. It lets you see most of the changes that are caused by editing the shader in real-time. So you can add a directive like tcMod rotate and it will actually preview your shader with a rotating texture. Just note that Q3ASE is a little outdated and it's no longer in development. Some Q3Map2 features aren't available. Because of this, I write all my shaders directly in Textpad, but Q3ASE is still useful as a learning tool.
By the way, since you guys are new to shaders, any suggestions that you can recommend for the shader manual to make it easier for newbies?
Downloads:
Q3ASE
Textpad Syntax file I wrote (textpad_shader_040713.zip)
[size=85][url=http://gtkradiant.com]GtkRadiant[/url] | [url=http://q3map2.robotrenegade.com]Q3Map2[/url] | [url=http://q3map2.robotrenegade.com/docs/shader_manual/]Shader Manual[/url][/size]
Re: A couple simple problems I'm having
Add surfaceparm nonsolid to the grill shader, then cover the fence with playerclip. Even the bots will shoot through that.eepberries wrote:And here is the last problem I'm having. I'm not sure what shader I'm supposed to apply to the side of this fence brush that will keep player from walking through it but will allow players to shoot through it. Is this possible?
http://ohshi.dyndns.org/testingground/work/sewer4.jpg
-
SonicClang
- Posts: 209
- Joined: Sun Mar 28, 2004 8:00 am
Hey I'm on vacation all next week too!bork[e] wrote:I'm on vacation all next week and only a one day trip planned with the g/f. I'll spend a good deal a time on the computer next, I'll read the your guide again and see if I can't help ya out there.
cheers to us!The number 1 cause of death in games is panic.
[img]http://webpages.charter.net/sonicclang/small.jpg[/img]
[img]http://webpages.charter.net/sonicclang/small.jpg[/img]
-
eepberries
- Posts: 1975
- Joined: Mon Jan 24, 2005 10:14 pm
That grid texture is hard-coded into Q3. It's basically telling you that Q3 can't find the texture/shader that you are using in the map, so it's displaying this as a default instead.
Check your texture/shader file paths.
Check your texture/shader file paths.
[size=85][url=http://gtkradiant.com]GtkRadiant[/url] | [url=http://q3map2.robotrenegade.com]Q3Map2[/url] | [url=http://q3map2.robotrenegade.com/docs/shader_manual/]Shader Manual[/url][/size]
as said before, pull down the console with ` and use page up/down to find the error. You should be looking for yellow text near the bottom, something like "warning: cant find isuckcock/cumonmytits.tga". That tells you the texture name.
Now, from the looks of your editor shot, the texture is fine. But GTK and Rad dont show shaders in the editor, so its your shader for sure. The yellow text in the console will tell you what you did wrong for your shader, but if you cant fix it, just post it here and somebody will fix it for you so that it works. Its possible you pointed to the wrong texture, gave a different blend, or maybe even added a few to many }'s, its a simple mistake to make.
Howeve,r "honestly", that texture does look like its worthless to use a shader. A shiney effect would load from alpha, but it would need to be VERY faint otherwise in that spot it would look wrong.
Now, from the looks of your editor shot, the texture is fine. But GTK and Rad dont show shaders in the editor, so its your shader for sure. The yellow text in the console will tell you what you did wrong for your shader, but if you cant fix it, just post it here and somebody will fix it for you so that it works. Its possible you pointed to the wrong texture, gave a different blend, or maybe even added a few to many }'s, its a simple mistake to make.
Howeve,r "honestly", that texture does look like its worthless to use a shader. A shiney effect would load from alpha, but it would need to be VERY faint otherwise in that spot it would look wrong.
-
eepberries
- Posts: 1975
- Joined: Mon Jan 24, 2005 10:14 pm
I didn't use any shaders though 
. One thing I did notice though it that once compiled, it created a folder under maps called "sewer2" (name of the map) containing the files lm_0000.tga and lm_0001.tga. Am I supposed to do something with these?
Also, when it loads the map, there isn't anything in yellow but near the bottom it says
trying levelshots/sewer2.tga
trying sewer2/A1382qyutraweh89fqwgh.tga <-not actual filename, but you get the point
etc
etc
etc
. One thing I did notice though it that once compiled, it created a folder under maps called "sewer2" (name of the map) containing the files lm_0000.tga and lm_0001.tga. Am I supposed to do something with these?Also, when it loads the map, there isn't anything in yellow but near the bottom it says
trying levelshots/sewer2.tga
trying sewer2/A1382qyutraweh89fqwgh.tga <-not actual filename, but you get the point
etc
etc
etc
-
^misantropia^
- Posts: 4022
- Joined: Sat Mar 12, 2005 6:24 pm
What. Sure they do. (Unless I'm misunderstanding what you mean or something...) The shaders have a white border around them in the texture window.o'dium wrote:GTK and Rad dont show shaders in the editor
I'm guessing those are alternate/switchable lightmaps that were created for a particular part of the map. You can set up q3map2 to use lightstyles (i.e. lights in a map that blink or switch on and off, that sort of thing), and when you do, the compile creates a separate file for these altered lightmaps.eepberries wrote:it created a folder under maps called "sewer2" (name of the map) containing the files lm_0000.tga and lm_0001.tga. Am I supposed to do something with these?
Are you using some sort of flickering or blinking light somewhere in the map? If so, there would be a "style" key on the light (and there should be a "_style*" key or keys in the worldspawn to tell the compiler exactly what to do for that style).
I'm not sure if your missing texture is related to the above problem or not, but if not, my guess is that you picked a shader-fied concrete from the texture menu for those walls (instead of just the concrete texture), and it's a shader that's fucked up somehow and/or references a texture that you don't have.
Do you have "shaderlist.txt only" checked (under the "Textures" menu...in 1.4 anyway)? You should if you don't. It will prevent you from:
a) picking textures/shaders that are broken.
b) picking stuff from random maps in your baseq3 and then not being able to figure out where it came from.
Hope this helps.
I beat the internet; the end guy is hard.
pjw, what i mean is that shaders dont show up in the editor. Yes, they show up, but you cant see them in action while browsing textures.
So yeah, you get textures with a box around them to tell you a shader is on this texture, but it wont sit there wiggling about if you gave it a wiggly shader :P It simply draws a pic that the shader tells it to, here.
So yeah, you get textures with a box around them to tell you a shader is on this texture, but it wont sit there wiggling about if you gave it a wiggly shader :P It simply draws a pic that the shader tells it to, here.