Search results

I get that when I alloow hammer to run my map, so try running it from the game yourself.

It's always better to start around 0,0,0. If you run out of space from there theen you've either got a huge map or possibly a rather odd design. In the first case you should reconsider, in the secon case you can just move the map. That way ou wont have this trouble. But I'm glad you solved it :)

Compile is fine. What's the error when you try to load the map? Oh, and load the map manually, don't let Hammer do it for you.

NOt a problem. Dont forget to disable it if you want to map for OrangeBox.

Load game and type "developer 2". Now load map. If you have invalid spawn point then the console will show errors!

launch the sdk with the parameter -engine ep1 That should load up the old sdk with the old games as options in the list.

Several trains on one track? No, they drive through each other and I assume the console reports one or two errors.

Not a problem. I like working things like thiese out. For the record, what was messing it up for you before was having two physically simulated objects / two colligin objects inside each other. (By this I mean either 2 phys objecs or one dynamic an one phys) Phys object is grabbed by the...

I had to get a cure for this one, and luckily I found one... Here is what you need to create a radio that breaks on bullets and physics using a non-breakable model. 1. prop_dynamic_override This shows our radio and nothing else. The _override allows us to use props meant to be...

And get the hammer 3.5 beta exe so that you will be running hammer 3.5 instead. You can find it at the valve collective, i forget the link. That one adds modelv viewing to the 3d window which is a godsend.

So make a physbox which you can darg the radio around with and then have that trigger the radio to kill itself once damaged. Also parent an env_shooter to the physbox and have that shoot out a multitude of gibs.

Does HL2DM use CSS gcf? If so then there is a breakable radio there. From cs_office.

Well, the func_breakable is really not meant to be dragged around and whatnot so I can see it causes lag and all of that. However, a physbox is really just a physically simulated breakable that can be set to being nonsioliod and all of that. Plus it's meant tio be dragged around. :)

It is a bit stupid in my opininon... But I guess it could come in handy of you have serveral trains with different speeds on the same track.. But that doesn't happen all that often...

The path_track entity has a New Train Speed keyvalue or something like that anyway. If I remember things correctly then this scales the train speed instead of actually settnig a new speed. So just make a few path tracks before the stations that slows the train down...

I'd go with the breakable but make sure that the breakable is nonsolid and all that....

Doesn't the sprite size override the set size?

masters are legacy keyvalues I think. You just need a text and a position for it and then a trigger. So it should really be working for you. Could you show us a screen of the settings? And does your map compile properly?

Aha! You are not the first to assume that I am not lazy. And that is unfortunatley incorrect. I am. I will not make your map for you. That would be stupidity. However, if you tell me what kind of map you had in mind (cp_, ctf etc) then I will tell you what kind of entities that are needed for...

What did the compile log say? (The bunch of text that pops up when you click run) I don't think that URL bit was related.