Forum posts
- Forums
- Posts
- Posted by
The Mad Carrot
I thought of something similar myself some time ago and came to the conclusion that its not possible. Not in GoldSource.
Grim accidentally deleted that thread due to shitty placement of the Delete and Edit buttons... It happend to me too once.
Me or Daubster will create a new HLDM thread soonnish.
Me or Daubster will create a new HLDM thread soonnish.
Whatever...
Why is my Space Shuttle Source Mod not mentioned in the "The Best Mod In Progress" catagory?
Does it suck?
Or simply because i never made a thread about the mod?
Aw well... It doesn't matter.
Why is my Space Shuttle Source Mod not mentioned in the "The Best Mod In Progress" catagory?
Does it suck?
Or simply because i never made a thread about the mod?
Aw well... It doesn't matter.
Impossible. You can't use the sky to hide parts of your map.Actually, you can if you compile with full vis.
We're at T-Minus 6 hours and counting...
LOL!
Sheesh, relax man. :/
Whats the big deal? You can map for HL2/Ep1 and it'll load fine in Ep2.
Unless you can't run HL2/Ep2 either, i would feel bad for you...
But thank Valve, there is still GoldSource!
Whats the big deal? You can map for HL2/Ep1 and it'll load fine in Ep2.
Unless you can't run HL2/Ep2 either, i would feel bad for you...
But thank Valve, there is still GoldSource!
Sure, why not. Ill put something together...
Looking great, Huntehmoo!
You better finish that! Ye hear?
You better finish that! Ye hear?
You fail at linking...
If you got large surface area's, try increasing the texture scale.
And don't forget to func_wall / func_illusionary complex groups of detail brushes. Be carefull not to func_wall / func_illusionary entire groups as one single entity, to avoid facesplitting.
Face splitting occurs when:
I've seen maps way more complex than mine. My map has several turnings and walls for vis-blocking.Thats probably not enough optimization.
If you got large surface area's, try increasing the texture scale.
And don't forget to func_wall / func_illusionary complex groups of detail brushes. Be carefull not to func_wall / func_illusionary entire groups as one single entity, to avoid facesplitting.
Face splitting occurs when:
- 2 or more solid world brushes meet (touch).
- 2 or more brushes that are in the same entity group meet.
- 1 solid world brush meets a brush entity.
- 2 seperete brush entities meet.
Textures that bleed when shot?
:/
Don't you mean blending textures?
:/
Don't you mean blending textures?
Then you made your map way too complex.
Instead of func_i. the whole thing, func_i. only parts, otherwise you would still generate facesplitting.
Check this out:
http://www.themightyatom.nl/twhl_downloads/xenish_creature_seperate_ents.rmf
And see if that did anything. Also check if the number of leafs went down with this one (keep an eye on the charts shown during each compile stage (requires the -chart parameter)). The Compilator has the -chart option enabled by default.
Check this out:
http://www.themightyatom.nl/twhl_downloads/xenish_creature_seperate_ents.rmf
And see if that did anything. Also check if the number of leafs went down with this one (keep an eye on the charts shown during each compile stage (requires the -chart parameter)). The Compilator has the -chart option enabled by default.
You simply exceeded the maximum amount of faces a map can have.
Tommy14 says this:
Tommy14 says this:
You have gone over a limit similar to max patches error, but by BSP creating too many leaf faces for VIS to handle - probably due to "shattering" of a brush. Did you carve a complex brush (like a cylinder) or intersect it with another brush?
- Up your texture memory. 8mb (8192) should be more than enough.
- Func_illusionary those Xen objects and use a clip brush to prevent the player from walking though it. Only if the player can actually walk up to it.
- Apply the NULL texture to unseen faces, to world brushes and brush entities.
Ah. Neat!
Don't bother asking.
Penguinboy always says no. Even to funny little things like custom usertitles.
Penguinboy always says no. Even to funny little things like custom usertitles.
I have yet to play it. His host sucks major balls. As soon as it finished downloading, im gonna upload this to my own webspace (yeah, im that nice).
4) Yes, but that would make it a custom wad file and you'll have to included it into the BSP, if you're ever plan to release your map to public.
LOL!
For HL singleplayer or HLDM, move the bsp files to:
valve/maps.
For CS maps:
cstrike/maps
For DOD:
dod/maps
etc.
valve/maps.
For CS maps:
cstrike/maps
For DOD:
dod/maps
etc.
Well, there's your problem.
Switch to OpenGL and never change back.
Switch to OpenGL and never change back.
No, you need 3.5. It won't work with 3.4.
Get 3.5 here: http://www.themightyatom.nl/hldownloads/hammer_testbuild04.zip
Get 3.5 here: http://www.themightyatom.nl/hldownloads/hammer_testbuild04.zip
JeffMOD, just go ahead and make whatever you like, as long as you enjoy making it. Who cares if its a Black Mesa themed mod, Black Mesa is WIN!
There's no need to give entities a name (targetname) if their not going to get triggered.
Try to func_wall and func_illusionary groups of detail work (only if their close to eachother). Func_illusionaries work fine on brushesh the player never can reach (IE: touch it).
Edit: Your download link doesn't work.
Edit2: I assume this is the correct link: http://www.pork-cheese.com/downloads/gg_oil_facility_test1.rar?
Holy shit dude! No wonder LeafThread takes years! Ill do some optimizing for you.
Edit3: Here you go: http://www.themightyatom.nl/stuff/gg_oil_facility_test1_optimized.rmf
Try to understand what you should func_wall and what to func_illusionary.
The only thing i didn't touched are those two shipping containers. The halflife.wad texture file comes with some shipping container textures. Use those. Or maybe you have a different shipping container texture in any other wad files you're usig for your map.
The worst thing you could do in HL mapping, is making fences with hundreds of brushes and not tie it to an entity. So i replaced those with actual metal fences, tied it to func_illusionaries, and placed a CLIP brush inside them.
Im worried about your r_speeds though...
Edit: Your download link doesn't work.
Edit2: I assume this is the correct link: http://www.pork-cheese.com/downloads/gg_oil_facility_test1.rar?
Holy shit dude! No wonder LeafThread takes years! Ill do some optimizing for you.
Edit3: Here you go: http://www.themightyatom.nl/stuff/gg_oil_facility_test1_optimized.rmf
Try to understand what you should func_wall and what to func_illusionary.
The only thing i didn't touched are those two shipping containers. The halflife.wad texture file comes with some shipping container textures. Use those. Or maybe you have a different shipping container texture in any other wad files you're usig for your map.
The worst thing you could do in HL mapping, is making fences with hundreds of brushes and not tie it to an entity. So i replaced those with actual metal fences, tied it to func_illusionaries, and placed a CLIP brush inside them.
Im worried about your r_speeds though...
The name "multisource" comes to mind...
I see. And yes, i meant func_button.
No, you tied all four button to one func_button. That would be pretty weird, because when you usekey one button, they all light up. Its better to tie each button to a func_wall entity and then have them all target the gate.
Looks like you're running CSG, then BSP, then CSG again, then BSP again. Where's VIS and RAD?
So try to compile your map the correct way first (in this order: CSG, BSP, VIS, RAD) and then we can focus on the problem at hand (if it still persists).
Also, if a compile process shows (Not responding), it doesn't mean that it crashed or locked up, its simply doing its job, but there's not time to update the process so Windows thinks its handing. Just give it time.
If there's an actually crash dialog popping up, then there's really a problem with either the compile tools, or your map.
So try to compile your map the correct way first (in this order: CSG, BSP, VIS, RAD) and then we can focus on the problem at hand (if it still persists).
Also, if a compile process shows (Not responding), it doesn't mean that it crashed or locked up, its simply doing its job, but there's not time to update the process so Windows thinks its handing. Just give it time.
If there's an actually crash dialog popping up, then there's really a problem with either the compile tools, or your map.
You need newer compile tools:
http://www.themightyatom.nl/hldownloads/zhlt34x86final.zip
You may want to func_wall that arch, its less tough for the compiler that way.
And why did you func_walled those four big walls? That could be the cause of the arch being too bright. I say convert the big walls back to normal world brushes, but those detail things on top of the walls (i don't know the name for those) should stay func_walls.
http://www.themightyatom.nl/hldownloads/zhlt34x86final.zip
You may want to func_wall that arch, its less tough for the compiler that way.
And why did you func_walled those four big walls? That could be the cause of the arch being too bright. I say convert the big walls back to normal world brushes, but those detail things on top of the walls (i don't know the name for those) should stay func_walls.
Maybe the FGD has not model/sprite support in Hammer.
Now: Solarscape - Coming Down (Ishido Remix)
Next: Vagabond - Music Holocaust
Next: Vagabond - Music Holocaust
How about a good ol' singleplayer mod?UberWin * 2 & "!"
Holy cow, have you got nothing better to do? 
I can't press any of the buttons at the top of the hill that are supposed to open the gate of the 'fortress'.Because you're not targeting the door. The 4 buttons all target the multimanager and the multimanager targets all the buttons.
Whats the point of that?
Also the texture of the gate gets buggy ingame.Make a screenshot.
You know Urb, nothing can beat a good oll' Half-Life singleplayer map!
So you better finish that, boy!
So you better finish that, boy!
I can't help you with that, i've never used that entity. Why not try it out and look for tutorials?
I got a pet headcrab. ^^
Why not rotate that texture until its 90 degrees and rotate them 45 degrees in Hammer with the Face Edit Sheet?
I don't really get the problem. What do you want with the door?
penguinbodyEpic win.
If you want a door, use func_door or func_door_rotating, not func_train.
As for the no solids error, you probably assigned an entity to a brush, and then deleted it. Or something. There's not really a fix for it, its just something you did.
First make your brush door, then tie the whole thing to func_door or func_door_rotating.
To get rid of the blue, use render mode solid, and FX amount 255.
I don't do CS so i can't help you with your last question.
As for the no solids error, you probably assigned an entity to a brush, and then deleted it. Or something. There's not really a fix for it, its just something you did.
First make your brush door, then tie the whole thing to func_door or func_door_rotating.
To get rid of the blue, use render mode solid, and FX amount 255.
I don't do CS so i can't help you with your last question.
I think so, that did the trick.
Ill check it out. Stay tuned.
Edit:
Ok, try this: http://www.themightyatom.nl/stuff/3floor_elevator_test_map.rmf
Also, do not user uppercase characters in entity strings (names and targets), this may cause problems.
Edit:
Ok, try this: http://www.themightyatom.nl/stuff/3floor_elevator_test_map.rmf
Also, do not user uppercase characters in entity strings (names and targets), this may cause problems.
do you think the problem could also be that I have the 3.4 edition of the hammre?No. You can consider upgrading to version 3.5. Get the executable from my website.
what about my inability of posting the map in the map vault?Like i said, you need to zip your file.
Correct Luke is correct. Use the journals.
I just did a quick test and it works perfectly on path_corners. I think you either misnamed something or forgot a property.
Here's the rmf for you to examine: http://www.themightyatom.nl/stuff/change_target_test.rmf
The yellow button starts the train. The train goes left.
The red button targets a trigger_changetarget, which targets the second path_corner named stop2 and changes its next stop target from stop3 to stop2a, making the train go right.
Here's the rmf for you to examine: http://www.themightyatom.nl/stuff/change_target_test.rmf
The yellow button starts the train. The train goes left.
The red button targets a trigger_changetarget, which targets the second path_corner named stop2 and changes its next stop target from stop3 to stop2a, making the train go right.
You need to zip it...
Post the map in the problem maps vault.