Killer_Duck, in Hammer use the -wadinclude parameter in the command line, or just get a third party compiler.What!? I think you meant that for Kill_the_bug.
Forum posts
- Forums
- Posts
- Posted by
Killer-Duck
The largest recommended size of a texture is 256x256 pixels, you've probably gone over the limit with some of your textures. This is just a warning(not an error) and your map should compile fine anyway, but people with slow computers might not be able to play your map.
Either you have a leak or you've turned off RAD.
Wadfather has some textures.
Yes.
what? how come i need mine at least 38000, before they are decently lighted?You may be right on that, I haven't used them for a while...
Which texture are you trying to use?
Also, inside lights.rad the column most to the right is the one which controls the brightness of the texture-light, if it's set to 0 it will emit no light at all. Remember that texture-lights aren't as strong as point-entity-lights, while a light-entity lights pretty good with a 200 brightness-value the texture-light might need a brightness of at least 1000 to light up decently.
Also, inside lights.rad the column most to the right is the one which controls the brightness of the texture-light, if it's set to 0 it will emit no light at all. Remember that texture-lights aren't as strong as point-entity-lights, while a light-entity lights pretty good with a 200 brightness-value the texture-light might need a brightness of at least 1000 to light up decently.
The "~"-sign doesn't have anything to do with it(it's just used to more easily find light-textures in the texture-browser), any texture could give off light as long as it is referenced in the lights.rad. Furthermore not all "~"-textures in the halflife.wad is referenced in the lights.rad so you might need to add them in manually.
And make sure the lights.rad is placed in the same folder where your compiling tools are. I think its case-sensative so make sure you match the texture name EXACLTY.
And make sure the lights.rad is placed in the same folder where your compiling tools are. I think its case-sensative so make sure you match the texture name EXACLTY.
What kind of roofs do you want?
Does anything show up when you press Alt+P?
Here: http://nemesis.thewavelength.net/index.php?p=2 (The site seems to be down at the moment but should work again shortly, otherwise i think you can get the batch compiler from FPSBanana.)
As someone pointed out before, your hlbsp-process isn't running through correctly and therefore doesn't create a portal-file.
- Re-check your paths in the options and make sure everything is set up correctly.
- At run map(f9) make sure all tools are set to "Normal".
- Have you placed out correct entities?(a minimum would be a light and player-spawn)
- Re-download the compiling tools, the ones you've got may have got corrupted.
- Use some front-end compiler like Nems Batch Compiler.
Re-install Hammer to an shorter path, as it is now it seems to be installed on your desktop, install it in like C:maps and place the compile tools in the Hammer-folder.
If I remember correctly it could be because of both. Anyway, if this happens on all the maps he tries to compile then its probably set up-related, but if it happens only on this one then its probably mapping-related.
BTW, do you get this error with all maps you create or only this one?
If you're on Vista then it's probably because of shitty drivers.
The compile-tools should be placed in the same folder where Hammer Editor is installed.
What's your new compile-log?
Ah sorry, didn't read it all through! 
Hammer doesn't like long paths with spaces in them, try making a new folder with an shorter path like C:mapping and place all your stuff in there.
And also illegal.
Kille_the_bug, go to the folder where your compile tools are located, in there you should have a lights.rad-file, just open it up with Wordpad, there are a lot of tex-lights already added so you can just watch how they made it.
At "Run Map [Advanced]" uncheck the box "$game_exe..." and after the compile start up HL manually and load your map(with instructions I gave you above), does it work then?
Also, are there any errors in the compile-log?
Also, are there any errors in the compile-log?
How are you loading your map? Best is to check the "Don't run the game" at the compile-settings and then start up HL manually after compile and then starting up your map by writing "map name_of_your_map" in console.
Do you really need to include the lights.rad, I thought it was only used by hlrad during the compiling-process?
5 minutes isn't a very long time for compilation, a big map can take hours to compile.
Most errors will show up when you press Alt+P in Hammer, then it's just a matter of pressing the "Fix"-button.
Most errors will show up when you press Alt+P in Hammer, then it's just a matter of pressing the "Fix"-button.
Coplanar faces: http://www.slackiller.com/tommy14/errors.htm#coplane
Bad surface extents: http://www.slackiller.com/tommy14/errors.htm#badsurface
Bad surface extents: http://www.slackiller.com/tommy14/errors.htm#badsurface
leaks are a problem, however i have never found an effective way of dealing with them, other than boxing the map with hollow brush with texture scale of 40Find them and seal them.
At least it's more effective than enclosing your map in a giant box which will give your map bad performance.
Some thing you can do to reduce r_speeds:
? Apply NULL-texture to unseen brush-faces.
? Tie complex geometry like cylinders into func_wall.
If you're a bit more advanced mapper you can also make use of Hint-brushes.
I don't really understand what you said about sky-texture.
? Apply NULL-texture to unseen brush-faces.
? Tie complex geometry like cylinders into func_wall.
If you're a bit more advanced mapper you can also make use of Hint-brushes.
I don't really understand what you said about sky-texture.
"Map" --> "Load pointfile" and select the .lin-file.
In that map you uploaded there is only one leak and that one is caused by the light-entity outside the map, delete the light and you don't get any more leaks. But if you try to compile it again afterwards you still won't be able to get a complete compile because you will get an "MAX_PATCHES"-error, to fix this apply the NULL-texture to all unseen faces of your map, then you will be able to do a complete compile.
You could start with sealing the leak(s) so you actually can do a complete compile.
Go to the Dod-forums maybe?
It hasn't locked up it just takes a while to compile it. Make sure you don't run any programs in the background since the compile tools needs all of the RAM available to compile the map. You can also speed up the compile(as long as it is not a final compile) by setting VIS to "Fast".
Long compile times are often the result of a poorly built map. Make sure no brushes are overlapping, tie complex shapes (like cylinders) to func_wall, never use the carve-tool and don't create a giant skybox around your map.
Long compile times are often the result of a poorly built map. Make sure no brushes are overlapping, tie complex shapes (like cylinders) to func_wall, never use the carve-tool and don't create a giant skybox around your map.
If the pointfile do not work then you're doing something wrong.
It's actually pretty easy, load your map in Hammer, go "Map"-->"Load Pointfile" and load the .lin-file with the same name as your map. Then just follow the line and see where it goes outside your map, seal that place and do another compile, if you got more leaks just repeat the procedure. Also, to be able to see the pointfile in the camera-view(which makes it alot easier) you need to be using the VHE 3.5 BETA.
It's actually pretty easy, load your map in Hammer, go "Map"-->"Load Pointfile" and load the .lin-file with the same name as your map. Then just follow the line and see where it goes outside your map, seal that place and do another compile, if you got more leaks just repeat the procedure. Also, to be able to see the pointfile in the camera-view(which makes it alot easier) you need to be using the VHE 3.5 BETA.
FFS...
Remove the giant box around your map, that box makes vis choke.
Remove the giant box around your map, that box makes vis choke.
Have you tried compiling it without the -estimate-parameter?
Try to compile without the -estimate-parameter.
Get Steam and Steam-account. In Steam press on the "Activate a product on Steam..."-button then you're asked to write in the CD-key and then Half-Life will be available through Steam and auto-update itself to latest version.
Warning: More than 8 wadfiles are in use. (13)
This may be harmless, and if no strange side effects are occurring, then
it can safely be ignored. However, if your map starts exhibiting strange
or obscure errors, consider this as suspect.
A giant doughnut.
Most of the prefabs out there looks like shit. Make your own.
You've turned almost your whole map into func_wall, that's always a bad idea...
Could be related to you putting 2 layers of sky-brushes around your map. Remove the outer sky-brush-layer and you'll end up with a leak, seal it and the problem should be fixed.
Thanks for the replies, but I can't make a bombsight neither a func_rotating_door. :sThere are two types of entities in Hammer: brush-based and point-based entities.
Point-based entities(eg. light and player spawnpoints) are placed out anywhere on the map using the 'Entity Tool'-button.
Brush-based entities(eg. func_rotating_door and func_bomb_target) are created by tieing them to a brush. So you select an existing brush(or AAAtrigger-area) and press Ctrl+T on your keyboard and just select which entity it should be.
Glad I could help! 
I'm placing the maps in the following directory:Try remove them from that directory and place them in this one instead: C:Program FilesValveSteamSteamAppsdan492condition zeroczeromaps
C:Program FilesValveSteamSteamAppsdan492condit
ion zerocstrikemaps
Since no 3rd party maps work for you may I ask where you put them? Maybe you're placing them in the wrong directory or something?