As for the Surface Inspector... Well, for me texture application in Radiant is a true torture. I think I have to use Jackhammer for texturing and Radiant for the rest.
Forum posts
There's a simplier way. You just do a W:3 H:3 patch mesh and then... Well, the screenshots will explain better:You just drag verticies like that. No need to divide it in segments - the editor will do it automatically.
As for the Surface Inspector... Well, for me texture application in Radiant is a true torture. I think I have to use Jackhammer for texturing and Radiant for the rest.
As for the Surface Inspector... Well, for me texture application in Radiant is a true torture. I think I have to use Jackhammer for texturing and Radiant for the rest.
At least you don't have to drag every vertex manually if you don't need to. But sewing and subdividing is still something I barely understand.
What's also frustrating is that the texture you apply to a displacement has some kind of... UV-Lock(?) which causes the texture to stretch sometimes.
What's also frustrating is that the texture you apply to a displacement has some kind of... UV-Lock(?) which causes the texture to stretch sometimes.
The problem is that I just can't make an arched patch mesh:
There's just no arch tool for that.
EDIT: Nevermind, I sorted it out. Curves is a wonderful thing:
EDIT: Nevermind, I sorted it out. Curves is a wonderful thing:
Oh shit, sorry. Of course it's light_surface. Just didn't sleep that night so I said this weird thing.
They should be able to teleport to them though, as it is said in the "Keys" tutorial.
Try backspaceOh... I feel so-o-o-o stupid.
Now I only need to understand how do curves work and how to use the texture application tool and then I will be able to create a decent map. Btw the "Curves" tutorial isn't too helpful.
Use info_texlights instead of obsolete lights.rad. Just disable SmartEdit, Press add and in the "Key" type in the name of the texture and in the "Value" type in the values of Red, Green, Blue and the Brightness. You can store many values in this entity, plus it's individual for every map.
There's also info_translucent. It's like info texlights, but it's more flexible and you need a separate info_translucent for every texture light.
Func_detail is also useful if some brush has disappearing faces. It usually happens when it's off the grid (like the support pillars on DM-Fractal) and the only way to fix it without repositioning the brush is to convert it to func_detail.
Good luck!
There's also info_translucent. It's like info texlights, but it's more flexible and you need a separate info_translucent for every texture light.
Func_detail is also useful if some brush has disappearing faces. It usually happens when it's off the grid (like the support pillars on DM-Fractal) and the only way to fix it without repositioning the brush is to convert it to func_detail.
Good luck!
How can you make something follow a path if it doesn't even have a basic AI?
Monster_generic doesn't have any AI, so I think you can't make it follow a path. But you could try to create a small platform tied to func_train with "zhlt_noclip" and "zhlt_invisible" set to 1 and place the monster_generic on it.
No, you can actually delete an object, but you need to go to "edit" -> "delete" to do that. While every other button in the "edit" menu has a shortcut specified at the right, "delete" doesn't have a shortcut.
Slowly getting used to the controls. The fact you have to manually enter the keys for the entities still shocks me.
Just found out that Del doesn't delete the selected object. It appears that the "Delete" operation doesn't have a shortcut at all. Or I'm just a dumbass.
Just found out that Del doesn't delete the selected object. It appears that the "Delete" operation doesn't have a shortcut at all. Or I'm just a dumbass.
Why wouldn't you use brushes for the lights instead? They don't look too complicated to be models.
Something is wrong with the compilation process.
All I can suggest is to switch from hammer to Jackhammer/Sledge (good alternatives to VHE).
Also, sorry for such a question (I need to know as much as possible) but did you actually try to compile the map? If you did, may you post the compilation log? It would be very useful.
All I can suggest is to switch from hammer to Jackhammer/Sledge (good alternatives to VHE).
Also, sorry for such a question (I need to know as much as possible) but did you actually try to compile the map? If you did, may you post the compilation log? It would be very useful.
@Snehk
I'll take a look at the tutorials, thank you. I felt so confused when Shift+A didn't call the texture application tool xd. At least I compiled my first box map successfully with Radiant. Jackhammer kept doing weird things.
I'll take a look at the tutorials, thank you. I felt so confused when Shift+A didn't call the texture application tool xd. At least I compiled my first box map successfully with Radiant. Jackhammer kept doing weird things.
Jackhammer supports Q3. Just setting it up is pretty difficult. And I couldn't find any tutorials about how to do that.
I use GTKRadiant 1.6 if I know right. Because of my stupidity I couldn't set Jackhammer up for Q3 so I had to use GTKRadiant. Even though I'm an intermediate mapper, I couldn't do more than a simple box-like room.
I agree with you. It's much more comfortable to use your favorite editor.
Oh, and how do you make terrain in Radiant? Do you use those "patches" for that? I'm just going to start learning Radiant. Want to try Q3 mapping.
Oh, and how do you make terrain in Radiant? Do you use those "patches" for that? I'm just going to start learning Radiant. Want to try Q3 mapping.
Weren't you going to use 3d-modeling software for the levels?
@GMK_5
Try launching full VIS. This may help.
Also, VIS in Source works almost the same way it does in GoldSrc, so here's some VDC documentation:
https://developer.valvesoftware.com/wiki/Visibility_optimization
https://developer.valvesoftware.com/wiki/Visleaf
This should explain how does VIS work if you read carefully. I also recommend to read it multiple times.
Try launching full VIS. This may help.
Also, VIS in Source works almost the same way it does in GoldSrc, so here's some VDC documentation:
https://developer.valvesoftware.com/wiki/Visibility_optimization
https://developer.valvesoftware.com/wiki/Visleaf
This should explain how does VIS work if you read carefully. I also recommend to read it multiple times.
Basically, by disabling Snap-to-Grid you get 1-unit sized grid instead. So it's still possible to make a nice map without snap-to-grid. What about info_player_start... Well, that's so weird I want to try it too.
As far as I know, in Source disabling snap-to-grid works as it should.
As far as I know, in Source disabling snap-to-grid works as it should.
So, all this time you just didn't know about grid at all? And why do you use Quark?
I wish I could be as weird as you.
It reminds me of how in Warcraft 3 me and my friend used to measure the distance you can cast spells from in footmen.
I wish I could be as weird as you.
It reminds me of how in Warcraft 3 me and my friend used to measure the distance you can cast spells from in footmen.
Then I'm a very stupid person in comparement to you.
Ok, that has gone too far from the main topic.
Ok, that has gone too far from the main topic.
Maybe it's cool stuff, but I have no clue how to edit a fgd file. I can only add that sky list from jackhammer to a fgd. I hope you get what I mean.
I wish someone would make a detailed tutorial about how to edit a fgd file and how to adapt it to Jackhammer.
You do almost the same with the planks. But instead of picking up a key the player picks up the planks and then, instead of opening a door player activates an invisible button/a trigger_once, the target of which is func_wall_toggle (which looks like a set of wooden planks and is turned off at the start).
Read all the tutorials (including the one I gave you a link for) on TWHL. They are extremely useful.
Read all the tutorials (including the one I gave you a link for) on TWHL. They are extremely useful.
Oh, that's a combination of some env_renders and this: http://twhl.info/tutorial.php?id=64
After you set this all up, you must make a brush-based key, similar to the one picked up by the player at the keyhole, then tie it to a passable func_door_rotating with Render Mode "Texture" and FX Amount = 0 and set up two env_renders - the first one with Render Mode "Normal" and the second one with Render Mode "Texture" with FX Amount = 0.
When the player activates the trigger_once that checks if the multisource is active, multi_manager gets activated and activates the first env_render (which makes the key (func_door_rotating) visible), then the key (func_door_rotating) itself, and then activates the second env_render which makes the key invisible again.
There must be an example map somewhere at the vault. If you want you can try to find it. Good luck!
After you set this all up, you must make a brush-based key, similar to the one picked up by the player at the keyhole, then tie it to a passable func_door_rotating with Render Mode "Texture" and FX Amount = 0 and set up two env_renders - the first one with Render Mode "Normal" and the second one with Render Mode "Texture" with FX Amount = 0.
When the player activates the trigger_once that checks if the multisource is active, multi_manager gets activated and activates the first env_render (which makes the key (func_door_rotating) visible), then the key (func_door_rotating) itself, and then activates the second env_render which makes the key invisible again.
There must be an example map somewhere at the vault. If you want you can try to find it. Good luck!
You need to understand how does VIS work and what is a VIS leaf. Sadly even I don't understand it completely (I'm too lazy to read anything about how VIS works).
As I said, copy a part of your map which you have problems with into an another map and then experiment with it.
As I said, copy a part of your map which you have problems with into an another map and then experiment with it.
The problem is his map has too many areas to rework.
@GMK_5
Reworking the area is not going to be easy. If I were you I'd just start a new map.
Just use Google and you'll find VHLT. Very useful thing, trust me.
Reworking the area is not going to be easy. If I were you I'd just start a new map.
Just use Google and you'll find VHLT. Very useful thing, trust me.
I think VIS takes so long because of... Just look:
So yeah, the best GMK_5 can do is to create a new map.
Oh... Ok.
Try to transfer a chunk of your map you have problems with into another map (a simple box for example, doesn't matter). This way you can significantly speed up the compilation.
I'd recommend you to start a new map instead. No offense but your current map is very messy. You can still copy some ideas though, so creating a new clean map is the best option.
I'd recommend you to start a new map instead. No offense but your current map is very messy. You can still copy some ideas though, so creating a new clean map is the best option.
Oh, so I'm not the only one who uses player start as a measure?
@Snehk
Great job. Waiting for the first screenshots.
@Suparsonik
I've never played TFC. Is it still alive?
Great job. Waiting for the first screenshots.
@Suparsonik
I've never played TFC. Is it still alive?
Here's one of my abandoned projects:
I don't know if I'm ever going to continue working on it. Was thinking about it recently.
Here's the layout, unfinished as the map itself:
As for now, I decided I should stop my mapping, ahem... "career", because I started making pure shit.
Here's the layout, unfinished as the map itself:
Although it would be better if I upload images, here are the places:
-Light fixtures at the cells are wbrushes that intersect with eachother. Convert to func_detail
-Two ground wbrushes intersect near that trigger_push thing (I have no idea what it is)
-Castle towers intersect with castle walls.
There can be a lot of other intersecting brushes, these are the most obvious ones. I'll try to find more.
-Light fixtures at the cells are wbrushes that intersect with eachother. Convert to func_detail
-Two ground wbrushes intersect near that trigger_push thing (I have no idea what it is)
-Castle towers intersect with castle walls.
There can be a lot of other intersecting brushes, these are the most obvious ones. I'll try to find more.
@GMK_5
Well, try to compile your map. If the bug still occurs, then probably Admer can help, because I don't have any other ideas yet. The map should compile faster now.
I also found a lot of intersecting brushes in some other regions of the map.
Well, try to compile your map. If the bug still occurs, then probably Admer can help, because I don't have any other ideas yet. The map should compile faster now.
I also found a lot of intersecting brushes in some other regions of the map.
I didn't cut it because I was so tired I just used PrtSc instead. Then I pasted it directly to imgur and had to wait until it uploads, the size of the image was really high.
@GMK_5
Also, I suggest you to convert all crates on your map to func_details. They're all wbrushes and that's not good for both CSG and VIS.
EDIT: One more weird thing:
@Admer456
Thanks anyway
Also, I suggest you to convert all crates on your map to func_details. They're all wbrushes and that's not good for both CSG and VIS.
EDIT: One more weird thing:
Just so you know, there's this Snipping Tool in Windows 7. It's handy for screenshots. :3Sometimes I think that you're just mocking me. No need to do that if so, I get that I'm a terrible person :/. I you aren't then sorry, I'm just being paranoid.
Thanks anyway
Ok, just lemme unpack the textures and set my editor up.
I can't really tell you if that's the problem, but here's what I found:
There are two other brushes under this one. One of these intersects with an another brush:
Sorry, but I'm not really sure if that's what causes the bug 
I'll keep looking into it though.
I can't really tell you if that's the problem, but here's what I found:
I'll keep looking into it though.
@GMK_5
Also, crates on your map are world brushes and intersect with other w(orld)brushes. Convert them to func_details and reposition them.
Poor VIS.
EDIT: Beds at the cells are made of intersecting wbrushes. You know what to do.
Lots of intersecting wbrushes. Your map needs some serious work.
Also, crates on your map are world brushes and intersect with other w(orld)brushes. Convert them to func_details and reposition them.
Poor VIS.
EDIT: Beds at the cells are made of intersecting wbrushes. You know what to do.
Lots of intersecting wbrushes. Your map needs some serious work.
Dude, you forgot the textures. I can handle it without them though
EDIT: The map is pretty messy. Found some intersecting brushes.
EDIT 2: There are many brushes which can be replaced with one single brush. They even have the same texture.
EDIT: The map is pretty messy. Found some intersecting brushes.
EDIT 2: There are many brushes which can be replaced with one single brush. They even have the same texture.
Maybe he just placed too many small world brushes. Every world brush blocks VIS, and if there are too many small wbrushes or a very detailed single wbrush (Like cylinder), this may cause VIS to do weird things.
I'd recommend to convert such things into func_detail entities and if the shape of such brushwork is too complex then you should also put a less detailed CLIP brush over it.
But as Admer said, it would be better if you upload your map so we can look into your problem.
Ok, looks like I'm totally not being helpful.
@Admer456
I'd recommend to convert such things into func_detail entities and if the shape of such brushwork is too complex then you should also put a less detailed CLIP brush over it.
But as Admer said, it would be better if you upload your map so we can look into your problem.
Ok, looks like I'm totally not being helpful.
@Admer456
Hint and Skip brushes are a pretty weird topic for beginnersI'll be honest - don't even I know how to properly use these.
Probably a VIS error. Did you convert all the small detailing brushes into func_detail? If it's a VIS problem then you should try to place some HINT brushes.
Also, can you fall through those "leaks" into the void? If no then it should be a VIS error.
Also, can you fall through those "leaks" into the void? If no then it should be a VIS error.
That's what happens when you make yourself work on the map while not in the mood.
Throw in some screenshots. This gets too far from WIP stuff. I'd throw in some of dm_deadlands, but it looks like shit.
I'm going to completely remove the second structure. Kachito said that those pillars get to repetitive but I couldn't find any alternatives to them. Damn it.
I'm going to completely remove the second structure. Kachito said that those pillars get to repetitive but I couldn't find any alternatives to them. Damn it.
What a cutie, lol.
Was that the first mouse he destroyed?
Was that the first mouse he destroyed?
Can't wait for the results.
Ok, I can't keep it anymore. I'm envy to you.
Also, how did he actually break his mouse?
Also, how did he actually break his mouse?
This conversation needs a separate thread xd.