I looked over your code really good... I'm sure it would work fine.
Just wont do what mine is intended to do?

I assume this is more of a tourist elevator?
just stopping ocasionally....?

Quote:

---

define _destination, skill20;

---

where are all the destinations for the other floors?
you only have 1? Or maybe I missed something.

Quote:

---

var gc_elestop[5] = 0, 200, 400, 600, 800;

---

I'm not sure how exactly your implementing this
I know its for the stop pints but I just don't
understand how your using it?

I'm guessing you just have 1 destination stop
but several frquent stops on the way?

On another note...
I tried using "time" pretty much the same

Quote:

---

my._destination

---

except figuring that factor in
unless you count elevator_pnt.z as the
equuilivalent to my._destination?

Also I'm trying to make compatible with A5 as I still use
it often. I don't think:

Quote:

---

time*speed_constant

---

is an A5 feature though there are some similar I beleive that
I might be able to substitute. Just wanted it to
be more Universal

I do thank you for all your input!

Maybe if I can scan through your code here I can
find a better way to implement my own "button contolled"
elevator.



*** Teutonic Darkness ***

...

you have 5 stop-positions (can be varied).
var gc_elestop[5] = 0, 200, 400, 600, 800;

The Property ._destination is set to the wanted destination and the moving is activated by setting the flag ._moving=on.

You want to level 3? ent_elevator._destination=3;ent_elevator._moving=on;

time: use time to have a universal gamplay (meening of time).
time*speed_constant is a factor and will just vary the speed of the animation. (Warks also with A5).

mercuryus

Hi!

Here's some little description:

my._direction=1-2*(my.z>gc_elestop[my._destination]); // go up if not my.z>my._destination (over the dest.point)
ok - this part is havy to understand.
rule no.1 in programming fast code is to use methematic!

At the beginning our evelator (ele) has a arbitrary z-position.
Triggert by an event (in my case the 1-,2-,3-,4-,5-key) i tell the ele his destination(-index of the stop-position-array) and tell him also to move on (_moving=on).

In the action you can see that ele is waiting until _moving==on. (//wait for activating)
Now he calculates the direction he needs to move:
(read the line from behind to the beginning!)

1. gc_elestop[my._destination], this is one of the stop-positions declared at the top. An array always begins with index 0, so the first value is gc_elestop[0], the second gc_elestop[1], a.s.o...
(example: let say ele has the z-pos 0 and _desination is 3 -> gc_elestop[my._destination] = 600)

2. (my.z>gc_elestop[my._destination]), is a logical comparison like "if my.z>gc_elestop[my._destination]" and has 0 (off) or 1 (on) as result, what we can use for calculation!
(example: my.z>gc_elestop[my._destination] -> 0 > 600 = 0)

3. 1-2*(my.z>gc_elestop[my._destination]), (multiplication comes bevor substraction): I want have 1 if the ele should go up, and -1 to move down.
take the 1: this means go up
take the -2*(my.z>gc_elestop[my._destination]: this means substract 2 times the result of the comparison. (2 times to get not 0 as the total result but -1)
(example: 1-2*(0>600) = 1-2*(0) = 1)
(example it ele is upper the destination: 1-2*(800>600) = 1-2*(1) = -1)

So we have the direction.

What does _direction?

Look at line my.z+=time*gc_ele_speed*my._direction
It means: move ele (at the z-axis) in the _direction multiplied my time and speed_constant. (of cause there is NO collision-detection.)

Where to stop?
In the loop where the ele moves we constanly ask if the ele has passed the actual stop-position depending of his both possible directions.
If he has passed (after the loop), we set the exact position and stop the ele (_moving=off), so he will wait again until _moving=on is set (by a trigger).

hope I could help?

mercuryus

Thanks,

Really appreciate the breakdown of everything!
I actually began messing around with trying this after
studying it real closely.

I came across a major problem when you actually
reach the destination though!

Apparantly when you reach the destination
The

Quote:

---

ent_elevator._moving==on

---

Is not being set to off...

So a a result it does nothing and will only sit there and
Shake real funny.

I'm sure this is a easy fix... and
I'm going to look into it
Probally just need to add ent_elevator._moving==off.

just letting you know!




*** Teutonic Darkness ***

Hi mercuryus, I've found a little bug. I assigned the elevator action from your script to my entity ( mdl ), everything works, I adjusted the numbers in the array, it can also travel from level to level, BUT when i stand on it and press for example, the 2, it goes up, but passes right through the player. Ive checkmarked the polygon flag in the main options, not in the script, tried with only checking Bbox, and tried adding my.polygon = on in the script, nothing happens, the same with the line my.passable = off, and I recompiled the level after each time. Please help.

Hi Edgecrusher!

The elevator-script only handles the entity (mdl/mapentity) of the elevator-platform, not the addicted objects.
If you want to move an object (e.g. the player) with the elevator you have to handle this separate.

There are many solutions for doing this, depending on the way you move your player. A simple way to move the player addicted from other objects is to use forces and the absolute vector of c_move(....

Here you can see one idea of moving the player with the elevator. The elevator-script is modified to use and share z-forces. At the end there is a draft how to implement the forces to your player-script.

have fun, mercuryus

Hi, mercuryus can you upload that .txt file again, please? I'm looking for good way to make an elevator. Thank you.