New configs for GF 3.1

[Rovastar]

Not done many new flowfields for a bit but now we have funky new commands I can recreate theta.

Just taking some of my existing configs and changing them a buit to add a new theta value.

You will require the new Gforce 3.1 beta so it is only for users taht have purchased it.

Code: Select all

//Rovastar - Everflow Flower (Offset Remix)
//By John Baker (Rovastar) www.milkdrop.co.uk
Aspc=1 

A0 = "0.001*((10+ rnd( 10 ))*((rnd( 1 ) *2) -1)) "  
A1 = "45+ rnd( 35 )"  
A2 = "0.001*((10 +rnd( 20 ))*((rnd( 1 ) *2) -1)) "  
A3 = "60+ rnd( 30 )"  
A4="(0.01*rnd(70)) -0.35" // x offset
A5="(0.01*rnd(70)) -0.35" // y offset 

D0 = "x+A4" //newx
D1 = "y+A5" //newy
//D2 = "sqrt(D0*D0 +D1*D1)" //newrad
D2 = "atan2(D1,D0)" //newtheta 

srcX="x+(A0)*sin(D2*A1)"  
srcY="y-(A2)*cos(D2*A3)"  

Vers=310

[Rovastar]

Another

Code: Select all

//Rovastar - Cosmic Mosaic (Offset Mix)
//By John Baker (Rovastar) www.milkdrop.co.uk

Aspc=1

A0 = "0.0001*((30+ rnd( 50 ))*((rnd( 1 ) *2) -1)) "  
A1 = "50+ rnd( 50 )"  
A2 = "10+ rnd( 15 )"  
A3 = "0.0001*((30 +rnd( 50 ))*((rnd( 1 ) *2) -1)) "  
A4 = "50+ rnd( 50 )"  
A5 = "10+ rnd( 15 )"  
A6="(0.01*rnd(70)) -0.35" // x offset
A7="(0.01*rnd(70)) -0.35" // y offset 


D0 = "x+A6" //newx
D1 = "y+A7" //newy
D2 = "sqrt(D0*D0 +D1*D1)" //newrad
D3 = "atan2(D1,D0)" //newtheta 


srcX="x+A0*sin((tan(1-D2))*A1+((D3)*A2))"  
srcY="y-A3*cos((tan(1-D2))*A4+((-D3)*A5))"  

Vers=310

A pic of it

[JayPro]

That's really funny in an odd sort of way....
I'm still on 3.0.1 and these work ostensibly as advertised.

I.E.: These are supposed to be variably offset from mid-screen.

BTW: You have two D vars separated by a comma accidentally.

[Rovastar]

I don't understand how they work or you on v3.01

But good anyway.

I fixed the comma thing it seemed to work anyway but play it safe.

It is a little more complicated to emulate the srcR -srcT configs but I am sort of getting there.

Code: Select all

//Rovastar - Gravity Trap
//By John Baker (Rovastar) www.milkdrop.co.uk

Aspc=1

A0="( trnc( 5 + rnd(5) ) )"
A1="( trnc( 5 + rnd(5) ) )" 
A2="(0.01*rnd(80)) -0.4" // x offset
A3="(0.01*rnd(80)) -0.4" // y offset 
A4="( trnc( 35 + rnd(58) ) )"
A5="( trnc( 35 + rnd(58) ) )" 

D0 = "x+A2" //newx
D1 = "y+A3" //newy
D2 = "sqrt(D0*D0 +D1*D1)" //newrad
D3 = "atan2(D1,D0)" //newtheta 
D4 = "D2 - 0.5*sin(D3*A4)" //newnewrad 
D5 = "D3 - 0.5*cos(D2*A5)" //newnewtheta

srcX = "x+(D4*cos(D5*1))/180"
srcY = "y+(D4*sin(D5*1))/180"

Vers=310

[JayPro]

The comma's still there in D3.

I replaced it with "*".

Maybe I'm missing something, i.e. it has a different function in the streamlined code?

[chkman]

D3 = "atan2(D1,D0)" //newtheta

Please see topic Atan2 takes 2. Yer supposed to have two arguments to it. Somehow the old version could use just one but 3.1 requires two meaning that a 2nd param be added to older flows or change it to atan if you're lazy like me.


http://forums.soundspectrum.com/viewtop ... 434ce466aa

[JayPro]

That's really nifty and all; but this doesn't answer one question (actually two):

If this is for v3.1, why do the other offset flields work on my machine with v3.0.1?

Secondly, I changed the comma'ed statements in atan2....

To wit: atan2(D var, D var)

for both aforementioned fields to multipliers.

