Forum posts
Thanks all of you. I never really left. I check in all the time. Just didn't have anything worth posting.
So in 2003 I released MINIMICUS for HL1. I was proud that thousands of gamers downloaded it, played it and liked it. On Friday, Sept 9th, 2011 I FINALLY met someone in real life who had heard of it - his room mate had played it and made him watch the microwave scene. Took long enough! 
It's been a while since I worked with the monster-maker, but I do remember that I couldn't set the properties of the children to do what I wanted. So I created a way of teleporting a set of real monsters in, one by one, triggered when I wanted them. Look in the rmf included with LDSF in the 'fun with lasers' competition; http://twhl.info/competitions.php?results=4 There is an elevator that lifts each monster into a trigger-teleport to bring them into the map when they are needed. It was complicated, but it worked. It's nice to see people still mapping for HL1 after all these years.
Are you using a multimanager to control the timing of the sequence? Or are you controlling it another way? After initially starting each camera, you may need to trigger each camera again to turn it off before triggering it back on again.
Only thing I can think of is, make sure you haven't accidentally placed any entities outside the map.
Thanks everyone! I appreciate all the votes and compliments on my maps.
My votes are:
1 - Timefall...I was one of the beta testers for this one, so I got to watch it improve to the final version.
2 - Issues...nice teamwork there.
3 - Star Wars... going into the tie fighter was cool.
4 - I would vote for Andy's CS map, but I couldn't find it.
My votes are:
1 - Timefall...I was one of the beta testers for this one, so I got to watch it improve to the final version.
2 - Issues...nice teamwork there.
3 - Star Wars... going into the tie fighter was cool.
4 - I would vote for Andy's CS map, but I couldn't find it.
The multicolored sparkles are telling you that you have nodes that can't 'see' any other nodes. - There is architecture probably blocking them. In game, typing impulse 197 will show the node connections to the nodes nearest to you.
I set up an example map for you. You needed to control the teleport with a multisource that was controlled by an env_global. That setup allows you to control the reset. Take a look at the example map and let me know if you have any questions.
http://twhl.co.za/mapvault_map.php?id=4578
http://twhl.co.za/mapvault_map.php?id=4578
Compile your map with the prefabs in it, then post the compile log here. There should be an error message in there, telling you what the problem is.
Sometimes the node sparkles appear around a node that can't 'see' any other nodes. You must have 2 or more nodes in an area where nodes are placed. They have to have a direct line of sight between them.
I don't know if this deserves its own thread, but i thought it was funny.
http://www.albinoblacksheep.com/flash/pwningdanoobs
http://www.albinoblacksheep.com/flash/pwningdanoobs
Has the map rotation been released yet? I'll prolly need to download before I can join in.
Be sure to let us know if OpenGL fixed the prollem. 
That way anyone researching the same thing can find an answer.
That way anyone researching the same thing can find an answer.One thing that may help is to use OpenGL in the video properties of the game. It sounds like you may be using software mode, which limits the amount of polys that can be displayed (compared to openGL.)
Just make two trigger_pushes in wedge shapes that compliment each other. The bottom wedge pushes up and the top wedge pushes sideways in the direction you want. The player should rise and move sideways at the same time.
Don't tie the train starting to a game_playerspawn. Use trigger_auto if you want the train to start when the map starts.
There was a problem compiling the map.What does this log say?
>> Check the file C:SierraHalf-Lifevalvemapstransitcar
test.log for the cause.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
Cool. Glad that worked. Level changes are tricky.
When Gordon is facing a certain direction, north for example (using top view in hammer), as he leaves the first map, he will be facing the same direction in the new map. It sounds like the two maps are not in sync directionally. Changing the angle parameter will not be able to fix the problem. To fix this, select the entire second map and rotate it so Gordon is facing the right way when he spawns in. Be advised, this may mess with other directional entities in the second map, like func_door_rotating.
Also, I was never able to do this using monstermakers. I had to use the true monster_human_grunt entities or whatever.
You don't know which monster will die last, so they need to be connected to a multisource somehow. If you DO know which monster dies last, then tetsu0's idea will work...
Why such a brief......... comment - i mean, +'s?????? what happened to the lengthly write-up?sigh Slayera shakes his head ruefully.
It can be done by hooking a multisource to your trigger_endsection. The problem with getting it done is you can't target the multisource directly from the death property of the monsters.
One solution is, The death can trigger a hidden func_button that CAN trigger a multisource. Each grunt would trigger a different button. Each button is hooked to the multisource. When the last button triggered, the multisource is triggered and that can trigger your endsection- make sure the buttons are set to stay on when triggered (-1).
One solution is, The death can trigger a hidden func_button that CAN trigger a multisource. Each grunt would trigger a different button. Each button is hooked to the multisource. When the last button triggered, the multisource is triggered and that can trigger your endsection- make sure the buttons are set to stay on when triggered (-1).
The scripted sentence isn't working because you didn't use the sentence name, you used the wav name. Put !SC_TEAM in your scripted sentence and see if that works. You can look it up in sentences.txt; the sentence name is in capital letters. As for #3, you would use a func_rot_button for that.
Compo results were written by SlayerAI was only asked to submit my notes, not a write-up of the winners, or I would have done a better job of writing things up. I didn't know they were going to be printed word for word. Ant's writeups above could be used in place of my notes. Anyway, congrats to the winners; nice job.
The answer to the first part is, you can't trigger a multisource directly from the death of a grunt. One solution is, The death can trigger a hidden func_button that CAN trigger a multisource. Each grunt would trigger a different button. Each button is hooked to the multisource. When the last button triggered, the multisource is triggered - make sure the buttons are set to stay on when triggered (-1).
The second question would be to use trigger multiples (t_m) that are each near a monsterspawn, but each t_m is tied to the spawn that is out of sight. The t_m's can be controlled by the multisource if that's what you're going for.
The second question would be to use trigger multiples (t_m) that are each near a monsterspawn, but each t_m is tied to the spawn that is out of sight. The t_m's can be controlled by the multisource if that's what you're going for.
Are you mapping for HL1 or something else? The angular velocity should be in the func_train properties, not the path corners.
Make sure your ship (func_train) has an origin brush. Then in the func_train properties, set the angular velocity to something like 50 0 0.
You'll need to play with it to get it to rotate at the speed you want. Anyway, when you trigger the ship to sink, then it will rotate at the speed you chose. If it rotates the wrong way, set one of the other variables in the angular velocity field, like 0 50 0 until it looks right. You can even set more than one to get it to twist and rotate, like 50 25 0.
You'll need to play with it to get it to rotate at the speed you want. Anyway, when you trigger the ship to sink, then it will rotate at the speed you chose. If it rotates the wrong way, set one of the other variables in the angular velocity field, like 0 50 0 until it looks right. You can even set more than one to get it to twist and rotate, like 50 25 0.
Anyone remember the Sega genesis console? It had a game called "Road Rash II." The default player name came up as PlayerA, so rather than delete the default and type my name, it was easier just to change the P to an S to make SlayerA. I've kept the name ever since.
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
i just found this game; it was extremely addictive. Thought I'd share it with you. http://www.albinoblacksheep.com/games/mindlessviolence
Wow, that will be really complex. Take it in small steps. Do you have the multimanager working already? Maybe you could just cause the staircase to become a bridge again after a short pause by triggering another multimanager, rather than trying to control it with the multisource. That way, you've already got all the pieces in place, you just have to add the part the turns the staircase back into the bridge. Also, it will be very difficult to get the staircase to turn; it can probably be done, but it will become very complex.
And so if one of the func_buttons turns off, you want the multimanager to stop on whatever step (1-10) it is performing? Is that right? It will be complex, but can be done...but it can't be done within the same multimanager. Let us know if that's what you're trying to do and we'll offer some suggestions.
Tell us what the multimanager is doing. Usually once you trigger a multimanager it has to complete it's routine. I don't know how to turn off a multimanager; although there is a way to set up two multimanagers in a loop and control the looping. Let us know what you are trying to do and we can help.
This post was made on a thread that has been deleted.
I like it when people post their compo maps early for all to see. But since I'm judging this one, I won't look at any maps until after the deadline. I don't want to get familiar with any of them until then.
This post was made on a thread that has been deleted.
Do you have your half-life executable set to accept development commands? Mine looks like this C:SIERRAHalf-Lifehl.exe -dev -console
Here's the example map for this. It looks great! Link
This post was made on a thread that has been deleted.
This post was made on a thread that has been deleted.
If you can put it in problem maps, I'll have a look.
I can only guess, but it seems that once you trigger any camera, that camera's hold time needs to be long enough to contain any other camera sequences you use in that map. I haven't tested fully, and I've only used multiple camera sequences that were back to back. For instance, I've never tried a camera sequence at the beginning and then another at the end of one map with a long time in between.
I didn't know there were 3 cameras... extend the first camera's hold time by 20 or more; that's the problem.
It sounds like the camera is being triggered a second time 1 second after it starts...perhaps on the 'fire on pass' property of that first path-corner? I've found that I have to place the camera near/behind it's first path-corner. Also try a faster acc/dcc speed like 500/250 and initial speed 85; that's what I use in my maps. Also, moving camera through its path corners is like driving a car on ice; it tends to overshoot the path when turning. The paths are more like suggestions to the camera entity.
This post was made on a thread that has been deleted.