Minor Particle performance issue (Raining Oscillo's)

JayPro · Post by **JayPro** » Thu Oct 15, 2009 10:50 am

Greetings;

This particle in this version of GF shows only one falling beam at the RH side of the screen. The code is as follows:

Aspc=0

Stps="40"

NUM="10 + rnd( 8 ) + rnd( 8 )"

A0="t" // Record start time

A1=""
A2=".03 * ( 2 + rnd( 3 ) )" // The width of each scope
A3="rnd( 7 )" // Time offset variance
A4="3 * a2" // Magnitude scale

B0="seed(ID * a0 )" // Seed the particle thread
B1="rnd( 2 )" // Pick starting y
B2="rnd( 2 - a2 ) - 1" // Pick starting x
B3=".01 + rnd( .08 )" // Scroll speed

// B3: The base y of the scope
B4="2.2 * ( wrap( b1 - b3 * ( t - a0 ) ) -.5 )"

Pen=".95"

X0="b2 + s * a2"
Y0="b4 + a4 * mag( .7 * s ) * sin( s * PI )"

LWdt="1"

ConB=1

Meta="reactive=1 detail=3 density=3"

Vers=392

I tried updating the Vers number and updating seed to srand. The rest of the syntax seems okay to me. Can someone pls advise? thanks.

juxtiphi · Post by **juxtiphi** » Thu Oct 15, 2009 4:50 pm

Hi Jaypro

I dont know a darn thing about this stuff , I wish I could help you,

but Forum member bnh has a problem with scripting and I think you could probably help him sort it out his thread is right above yours

Baldufa · Post by **Baldufa** » Mon Oct 19, 2009 5:23 pm

I have the same problem in two diferents pc since 390 version

JayPro · Post by **JayPro** » Mon Oct 19, 2009 5:54 pm

Which ones? If you can point them out for me, I can take a look at the syntax and try pinpointing the matters.

BTW : It looks as if my issue was solved adding "NUM_S_STEPS" to the "t" value in variable AO (See above-posted code).

Post by **andy55** » Mon Dec 28, 2009 4:30 pm

Nice catch, JayPro -- I'll have this fixed for the next release. In the meantime, you can just edit that line to "seed( ID )" for now.

JayPro · Post by **JayPro** » Mon Dec 28, 2009 6:15 pm

I did this:

A0=t^B0 with B0=srand(ID * A0)

it works fine...it may be more of an Oscilloscope Monsoon; but ii like a lot of 'em coming down anyway.

jerohm · Post by **jerohm** » Mon Dec 28, 2009 7:43 pm

Due to some other problems that I had eariler, I was starting to think that 't' always started at '0' at the inception of a config... no matter what the documentation said. If this WAS true, A0='t', t-A0, would STILL work right... On XP anyway, clock() and time() don't seem to be implemented either, so I resorted to some combination of the addition of 't' and ID to form a srand(seed)... which LOOKS to be no better than just being a function of ID alone.

RE "A0=t^B0 with B0=srand(ID * A0)"

technically, I didn't THINK you SHOULD be able to set 'A' variables with 'B' ones ... initialized or NOT ... so I SUSPECT 'A0' is being reduced to '1' because of the whole raising to the '0' power thing.