To wit: atan2(D var * D var)

It seemed that having the comma there initially didn't yield the expected results; but changing comma to "*" did the trick.

Yet now, for the third field, it seems that the comma *is* necessary (as it apparently is now supposed to be) to get it to work.

Really strange, this........

[chkman]

Okay, here is a simpler one:

A0=".04 + rnd( .05 )"
srcR="( 1 - A0 * atan2(r,pi) ) * r "
srcT="theta +.0025"
Vers=100

==============
Now changing the one line to:
srcR="( 1 - A0 * atan2(r) ) * r "

will kill it under 3.1 but I just checked 3.01 and it still works. By kill it I mean that srcR will always be zero and the whole screen will flash at times.

==============
Same with:
srcR="( 1 - A0 * atan2(r*pi) ) * r "

It is still giving one param and killing the line.

==============
Now taking the original line:
srcR="( 1 - A0 * atan2(r,pi) ) * r "

and pulling out the atan2:
D1="atan2(r,pi)"
srcR="( 1 - A0 * D1 ) * r "

and it still works the same.

=============
Now killing D1
D1="atan2(r*pi)"

will still give you a live flow but different:
srcR="( 1 - A0 * D1 ) * r "
because D1=0, A0*D1 will be zero and 1 * r is r. So it is watchable but the D1 is zero coz 3.1 can't compile it.
============
Make it:
D1="atan2(r*pi)+.5"
and it will be the same coz it's dead.

Well, I got a new flow out of it.

[JayPro]

So would it be right to say that the optimized atan2 computes multiple variables or integers using:

1) A comma within the source statement itself

and/or

2) a multiplier within an A or D Var?

My math/programming skills are really showing now...

[willrob]

With no mth skills, I can only report that all of the above fields work on my Mac running G-Force 3.01. Perhaps the 3.1 variables won't show until I switch to 3.1, but as is they work fine.

[chkman]

JayPro,

2) a multiplier within an A or D Var?

No, I don't see it.

Same with:
srcR="( 1 - A0 * atan2(r*pi) ) * r "
It is still giving one param and killing the line.

This is using the * which gives atan2 the result of r*pi and no 2nd parameter which it needs. Try it, it will give a 'strobe' screen coz srcR = 0.
You can have r*r*r*pi*pi*pi but you still need ,pi or comma something. You are breaking rules of syntax just like not having enough or too many closing parenthesis.

Then I showed this:

and pulling out the atan2:
D1="atan2(r,pi)"
srcR="( 1 - A0 * D1 ) * r "

but that doesn't work. It should be D0 not D1. I was trying it again and saw my mistake.
Anyway, changin r,pi to r*pi still wipes out D0. The point I was trying to make was that with D0=0, srcR boiled down to being just r for a value. So it might look okay but it's not the same.

In the above flows by Rovastar you are confusing G-Force from giving a value to D2 if you change the comma to a *. You still have a flow because srcX="x+(A0)*sin(D2*A1)" is "x plus A0 times sin of ZERO times A1". Move the bad D2 =atan2(D1*D0) into it to get srcX="x+(A0)*sin(atan2(D1*D0)*A1)" and you will see the strobe coz the syntax error kills the entire srcX line just like adding )))) to the end.

So in other words, no, not your point 2 just

1) A comma within the source statement itself

willrob,
Correct and incorrect syntax will work under 3.0 but not under 3.1. When you update, any flows with atan2 need 2 parameters separated by a comma.

[Rovastar]

That's really funny in an odd sort of way....
I'm still on 3.0.1 and these work ostensibly as advertised.

I.E.: These are supposed to be variably offset from mid-screen.

BTW: You have two D vars separated by a comma accidentally.

JP I will explain more about how multiple parameters functions like the new atan2(var1,var2) work later.

But why are you not using 3.1 beta? You can download it now for Macs.

Initaily I though you were refering to the commas at the end of a couple of lines like:

Code: Select all

D1 = "y+A5", //newy
D2 = "atan2(D1,D0)", //newtheta 

As I left a couple in there and since removed them. Adding to the confusion more.

[JayPro]

But why are you not using 3.1 beta? You can download it now for Macs.

I have an issue with a few of my HSV colormaps that I'd like someone to help me look at till I can feel OK about everything.

BTW the two maps in question aren't bundled with 3.1.

Maybe you or someone else can help me figure it out????

Thx.

[chkman]

JayPro wrote:

a few of my HSV colormaps that I'd like someone to help me look at

Don't just stand there jawing, let's see 'em!

[JayPro]

You'll hafta go back a few threads and see:

Colormap Issue in Beta 3.1.