[behavior] rex_light

mattb

Beautiful demo.

Could I add this export result into my public demo list? And add this sample capx in my document page?

I will add your name (mattb) at the left-down side.

rexrainbow how to download this plugin ?

—

The most easy way is using this tool. Or check the document of this behavior.

rexrainbow - please do Here's a version with better textures & opacity falloff...

mattb

Thanks. I had put your demo capx into the document of this behavior.

—

The most easy way is using this tool. Or check the document of this behavior.

alright! thanks very much Rex! your plugin n behavior very useless for me

Hi rexrainbow I think I found a bug..

The behaviour seems to lag one frame behind, if you have many rays spinning around very fast you can see it easier, like this:

https://dl.dropboxusercontent.com/u/533 ... xlight.mp4

https://dl.dropboxusercontent.com/u/533 ... light.capx

if you manually set light point every frame, it fixes it but is slower.

keepee

It's because that the behavior is running before events in a tick.

rexrainbow that's what I thought.. do all behaviours have to run before events? If so, I didn't know that.

keepee

Objects or behaviors all could do something before and after events. Most of them ran before events, only few behaviors ran after events.

For example, official pin behavior would set related position after events to ensure that the changing of position of pinned object had done.

Hey rexrainbow, this plugin is awesome!

I have been trying to make a ray system for lasers for a while now, but I could never produce something that didn't kill performance whilst maintaining high accuracy. My final attempt involved setting the laser to it's "maximum width", then dividing the width until it no longer collides, then multiply the current width a little bit blahblah, it didn't work too well and performance was bad. But then you bless us with this beast of a Behaviour!

Before I attempt to even begin to interpret how you made this plugin work, could you tell me how you done it in pseudo-code? Would this behaviour essentially be possible to recreate in events?

I would think the most accurate but CPU-intensive way is to increase the width +1 in a loop until it hits a wall then -1 width and done. I'm very curious about how done this

Jase00

Almost closed. I first starts from current width; decreases width until no collision; then increases width until just collision. See this

The decreasing/increase is

current width - delta width[/code:3pi7dcv4]
[code:3pi7dcv4]current width + delta width[/code:3pi7dcv4]
delta width will increasing by multiplier 2, i.e. 
[code:3pi7dcv4]delta width = delta width *2[/code:3pi7dcv4]

Please tell me how to do the second sample? Or give a file of it if you have.

VVK

Is it?

Thanks for this plugin! I was wondering if there was a way to include objects that don't have the solid behavior? I would like to use this as sort of an instant bullet but I don't want enemies to be solid.