posted 08-12- 11:29 AM CT (US)        

It runs great on a K6-2 333mhz, ATI Rage Pro, etc. (my old computer), but try to use the darkness technique on my 1.4 GHZ Athlon, and it just does a cruddy fade_down(). Disappointing to say the least.

To find out how I did it, check out the following scripts. It doesn't really make any sense how it works (at least it didn't to me at first), but my theory is spawning a lot fo dark2.c makes dink.exe halt the fade_down process before it was completed (hence, semi-darkness). I discovered this while trying to spawn a lot of bombs while fading down; I streamlined it to the point where it worked without having to use bomb sprites or sounds.

//dark1.c - to be spawned from another script
//&darkness - global variable, defined before dark1.c is spawned
void main(void)
{
int &bcount = 0;
loop:
spawn("dark2");
&bcount += 1;
if (&bcount < &darkness) goto loop;
//Darkness is between 70-100. 70 really dark, 100 really light
fade_down();
kill_this_task();
}

//dark2.c - referenced to in dark1.c
void main(void )
{
wait(1);
kill_this_task();
}

One other option (perhaps) is to do something like this:

fade_down();
wait(50);
loop:
fade_up();
wait(1);
fade_down();
wait(1);
goto loop;

posted 08-15- 03:03 PM CT (US)            

I did try something that kinda worked though (like you said, but I tried it a couple days ago).

//NEscript.c
fade_down();
wait(50);
spawn("fup");
spawn("fdn");

//fup.c
loop:
fade_up();
wait(1);
goto loop;

//fdn.c
loop:
fade_down();
wait(1);
goto loop;

posted 08-18- 01:11 AM CT (US)            

//speedtst.c
main ( void )
{
&speed = 0;
//&speed would be global.
int &script = spawn("tick");
wait(1000);
run_script_by_number(&script, "kill");
say("speed is &speed.", 1);
kill_this_task();
}

//tick.c
main ( void )
{
loop:
&speed += 1;
wait(1);
goto loop;
}

kill ( void )
{
kill_this_task();
}