1  |   Order by index

Jul 28, 2002, 3:25am

I'm not sure if this has been mentioned already, but if someone on the
beta team could post this to the beta NG, that'd be great:

Corona Bug

When trying to set the corona command on an object using astart/adone,
you have to set the delay very high (>500) in order to see the corona,
and even then it blinks on and off. This could be similar to the light
bug a while back where the light would blink on and off if set with
astart/adone. Any way to fix this?

"create name a, animate me . 1 1 500,astart;adone corona halo
name=a,astart a"

--
Goober King
Proof that Goobers ARE as dumb as they look.
robrod at prism.net

Jul 28, 2002, 9:31am

I think its because coronas Fade in, so it will take about 500 to show em to
their full strength

Da Goober said:

When trying to set the corona command on an object using astart/adone,
you have to set the delay very high (>500) in order to see the corona,
and even then it blinks on and off. This could be similar to the light
bug a while back where the light would blink on and off if set with
astart/adone. Any way to fix this?

- Mark
*=D at he who knows*

Jul 28, 2002, 4:16pm

I was more concerned with getting rid of the "blinking effect". Since
astart/adone constantly refreshes the command, it causes the corona to
fade in, then blink off and fade in again, ad infinitum. I was hoping
they could find some way to make it only fade in once. They somehow
fixed the light command when it had similar problems, so maybe they can
fix this too. *shrug*

[View Quote] > I think its because coronas Fade in, so it will take about 500 to show em to
> their full strength
>
> Da Goober said:
>
> When trying to set the corona command on an object using astart/adone,
> you have to set the delay very high (>500) in order to see the corona,
> and even then it blinks on and off. This could be similar to the light
> bug a while back where the light would blink on and off if set with
> astart/adone. Any way to fix this?
>
> - Mark
> *=D at he who knows*
>
>
>


--
Goober King
He who already knew that :P
robrod at prism.net

Jul 28, 2002, 4:19pm

Would require a complete rewrite of the corona enter / exit code I would
imagine. Try doing it the hard way, use the put another object around the
corona source, so it blocks it. Then use astart to make it visble off, it
should only fade in

Jul 28, 2002, 6:57pm

Ehem... I can see it now...

CAUTION: Use of the Corona command may cause severe epileptic seizures.

Better fix this, even if you have to rewrite it.

Chris


[View Quote]

Jul 28, 2002, 7:56pm

create corona flare1 size=99999, light color=white fx=flash

stick that on a object in awteen and look at it

- Mark

Note: Dont forget to delete it after

Jul 28, 2002, 8:25pm

I'd rather have the coronas fade in AND out, like in Grand Theft Auto 3. Yet another Roland inconsistency...

[View Quote] > I was more concerned with getting rid of the "blinking effect". Since
> astart/adone constantly refreshes the command, it causes the corona to
> fade in, then blink off and fade in again, ad infinitum. I was hoping
> they could find some way to make it only fade in once. They somehow
> fixed the light command when it had similar problems, so maybe they can
> fix this too. *shrug*
>
[View Quote]

Jul 30, 2002, 1:42am

fade outs work for me, eep.

Chris

[View Quote]

Jul 30, 2002, 7:20am

Uh, huh? You replied to Goober King, not me. Coronas don't fade out; they only fade in. Look again.

[View Quote] > fade outs work for me, eep.
>
[View Quote]

1  |   Order by index