Hi all,
I asked this in the beginners forum but noone could help me, so I posted it here.
I´m using this code to shoot at a box.mdl:

function spieler_schiesst() {
temp.X = 5000;
temp.Y = 0;
temp.Z = 0;
VEC_ROTATE (temp, CAMERA.PAN);
VEC_ADD (temp, CAMERA.X);
TRACE_MODE = IGNORE_ME + IGNORE_SPRITES + ACTIVATE_SHOOT;
TRACE (CAMERA.X, temp);
}

with the box having the following script:

action testbox {
my.frame = 1;
my.scale_x = 0.5;
my.scale_y = 0.5;
my.scale_z = 0.5;
my.enable_shoot = on;
my.event = testbox_event();
}

function testbox_event {
my.pan += 45;

}

The result:

Fatal Engine Error E 1513
WDL-Crash in spieler_schiesst

It works with and without the box in the level, the error only occurs when I shoot at the box and hit it.

The errormessage says "Fatal Engine error E1513" in the titel bar. The messagetext itself is:"WDL-Crash in spieler_schiesst"

What am I doing wrong???

most probably i feel its because of retriggering
of the event action infinitely and so just try
adding a WAIT 1; in the begining of the event action of the box.
hope that helps

I think we have some classic bracket problems
here.

In the "my.event = testbox_event();" line,
delete the "()". What you want to do on this
line is set "my.event" to the *pointer* (or
name) of the event function. But, by including
the "()" you force testbox_event to execute itself, returning a nonsense value (since
testbox_event doesn't have a reurn statement),
which gets stored as the function to execute when
an event occurs. Of course, there's no function
at that address/value, so the engine bombs.

I also think you need a "()" in the "function
testbox_event" line.

I hope this is some help in resolving your problem.

Coda.

Coda,

Thanks for that reply. I usually get it right, but when it doesn't work, I resort to trial and error because I did not understand what the () means.

I'm better now.

Thanks again.

-WildCat

Coda: I removed the () from the my.event line but the result is an error message: parameter unknown:testbox_event

changing function testbox_event into function testbox_event() didn´t do anything.

zazang: the wait 1; didn´t change anything either

Thanks a lot for your help guys, but that was not it. Maybe somebody can post a working code snippet, so I can compare it to mine....

Not sure if it is a problem in the newer versions but seems like some of the older versions required you to either put the event function before associating it with an action or using the command "SET" :

//using SET MY.EVENT

action testbox {
my.frame = 1;
my.scale_x = 0.5;
my.scale_y = 0.5;
my.scale_z = 0.5;
my.enable_shoot = on;
SET my.event, testbox_event;
}

function testbox_event {
my.pan += 45;

}
///////////

or:

//using MY.EVENT before the ACTION

function testbox_event {
my.pan += 45;

}

action testbox {
my.frame = 1;
my.scale_x = 0.5;
my.scale_y = 0.5;
my.scale_z = 0.5;
my.enable_shoot = on;
my.event = testbox_event;
}

I think (hope? ) that Keebo has hit it on the
head: keep my suggested changes, AND move the
definition of the event function up before
the "my.event = " line.

A suggestion for anyone who's interested: newer
versions of A5 allow you to use "function prototypes" to, in effect, say "hey, here's a
function that I haven't defined yet, but I will
later on so its OK for you to reference it now".
If you create a prototype for EVERY function you
write, and if you store them in one big wdl file
that you include BEFORE all others, you'll find
that you no longer have to worry about the order
of function definitions in your code.

In fact, I've taken the above idea one step further.
(C programmers will recognise this instantly. ).
Say I'm writing some wdl code about movement. I
put EVERY variable declaration and EVERY function
prototype into a "move_h.wdl" file. My "move.wdl"
file then just consists of action/function definitions.
The advantage of this approach is that, provided
you include all your "????_h.wdl" files first,
you don't have to remember anything else about the
order in which you include files. All the variables
are declared, all functions are prototyped before
any of them are referenced.

Merry Christmas All,
Coda

I´ll try this when I get home from work tonight and then tell you what happened.

OK, I did some tests:

1)keebo: //using MY.EVENT before the ACTION
no result, no change

2) keebo://using SET MY.EVENT
result: unknown SETmy keyword

3) Coda: I kept the changes as far as they didn´t create an error (removing "()" from my.event line)

Somehow I´m glad it was not the simplest newbie-error but on the other hand I didn´t get anywhere yet. Still thanx to all who tried and keep on going with your ideas! It doesn´t really make sense to keep on working on an FPS with an errormessage everytime you hit a NPC.

I forgot:
I´m using 5.12 commercial on a Win98 AMD900 with 384mb RAM and a GForce 2.