Forum posts
- Forums
- Posts
- Posted by
Killer-Duck
What is "Pitch Yaw Roll" set to?
Too many wads?
Turn on the -chart flag for hlbsp. Then look at the clipnode-statistics.
http://data.fuskbugg.se/skalman02/clipnode.gif
http://data.fuskbugg.se/skalman02/clipnode.gif
Try compile with an older version of ZHLT. (eg. 2.53r17 can be found here: http://www.superjer.com/learn.php )
Are you sure hlrad has crashed, do you get and actual error message?
Compiling a map can take a long time and sometime Windows erroneously reports the compile tools as "not responding".
Compiling a map can take a long time and sometime Windows erroneously reports the compile tools as "not responding".
Like Soup Miner says, do it in Wally: http://www.egir.dk/index.php?page=wal_transparent/wal_transparent.html
I've set up my Hammer something like this:
Tools--->Options-->Build Programs--->Game executable: C:\Program Files\Steam\Steam.exe (make it point to your steam.exe)
Then when you are about to compile the map, at the "Normal" compile-window under "Additional game parameters:" write: -applaunch 70 +developer 1
(You can add additional game parameters after the applaunch-part, in this case I've set dev mode to 1...)
Then press OK to compile and the game should start your map after compile. Although I think the Steam-client must already be running in background for it to work properly.
(applaunch 70 is Half-Life, applaunch 10 is CS 1.6, other applaunch-values can be found here: http://developer.valvesoftware.com/wiki/Steam_Application_IDs )
Tools--->Options-->Build Programs--->Game executable: C:\Program Files\Steam\Steam.exe (make it point to your steam.exe)
Then when you are about to compile the map, at the "Normal" compile-window under "Additional game parameters:" write: -applaunch 70 +developer 1
(You can add additional game parameters after the applaunch-part, in this case I've set dev mode to 1...)
Then press OK to compile and the game should start your map after compile. Although I think the Steam-client must already be running in background for it to work properly.
(applaunch 70 is Half-Life, applaunch 10 is CS 1.6, other applaunch-values can be found here: http://developer.valvesoftware.com/wiki/Steam_Application_IDs )
When I play the map in developer-mode I get "Too many entity's in visible packet list" (i.e. too many visible entities).
(You can see if raising num_edicts help: http://forums.alliedmods.net/showthread.php?t=54117)
(You can see if raising num_edicts help: http://forums.alliedmods.net/showthread.php?t=54117)
Make a "sandwich" out of multiple trigger_push'es under the trampoline. The lowest one should have a high "speed of push"-value, then you lower it a little for each trigger_push.
Some recommendations: http://zhlt.info/settings-for-final-compiles.html
strange.....Abortion.
Check all your paths (Tools-->Options...), the "Access denied" error is usually the result of not setting up the paths correctly.
In CS 1.6 the normal way of placing models in a map is by using the cycler_sprite-entity, I have never had any problems with it. Are you mapping for Half-Life, maybe it behaves differently? Or maybe your using old version of Hammer and/or an old fgd?
Looks a bit blocky.
So the problem was the compile tools?
The tga's works nice here...
Can you upload your sky?
You have six pictures for your sky, right? (testBk, testDn, testFt etc.)
You place the sky-pictures in correct folder? (...gfx/env)
Correct format? (Default bmp-skies seems to be in 8-bit color depth...)
You have six pictures for your sky, right? (testBk, testDn, testFt etc.)
You place the sky-pictures in correct folder? (...gfx/env)
Correct format? (Default bmp-skies seems to be in 8-bit color depth...)
What happens when you select the brush afterwards and press Alt+Enter to see its properties?
Bob Marley - Could You Be Loved
Probably been brought up before, but still:
When you are making a reply and select some text and press one of the BBCode-buttons it replaces your text with a start-tag, instead it should place appropriate start- and end-tags around the selected text.
When you are making a reply and select some text and press one of the BBCode-buttons it replaces your text with a start-tag, instead it should place appropriate start- and end-tags around the selected text.
** Executing...Why are command parameters being applied to a directory? I think you should re-check the paths in your configuration...
** Command: Change Directory
** Parameters: "f:\games\home made cs maps\spirit\spirit_hardtests" -texdata 10000
Also, is this a Normal or Expert compile? Have you tried them both?
Clip-brushes don't have any big impact on r_speeds, clip-brushes are used to fix/reduce clipnodes.
The .rmf-file may be corrupt, have you tried saving it to a new .rmf-file?
Have you used the VM-tool anywhere in your map, if so, those brushes would be your prime suspects. Could be that a damaged brush have caused a chain of reactions causing the compile tools to intercept a legal brush as a damaged one.
Have you used the VM-tool anywhere in your map, if so, those brushes would be your prime suspects. Could be that a damaged brush have caused a chain of reactions causing the compile tools to intercept a legal brush as a damaged one.
Tried the extra-flag on rad?
What entity are you using to display the model? (Should be cycler_sprite)
Could also try and set "Game directory" to point to counter-strike (My "Game directory" points to: C:\Program Files\Steam\SteamApps\*****\counter-strike).
You could also try this fgd: http://www.speedyshare.com/files/20625061/cs-fgd-xpu.zip (Ignore "counter-strike-SP.fgd", only use "counter-strike.fgd")
Could also try and set "Game directory" to point to counter-strike (My "Game directory" points to: C:\Program Files\Steam\SteamApps\*****\counter-strike).
You could also try this fgd: http://www.speedyshare.com/files/20625061/cs-fgd-xpu.zip (Ignore "counter-strike-SP.fgd", only use "counter-strike.fgd")
According to some people the latest driver from ATI should allow people to select in the 3d-view again: http://www.chatbear.com/unity2/12/589,1263979479,28753/1081701?v=flatold
hlife_hotdog is right, here's a list of different texture types: http://www.slackiller.com/tommy14/hltexture.htm
Ah, sorry you're right, it does reset.
Read it on a forum long ago, stupid of my never to check its validity.
Read it on a forum long ago, stupid of my never to check its validity.
No, AFAIK there's no other way, you need to reset it manually by placing func_friction around it which resets to your default friction.
Also, if I remember correctly: when you die and respawn in a multiplayer game the friction will not reset by itself, so if you die inside the func_friction you will still have the new friction when you respawn, therefore you should also place func_friction under the spawn points which sets friction to the default value.
Also, if I remember correctly: when you die and respawn in a multiplayer game the friction will not reset by itself, so if you die inside the func_friction you will still have the new friction when you respawn, therefore you should also place func_friction under the spawn points which sets friction to the default value.
Are you sure it locks up, maybe it's just working? A badly built map could take an hour or more to compile.
And how are you compiling it, from Hammer? If so, try to compile with a batch-file instead.
And how are you compiling it, from Hammer? If so, try to compile with a batch-file instead.
Just google for a doom wad editor?
Haven't tried this one, but it may work: http://www.doomworld.com/xwe/
Also: http://www.doomworld.com/classicdoom/utils/editors.php
Haven't tried this one, but it may work: http://www.doomworld.com/xwe/
Also: http://www.doomworld.com/classicdoom/utils/editors.php
In Hammer, press F1, write in "Reshaping"....
This usually means that Hammer couldn't auto-start the map after compile, you could just check the box "Don't run the game" at the compile-settings and just start the map manually after the compile is done.
(Or set up the editor properly.)
(Or set up the editor properly.)
they are both completely finished and ready for compile.. except I keep getting vis error in both..How can they be "finished and ready for compile" when they don't compile properly!?
Any errors/warnings in the compile log?
Any error messages? Does it print any errors in the console?
First of all, can you post the compile log?
A cycler_sprite, like the name suggests, is specially made for sprites. Use a cycler instead.CS 1.6 uses cycler_sprite for models.
Try using a func_wall instead, covered with the {BLUE-texture (halflife.wad) with "Render Mode" set to "Solid" and "FX Amount" set to "255".
Also, like JeffMOD says, could be a visleaf bug. You are compiling with VIS set to "Normal", right? (You could also try to compile it with full by using the -full switch.)
Also, like JeffMOD says, could be a visleaf bug. You are compiling with VIS set to "Normal", right? (You could also try to compile it with full by using the -full switch.)
Have you covered it with a CLIP-brush? I heard that covering models with CLIP-brushes could sometimes cause them to disappear.
What's your current wpolys?
Make it turn-based like X-com: Apocalypse! 
If you want bombs/grenades to stay on the construction all you need to do is to turn construction into a func_wall, you don't need the CLIP-brush or func_illusionary.
1. I don't know
2. You could make a copy of the construction, cover the copy completely with the NULL-texture, make sure it's a world brush and doesn't touch walls or floors(or any other world-brushes) and place it in the same position where the real construction is, I think that should work.
1. I don't know
2. You could make a copy of the construction, cover the copy completely with the NULL-texture, make sure it's a world brush and doesn't touch walls or floors(or any other world-brushes) and place it in the same position where the real construction is, I think that should work.
lololol get a clue son. the truth of the matter is that EVERYTHING should be func_walled that is not part of the basic geometry of the map. leaving everything aside from tiny details, handrails and cylinders is just giving vis more to think about entirely unnecessarily.Just don't go overboard with the func_walling. VIS will have a hard time optimizing the map properly if you func_wall larger structures like walls and stuff that otherwise would've functioned as VIS-blockers.
Also brush-entities doesn't cast shadows if I remember correctly, I think ZHLT supposedly included something like zhlt_customshadow but I, personally, never got it to work satisfactory.