Forum posts
I didn't say it was, but thanks for the info, I didn't know that.
Do you have a .res file?
Put a .res file (basically a txt file but res extension) and name it exactly like the map. In it put the locations of the files you want to be downloaded with the .bsp
Put a .res file (basically a txt file but res extension) and name it exactly like the map. In it put the locations of the files you want to be downloaded with the .bsp
Wonderful. Thank You.
With the camera view I used to see quite a long distance without it becoming black at a certain range. But now, for some reason, the distance became a lot shorter, anyone know why? anyone know how to fix it? Its really annoying, I have to go close to the stuff I wanna see and select.
Thanks
Thanks
Well I don't know anything about batch compilers but if you just wanna compile a .bsp with all the textures included in it, use ZHLT. Thats what I use, and for the .bat file put "hlcsg -nowadtextures".
I don't know if Nems compiler worked for you, the link worked for me, but if you decide to use ZHLT and want more info, just say so and I'll explain.
I don't know if Nems compiler worked for you, the link worked for me, but if you decide to use ZHLT and want more info, just say so and I'll explain.
Oh thank you thank you. I'll do that.
Does anyone know why that exactly happens though?
Does anyone know why that exactly happens though?
I have a few rotating objects around my map, not all them are fans but they are all set to kill upon impact.
For some reason players get killed at certain locations around the rotators, while not obstructing them. Sometimes walking on or moving around the rotating objects' enclosures kills you.
Anyone know why?
Also, I thought about removing the fan pain and just adding a trigger_hurt, but then where you used to get killed you just hear object-obstructing noises and the rotating object stops because its being obstructed.
For some reason players get killed at certain locations around the rotators, while not obstructing them. Sometimes walking on or moving around the rotating objects' enclosures kills you.
Anyone know why?
Also, I thought about removing the fan pain and just adding a trigger_hurt, but then where you used to get killed you just hear object-obstructing noises and the rotating object stops because its being obstructed.
I see, thanks.
Sometimes when I start editing vertices on brushes, weird things start happening. They aren't invalid solids. And somethings one face on the brush disappears (giving complie errors)
Heres an example http://i28.tinypic.com/2elyyw4.jpg
As you can see, the solid has a 'dent' (made by me) on the right side, yet the camera shows it being full.
Whats happening?
Heres an example http://i28.tinypic.com/2elyyw4.jpg
As you can see, the solid has a 'dent' (made by me) on the right side, yet the camera shows it being full.
Whats happening?
Is there a way to build a custom brush by, lets say, making a cube and adding vertices to it. For example, you can split a face, can you split a side and get an extra vertex to manipulate?
Actually I found out how. Nevermind. Sorry.
Actually I found out how. Nevermind. Sorry.
Thank you both, and thank you for the tutorials. It worked.
I made a 16x16 RGB:0,0,255 texture with '{' in the front of the name, put it in the wad with wally, used it on a brush, set it to func_wall Normal Solid FX255.
I still see it as a blue texture and not transparent.
If I use the originals (eg. rails) they work perfectly.
I also tried to make the texture in photoshop and indexed it too.
Any ideas?
I still see it as a blue texture and not transparent.
If I use the originals (eg. rails) they work perfectly.
I also tried to make the texture in photoshop and indexed it too.
Any ideas?
Hmmm, I added -notexscale to my .bat like so "hlrad -notexscale de_map", and it still has the same problem.
The compiling log did actually say that texscale was 'off'.
Any ideas?
Can someone please really quickly if this -notexscale method works?
(Just make a room, 'Fit' the textures on its surfaces and play it, does the flashlight illuminate the entire surface?)
The compiling log did actually say that texscale was 'off'.
Any ideas?
Can someone please really quickly if this -notexscale method works?
(Just make a room, 'Fit' the textures on its surfaces and play it, does the flashlight illuminate the entire surface?)
Why are you posting something for HL2 in the HL section. Wrong.
Hah, you, Stixmaster.
I was hoping it wouldn't come to that, but thanks for the help.
Well its not just limited to walls. I may make big boxs, and stretch the box textures on their faces, they'll still have this problem.
Hi,
When I make a huge wall in my map, or any surface, and then 'fit' the texture the flashlight always illuminates the whole wall. Now I know why, because the small texture has been stretched, is there any way around this, where the flashlight radius stays the same as normal?
Thanks,
Yousif.
When I make a huge wall in my map, or any surface, and then 'fit' the texture the flashlight always illuminates the whole wall. Now I know why, because the small texture has been stretched, is there any way around this, where the flashlight radius stays the same as normal?
Thanks,
Yousif.