Okay, sounds good. I'm sorry to seem like such a newbie, but what exactly is texture lighting? Is that just getting the texture light and making it an ent?Texture lights are textures that emit light in-game. If you go into the folder where you got the compile tools you should have a file called lights.rad, you can open up that file with a text-editor like Notepad. The file lists all textures that should emit light. You can add or remove textures in the list to control which textures should emit light.
Forum posts
- Forums
- Posts
- Posted by
Killer-Duck
Are you using latest version of Zoner? (3.4)
Also, post compile log.
Also, post compile log.
Use the point-file to find leaks, "Map" ---> "Load Pointfile" and load the .lin-file with the same name as your map. Follow the line and see where it goes outside the map.
If I were you I would delete that map and start over again. The map is really shabby. And are players supposed to be able to go under the map? If not, you should try to make a better sky:
That will improve performance and shorten compile time.
And why did you make the ground 1 unit thick!? I see no reason for doing that, it just makes aligning brushes a nightmare having to zoom in/out all the time.
As I said before, compile the map with VIS and RAD on. Without VIS the game will render the whole map at once, which in your case, probably causes the game to choke.
And why did you make the ground 1 unit thick!? I see no reason for doing that, it just makes aligning brushes a nightmare having to zoom in/out all the time.
As I said before, compile the map with VIS and RAD on. Without VIS the game will render the whole map at once, which in your case, probably causes the game to choke.
Was that the whole compile log? Where's vis and rad?
How are you compiling the map, from Hammer or by using a batch-file? You should compile with a batch-file, that way, Hammer doesn't need to run in background which will free up some RAM for the compile tools to use instead.
You forgot to run hlvis.
Oh noes!
Create a trigger (e.g. trigger_multiple) inside the func_breakable (make sure people can't reach it while the box is still solid), set the trigger_multiple to trigger the gpe (don't forget to check the "Use only"-flag in the gpe).
func_breakable has a "Spawn on break" if I remember correctly, use that to set whatever weapon should spawn when it breaks.
gpe doesn't seem to work with func_breakable, although it seems to work perfectly fine with "trigger_"-entities. (don't forget to check the "Use only" flag in the gpe)
gpe doesn't seem to work with func_breakable, although it seems to work perfectly fine with "trigger_"-entities. (don't forget to check the "Use only" flag in the gpe)
I think this is even better:Depends on the situation/map, too low sky will give troubles when the players want to throw grenades high in the air. The middle sky-brush could be a good idea as long as players can't get up there.
This one has been brought up numerous times before, but this time it comes with some visual stimulation:
(The right one is how a correct sky should be created.)
More tutorials:
http://www.countermap2.com/Tutorials/tutorial1e85.html?id=54
http://www.countermap2.com/Tutorials/tutorial0b30.html?id=2
And a tutorial about pyramid-shaped hint-brushes: http://home.comcast.net/~ninjagrinch/pyramidhint.htm
http://www.countermap2.com/Tutorials/tutorial1e85.html?id=54
http://www.countermap2.com/Tutorials/tutorial0b30.html?id=2
And a tutorial about pyramid-shaped hint-brushes: http://home.comcast.net/~ninjagrinch/pyramidhint.htm
The editable project-file for awp_l337sk337 is available to the public: http://www.superjer.com/awp_l337sk337.php
So btw, what's that command useful for ?Command reference
If you're using Win XP there's a better solution: http://www.twhl.co.za/wiki.php?id=1072
4.In Wally: "Wizard" ---> "WAD Merge"
2. The "Lip"-value in func_door controls how far the door moves. '0' is default and means it travels its own full length in a direction. A higher positive value will make the door travel shorter and a negative value will make it travel farther than its own length.
4. It's in zhlt.wad, you usually get that wad together with the ZHLT compiling tools, place the wad in your cstrike-folder then add it in Hammer.
5. By default the player will face "east" in the "top (x/y)"-view. Change the Yaw-vaule to make them face another direction.
4. It's in zhlt.wad, you usually get that wad together with the ZHLT compiling tools, place the wad in your cstrike-folder then add it in Hammer.
5. By default the player will face "east" in the "top (x/y)"-view. Change the Yaw-vaule to make them face another direction.
What version of Hammer are you running? As long it is 3.4 or later it should work. If not, you're installing the fgd incorrectly, as I said earlier:
Then you didn't install it correctly. You need to unzip all the contents of the zip-file into your Hammer "root"-directory.
Doesn't latest version of Half-Life support env_rain?
Maybe it's something with the door? You want the door to open upwards, right? Then you need to go into the properties of your func_door, under the black "Yaw"-compass you got a little drop-down menu, choose "Up" there.
yeah, but when/if I manage to get this to work I'll...Take it one step at a time, you have to learn how to walk before you can run. If you don't have a game_team_master yet then you should not give the buttons a targetname yet.
zhlt_invisible should be 0, or do you want the buttons to be invisible? :S
Also, don't give them a targetname.
Also, don't give them a targetname.
You probably wrote in the wrong file-path to the model in your cycler_sprite. You have to use relative paths, e.g. if you have a model in:
C:\...\Valve\Steam\SteamApps\xxx\counter-strike\cstrike\models\pine_tree.mdl
then the filepath to the model in your cycler_sprite should say: models/pine_tree.mdl
C:\...\Valve\Steam\SteamApps\xxx\counter-strike\cstrike\models\pine_tree.mdl
then the filepath to the model in your cycler_sprite should say: models/pine_tree.mdl
Too much detail, VIS is choking. Overall, you need to make the geometry less complex.
What have you entered in the properties of your func_button?
erm... that's exactly what I didNo, in the map you posted, the buttons target a multi_manager. Why not just target the gate directly?
Could you post the compile log?
I can't reproduce the buggy lightning when compiling/running the map on my machine. Are you sure all four compile tools(CSG,BSP, VIS and RAD) are running correctly? And what version of ZHLT are you compiling with? (I used ZHLT 3.4 final with all the compiling tools set to 'Normal')
I tried both of them, still only have coloured blocks to show ent's.Then you didn't install it correctly. You need to unzip all the contents of the zip-file into your Hammer "root"-directory.
About the "empty entity"-error: "Map"--->"Entity report...", at the "Filter"-settings choose "Brush-entities" and then just select the first entity in the list and press the "Go to"-button, the entity should get selected in the 2D/3D-views, if nothing gets selected then that entity is "empty" and can be deleted(press the "Delete"-button).
Is it a custom texture?
It looks like your hammer/wally windows are showing through to the game screen?Uh... I think he edited the pictures in an image-editing program(MSPaint, Photoshop, etc) intentionally so all relevant information would be in one picture...
Also, check the console for any errors when the map has loaded.
OpenGL is the recommended graphical-mode for Half-Life and I think that is what most people use.
Also, this might as well be a hardware/driver-problem on your side as I don't see any big differences between D3D and OpenGL.
Also, this might as well be a hardware/driver-problem on your side as I don't see any big differences between D3D and OpenGL.
Post your zhlt-compile log...
It means im already using zhlt and I still have my problem, i'll try to post some pictures of my build configurations and build programmesPost your compile log instead.
Edit: I just downloaded the compile tools and Im already using zhlt to compile my gameShould we take this as you've fixed your problems?
Also, ZHLT compiles your map, not your game.
Do you have multiple hard drives? This can sometimes confuse the compile-tools. If you have multiple hard drives, move the compile tools to the same hard drive you have the game installed. (Then you of course need to change Hammer's settings in the "Build programs"-tab so the filepaths point correctly to the new location of the tools.)
Of course you need to change all your settings so Hammer points to Steam HL, Hammer 3.5 doesn't auto-configure itself like Hammer 4 does...
Killer-Duck, use the compilator.No, I don't.
How to autostart Steam-CS after compile: In Hammer, go "Tools" ---> "Options...", the tab "Build Programs", make sure "Game Executable" points to Steam.exe
Then when you wan't to compile your map in Hammer, go "File"--->"Run"(F9), then enter Expert compile mode by pressing the "Expert"-button(it only works in Expert-mode!). Under "Compile/run commands" select "?game_exe" in the list and add:
"-applaunch 10 +map $file" in the "Parameters"-box. Then just press "Go!" to compile.
Then when you wan't to compile your map in Hammer, go "File"--->"Run"(F9), then enter Expert compile mode by pressing the "Expert"-button(it only works in Expert-mode!). Under "Compile/run commands" select "?game_exe" in the list and add:
"-applaunch 10 +map $file" in the "Parameters"-box. Then just press "Go!" to compile.
The lightning maybe is because you have different brightness-settings in the games?
How many wads have you added in Hammer?
http://zhlt.info/other-software.html
"Optimizes the entities in compiled maps, allowing you to include more entities and also reduce network traffic."
"Optimizes the entities in compiled maps, allowing you to include more entities and also reduce network traffic."
Maybe this? http://www.speedyshare.com/115239952.html
But in the hlbsp parameters has only the "$file$path"...Could you post a screenshot of your expert-compile settings?
** Executing...You've fucked up the parameters for hlbsp.
** Command: C:\ARQUIV~1\VALVEH~1\tools\hlbsp.exe
** Parameters: "cs_conutc:\arquivos de programas\valve hammer editor\tools"
It failed me a month ago. It didn't help a shit.Then you don't know how to use it properly.