 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
I downloaded the movlight.zip by Marc Fontaine. A modification of a func_train to use for a moving light source in Quake, but
I didn`t get it working. (I use QuArK) Can somebody help me ? what are average times for a map of say, 1k brushes, 500, 4k?
i have this tiny map which is taking forever to compile. i think it's about 500 brushes, possibly less. i thought the whole point of d3 was that compiling takes a lot less time... windows reports d3 is using cpu cycles for something, and it's certainly eating up ram... does it just crash without telling you and stay frozen, pretending to compile? :P btw, no monsters in it, so it's not making any aas files either. i post to fast >_< just figured out what the deal is... apparently, i'm not doing skyportals right. :P
I'm sure someone can help but you need to give more information e.g. have you set up a light_move entity with path_corners, are you using the revised progs.dat or have you incorporated the qc files into your own progs.dat, is anything happening and if so, what?
Also, what is your expectation for this - it doesn't light up the room as it moves around, it is simply a moving light source: basically a glowing blob that moves. thanks for your answer. I`m a absolute beginner and had the idea of a moving light that lit up the walls while moving, but after some googling for that, I found out that it is very hard or probably not possible at all. This movlight.zip (found in the ID-Database) has an example map, but that has only a moving sprite, not a real light. Today I thought maybe the misc_fireball is something to use for this, but I`m not a programmer. I think this qc-stuff is to heavy for me.
What is the revised progs.dat ? OK, the moving sprite is all that happens. I don't know of any way of lighting walls and ceilings in the way a hand-torch would light a dark scene, which I suspect that is what you are looking for.
The revised progs.dat that I referred to was supplied in the movelight.zip and needs to be used in place of the standard progs.dat. It contains the necessary compiled The standard way of using these modifications is to set up a separate folder inside your Quake folder e.g. c:\Games\quake\movelight, and extract the files from the zip file into that. Then start Quake with the command -game movelight +map light. hi ladies!
i�m trying to make a http://trinca.no.sapo.pt/Quoth.qrk just made for two monster�s to test!!! i like Quoth mode a lot and i want to map more for it! so this might be nice when is finish :) and maby someone will find it nice also :| Yes, that was exactly the way I tested this "light-map", but as I say, it was only a moving sprite, not a light.
But this lava-blobs are looking like a moving light ( or is it just a fake ?), and if it is really a moving light, it must be possible to change this extension (qc.file) to something new, where you can choose the direction, speed, distance, etc... (in the editor) Than you have a mov_light extension. Of course you have to compile a custon progs.dat to get it working. Or did I talk nonsense, I don`t know ? Stop me if I'm wrong, but what you're saying is that you'd like an entity which emits light in the same way as a lavaball or a missile does - a small ball of dynamic bright light. The only difference is that you would like to be able to move this light like a func_train. If this is what you want, then this can be done fairly easily.
The movelight is an s_null.spr with an EF_BRIGHTLIGHT effects.
void() light_move = { if (!self.speed) self.speed = 128; if (!self.target) objerror ("light_move without a target"); self.noise = ("misc/null.wav"); precache_sound ("misc/null.wav"); self.noise1 = ("misc/null.wav"); precache_sound ("misc/null.wav"); self.cnt = 1; self.effects = EF_BRIGHTLIGHT; self.solid = SOLID_NOT; self.movetype = MOVETYPE_PUSH; self.use = train_use; self.classname = "movelight"; self.avelocity = '50 50 50'; precache_model ("progs/s_null.spr"); setmodel (self, "progs/s_null.spr"); setsize (self, '0 0 0', '0 0 0'); setorigin (self, self.origin); self.nextthink = self.ltime + 0.1; self.think = func_train_find; }; It is therefore a dynamic light in as much as it moves by use of path_corners but it doesn't dynamically light the set as it moves e.g. the flashlight in HalfLife. I think this is what jiri_b is after. could you just make a regular func_train, give it the ef_brightlight
Sounds about right, I'm trying to see if there's a way to make one that's also non solid. I think there is but it may be one of those hacks that's more trouble than it's worth. I'll see...
Otherwise that mod is the way to go, notice how in that code the entity is given a sprite s_null.spr. This is because an entity with no model does not get sent over the network, so clients won't see the light updating position. Good luck. I started that once but gave up early because it was so much work. Haven't got the files anymore, sorry.
I'm playing with the Vermis in a small test map and notice that he doesn't follow me (shooting) once I drop below a certain point: he just keeps firing at where I was. I'm no_clipping around the map just to get an idea of what he does.
Is there a specific number of units involved e.g. x units below his centre of origin? Also, is the spread of the missiles adjustable as if you are too far away you can just sit there and they always seem to miss. Perhaps it is a case that he only fits a certain kind of environment spacewise? Perhaps it is a case that he only fits a certain kind of environment spacewise.
exactly right. he, like all monsters, shoot in a cone around his fov. but unlike other monsters, his vertical size is massive, so you'll notice how he won't be able to shoot you when down around his 'waist'. and yes, his projectile spread is constant. after a certain range, the spores stop being a threat. designing an area for the vermis really is a matter of plopping him in first, and building the area around him. if your map has the vermis exposed all the way down to the bottom of the model, you'll need to keep the player away from it because he won't be able to attack you or grab you. on the other hand, if you keep him at grab height, then you can let him get as close to the vermis as you want. I tried the easy solution by necros, without qc, but could not get anything working. First tried it with a func_train, but without success. Than thought maybe better start simple and tried to built a fixed light and failed again.
Not shure if I set up everything right in quark. Here is a screen of the setting. http://www.kram-hochladen.de/files/25853/light-blob_test.jpg Whats wrong? help I once had a complete varation of all the possible moving light types, I'm searching...
please give me a link to the movelight.zip and I'll explain.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |