How does the logic system work?
I started working a little bit with the Spark editor yesterday and I gotta say that I really like it. So I decided to make maps for NS2 in my spare time ( if there is any ).
Now my first question would be, how does the logic system for the game work? I havent seen any flowgraphs or anything similiar yet so I´m quite confused.
I want to make flickering lights, rotating fans, etc.
Any help is greatly appreciated!
Now my first question would be, how does the logic system for the game work? I havent seen any flowgraphs or anything similiar yet so I´m quite confused.
I want to make flickering lights, rotating fans, etc.
Any help is greatly appreciated!
Comments
Add an cinematic entity to the world and search in the file slot for "cinematics/environment/light_repair_downflicker" and set the entity to loop. As far as I know that is the only flickering light that is predefined. So you have to live with the light color ;)
For the fans: Add a prop_dynamic entity to thw world and search for "models/refinery/sthsth/fan1" for example. If you need to see how that works, just search for a fan in one of the official maps. But don't forget to enable "all" layers so you will see more from the map in the editor. They are loaded by default with only a small room.
If you have any questions, feel free to ask. We have a lot of friendly mappers around. Welcome to the group and whatever you do, don't rage too soon when you work with the spark editor. Creating maps with it is like driving on a rocky road with a sportscar. But if you work long enough with it, you will get used to it and avoid many spark traps. Save often :D
Btw, I gotta say that I really like the Spark editor till now. I´m working as a leveldesigner for big companies, so I´m used to work with editors/builds that are utterly broken ( always amazases me, how the ###### we made maps under such circumstances ). In that case I love the Spark editor because its finaly something that actually works, and which is quite accesable!
PS: I really like NS2, so I figured I´ll use most of my spare time making maps for it. ( It´s not too much time :P )
<!--quoteo(post=1958371:date=Aug 7 2012, 10:35 AM:name=schkorpio)--><div class='quotetop'>QUOTE (schkorpio @ Aug 7 2012, 10:35 AM) <a href="index.php?act=findpost&pid=1958371"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Creating faces can sometimes be a bit of a pain until you know how the editor makes decisions to create the faces (or not create them). Some tips are:
If you have overlappnig lines and verticies - select the Selection Tool - and then go Edit > Weld Vertices. This merges them all into one, and then you should be easily able to make a face (this is usually the biggest problem from a face appearing - the editor doesnt' know which lines and verticies to use if they are overlapping, so welding them all into one fixes this)
If you double click a line it the editor will automatically select all nearby lines - this makes creating faces faster, and also is a quick way to determine whether you should weld or not.
Edit: some people don't like the weld however, because it means that you won't be able to control your faces seperately any longer since they are welded together - e.g. if you pull on one vertice or line that joines to another face, this face will also be pulled.
One way around this if you decide you need to go back and change a whole face, is to select the face and CTR+X it (to cut it) and CTRL+V to paste it (it will appear in the same location) but it will now have its own set of lines and verticies so it no longer will pull the other faces and lines - just weld it back in again if need to.
Get used to the ALT+C to create a face, and CTRL+F to flip the face (as 1/2 the time it appears on the wrong side). Remember these are only available when you have the selection tool selected (SPACE BAR). Use these 3 key combos will speed your work up significanlty :)
Also one thing that got me early on was the Texture Lock - it only appears when you have the move tool selected (down near the vertice/line/face/lightprop/entity/ filter).
stick to the grid -do a greybox of your room with 32unit grid first, then do some details with 16 or 8" grid. rotating and moving objects can sometimes pull things off the grid (not even1" will align) so try cycling the grid align points with the ";" and " ' " keys (or is <> keys? don't remember off the top of my head lol).
.<!--QuoteEnd--></div><!--QuoteEEnd-->
Right now we can't choose flickering etc. like in Worldcraft/Hammer. I hope we will get all those oldschool things after 1.0 but anyways, if you don't want to use the cinematic editor, you can use the following:
Add an cinematic entity to the world and search in the file slot for "cinematics/environment/light_repair_downflicker" and set the entity to loop. As far as I know that is the only flickering light that is predefined. So you have to live with the light color ;)
For the fans: Add a prop_dynamic entity to thw world and search for "models/refinery/sthsth/fan1" for example. If you need to see how that works, just search for a fan in one of the official maps. But don't forget to enable "all" layers so you will see more from the map in the editor. They are loaded by default with only a small room.
If you have any questions, feel free to ask. We have a lot of friendly mappers around. Welcome to the group and whatever you do, don't rage too soon when you work with the spark editor. Creating maps with it is like driving on a rocky road with a sportscar. But if you work long enough with it, you will get used to it and avoid many spark traps. Save often :D<!--QuoteEnd--></div><!--QuoteEEnd-->
On this topic, I notice that you cant scale them with prop_dynamic, they just scale back to their 1:1:1 size. Is there anyway around that or is it an engine thing?
There's no way around that at the moment - it's something to do with scaling the physics mesh.