Forum posts
- Forums
- Posts
- Posted by
RabidMonkey
You're not running with +deathmatch 1 perchance are you?
Did anyone notice There may be only one water level height in a PVS if the water is expensive.?
They're in different PVS's, if there's expensive water in two areas of a map.
They're in different PVS's, if there's expensive water in two areas of a map.
Or you can just select a texture before you make the brush and then it's automatically applied, but that's not the problem :/
Just experiment with the fit button...a standard tex ratio is .25x.25 now as opposed to 1 but it's not too different. (ie, a 512x tex fits correctly onto a 128x brush.)
Just experiment with the fit button...a standard tex ratio is .25x.25 now as opposed to 1 but it's not too different. (ie, a 512x tex fits correctly onto a 128x brush.)
I could mail it to you right now, but not for every update ;< - Arizona isn't toooooo far away 
No problem 
I guess the top toolbar functions in controlling additions to visgroups. Additionally, you should be able to set them in any object's properties.
I guess the top toolbar functions in controlling additions to visgroups. Additionally, you should be able to set them in any object's properties.
Hm, you should be able to have groups in a VisGroup. Did you group them, select the group(s) you want to hide, then hit that little red box on the toolbar, and select the group you want to add it to?
Eels - Numbered Days
The easiest way to ensure that they are accurately scaled is to import a player model from the sample model set and use it to scale things...a player is 72 units. Not sure how that corresponds onto the Maya grid.
You'd make a mod and make them 1/16th scale
You need the game activated and installed (and purchased) in order to use the SDK.
Ever heard of bumpmapping? It's probably the _a texture, and you're using the _b one. I've had it happen before.
Your swap buffers seem extremely high. Anything like the following?
Swap Buffers: This is typically caused by transparent textures/effects such as glass, env_steam, env_smoke, and of course, func_water. As long as it doesn't do it for a large section of your map, you will probably be ok. So if the swap buffers only go crazy when you stare RIGHT into an expensive water texture or some heatwave style env_steam, you probably don't have a problem... that's just what they do.
Make one piece and cut-paste it all over.
Yes, it's worth learning static prop modelling for Source because the engine really relies on props for detailed maps.
MAX/Gmax is soooort of similar to Hammer, but not really.
Yep.
If you want the sound to start or stop depending on the button presses, you need to toggle it instead of starting and stopping it.
Righto.
Run with +showbudget in the console and screenshot the graph, then post it here.
Nice.
They have good military surplus too ;D
They have good military surplus too ;D
I've had mine since the Kungfu espisode of W+B was released :< - I've changed it from 'drunken pirate' to 'monkey stance' along the way.
Gimme the server nfo and I'll drop by.
Argh, the problem with this is because you've used a model texture on that brush. Just use a texture that doesn't have models/ in front of it, or use a prop.
It happens to me too and everyone I know who owns the game!Not if you're using a proper texture
Huh? How do you want to import them? Do you want a prop of a weapon or something?
Change the brightness to something like 1000 and see if anything happens.
Oh, I'm online, I probably wasn't then though - I'll leave AIM on.
Office doesn't have any building models, most of the skybox stuff was done with brushes. There are some skybox models in props_buildings though.
- I'll leave AIM on. Office doesn't have any building models, most of the skybox stuff was done with brushes. There are some skybox models in props_buildings though.
A little, if they're simply decorative and don't serve any purpose other than being there. (ie if they're not within the playable area.)
Yes, do it with teh final BSP.
You can't really use func_wall_toggle, it's really for legacy support.
use func_brush instead. Experiment with the I/O system, it replaced a lot of those ents like relays and renders.
use func_brush instead. Experiment with the I/O system, it replaced a lot of those ents like relays and renders.
Damn right ;>
Generate a nav mesh (nav_generate).
nav_edit 1.
nav_toggle_place_mode.
Then set something with nav_use_place (ie nav_use_place ctspawn) and bind a key to nav_toggle_place_painting. Then hit that key, aim at all the squares in your given location (they turn green) and then hit the key again when you're done.
nav_edit 1.
nav_toggle_place_mode.
Then set something with nav_use_place (ie nav_use_place ctspawn) and bind a key to nav_toggle_place_painting. Then hit that key, aim at all the squares in your given location (they turn green) and then hit the key again when you're done.
Go ahead - I've got a bot mesh to compile for a while so I'll be hanging around with nothing to do.
- I've got a bot mesh to compile for a while so I'll be hanging around with nothing to do.Have the button 'ToggleSound' if there is such an output instead.
Can't really comment on it since it's heavily WIP
I suggest you use the prebuilt models for the time being.
Streetlamps should be models, too, use a prop_static and check the props_c17 folder. Anything relatively complex like that should be in model format, most things are already built.
I suggest you use the prebuilt models for the time being.
Streetlamps should be models, too, use a prop_static and check the props_c17 folder. Anything relatively complex like that should be in model format, most things are already built.
Depends if you're running with good or shit shaders
Only a few. Perform a filter for 'props/' and you'll see what I mean.
Those 'model' textures are part of the de_dust prop set, which you can use on a prop_static entity. Images of them are here for reference out of the editor as they don't include thumbnail images:
http://rabidmonkey777.bluewolf72.com/imagery/prop_images
The tall skyscrapers are part of a 3D skybox, which uses a sky_camera entity to project an image of a 1/16th scale 'skyscraper' at the world's origin (0,0,0). The Source SDK docs have some more nfo on this, and I have an example map on one.
http://rabidmonkey777.bluewolf72.com/imagery/prop_images
The tall skyscrapers are part of a 3D skybox, which uses a sky_camera entity to project an image of a 1/16th scale 'skyscraper' at the world's origin (0,0,0). The Source SDK docs have some more nfo on this, and I have an example map on one.
Curses ;<
/query Alex can we have a HL2 subcompo :>?
Ooh, can someone say Nice?
Oh, btw, Ant, there is a directory called 'props' with some textures in it that were leftover from the earlier days of HL2 that can be used on brushes. The real distinction is their base dir in the Material System is props/ and not models/props
First step, don't carve ;<
Second, the easiest way to make buildings is going to be to make each brush individually, or with the clip tool, or to use textures with windows on them already. Carving will ruin your brushwork so it's advisable to not use it.
The color problem is indeed the 'model' textures. Models are cheap to render in Source because they use a cheap lighting method. (Vertex Lit, as opposed to Lightmapped.) The model textures are defined as VertexLitGeneric in their nfo files (vmts) and they won't be useable on something that's to be lightmapped (ie a brush.)
You can indeed make models for windows in Softimage (which is really crappy imo :p) or another Source-supported modelling program. (3DS max, my personal preference) or Maya, for example. I'd advise against learning modelling in the beginning, though, unless you're really interested in it, though, and save it for later on in your mapping.
If you have any more questions, catch me in IRC or on MSN.
Second, the easiest way to make buildings is going to be to make each brush individually, or with the clip tool, or to use textures with windows on them already. Carving will ruin your brushwork so it's advisable to not use it.
The color problem is indeed the 'model' textures. Models are cheap to render in Source because they use a cheap lighting method. (Vertex Lit, as opposed to Lightmapped.) The model textures are defined as VertexLitGeneric in their nfo files (vmts) and they won't be useable on something that's to be lightmapped (ie a brush.)
You can indeed make models for windows in Softimage (which is really crappy imo :p) or another Source-supported modelling program. (3DS max, my personal preference) or Maya, for example. I'd advise against learning modelling in the beginning, though, unless you're really interested in it, though, and save it for later on in your mapping.
If you have any more questions, catch me in IRC or on MSN.
Divit - Plan B'
#I've got my gun, I've got my plans, I've got my alibis, they understand#
#I've got my gun, I've got my plans, I've got my alibis, they understand#
Meh, just get 3DS, Gmax doesn't have the exporters.
Black Mesa East is just a nickname, I suppose - The actual facility seems to be some sort of an old military bunker. Probably had nothing to do with the actual BM.
3D Studio Max.
Of course things are, you just have to know where to look
ballsocket and lengthconstraint are two different things. A ballsocket applies a constraint at teh given point and allows things to rotate upon it (like the lights in de_prodigy.) Lengthconstraint can be added to something to make sure it's a certain distance away.
Are these CS:S props? For they don't have their own images.
I've compiled a big list with images for everything CS:S: http://rabidmonkey777.bluewolf72.com/imagery/prop_images/
If they're HL2, I have no idea - They should always be displayed. Try right-clicking and seeing if there's a 'thumbnail' option.
I've compiled a big list with images for everything CS:S: http://rabidmonkey777.bluewolf72.com/imagery/prop_images/
If they're HL2, I have no idea - They should always be displayed. Try right-clicking and seeing if there's a 'thumbnail' option.
Valid point. In any case you use a physbox, it's always going to have messed up lighting, I suppose D:
The junk prop problem is interesting, I had the same issue in Petrol with the sawblade and cinderblock. Try putting it on prop_physics, and make sure it's not colliding with any other physics props or the world.
The junk prop problem is interesting, I had the same issue in Petrol with the sawblade and cinderblock. Try putting it on prop_physics, and make sure it's not colliding with any other physics props or the world.