Hee,
Not strictly. Of course the 3 dimensionality is more due to the raw materials. I managed to include a bit of beginner's code, and in areas where I borrowed, I started changing coordinates more. I'm getting braver now. I avoided using pure black, and pure white as much as possible. A lot of floral motifs, beginning with a sphere(jaarka's) petals become 3d and translucent, they shimmer even. I'm keeping it in mind for wings, both fairy and butterfly. Also keeping it in mind for a possible alien motif, and flower petals(3 dimensional rotation instead of 2 dimensional rotation).
The illusion of 3d files were actually very difficult to make. I couldn't sleep last night, so the hours were easy to come by. Once I figured out how to get the tunnel effect with the sphere in the center, the rest sort of fell into place, and it became fun with designs and patterns. Just having Tuggummi's movement from Club Seizure, wasn't enough. I had to adjust for the fact that my "base" file(jaarka's sphere) has different coordinates. After that it's kind of a blur(I really should have taken notes).
I kept wishing the particle fountain APE had more options. Since every time I tried to use it, it just looked weak, I avoided using it(was so impressive when I first started fiddling around in the editor too🙁).
Also I learned more about customizing texer2, so I'm happy about that.
All in all the presets are very watchable(to me anyway😉) But that's why I decided to bring them here and post them. I'm wonderring if I even have an eye for what looks good in a preset.
Just about a week in and 3D allready
52 posts
That are some amazing presets! I like them (although some look too similar). My personal favourite is "Illusion of 3D filligree". But all in all you're doing a nice colorwork, for sure! 👍
So take this as an incentive to improve your coding-skills, step by step. Someday you'll be able to code a fountain, that is much better. I have to admit that i don't have a concrete idea right know how to do it, but it is possible, perhaps a more skilled avs'er can help you out.
Volunteers, one pace forward! 😉
Originally posted by NolitaAs many wise Avs'er said before: Nearly everything the built-in render-effects can, can be done with a superscope, and much better!
I kept wishing the particle fountain APE had more options. Since every time I tried to use it, it just looked weak, I avoided using it(was so impressive when I first started fiddling around in the editor too🙁).
So take this as an incentive to improve your coding-skills, step by step. Someday you'll be able to code a fountain, that is much better. I have to admit that i don't have a concrete idea right know how to do it, but it is possible, perhaps a more skilled avs'er can help you out.
Volunteers, one pace forward! 😉
Particles, fancy formulas, and having Unconed's brain helps a lot too.
Thanks for the replies. ^..^ you're so supportive and helpful. So far nothing but constructive criticism🙂 that's the kind I like.
S-uper_T-oast, I'm a little confused by your post "Particles, fancy formulas, and having Unconed's brain helps a lot too." I think you're mostly kidding, but I don't get the bit about Particles and fancy formulas. I didn't use particles, unless texer2 counts as particles. Fancy formulas? I totally credit where I got bits of code, presets, and tutoring from. I thanked everyone I could think of, except for god and my mother😉. I mentioned Unconed in a previous post, but except for learning where to place the color elements in the tree, I didn't use anything from Unconed. I did use a great deal of the information from Pak-9's manual however.
I also used a bit of info from an online tutorial that breaks down ellipses into plain english, with examples(used it to help with movements, dms, superscopes, and one of the texer files). Right now I'm just not comfortable with doing more than changing values and parameters(still learning how everything works).
On the other hand though, I really think you're just picking on me, on account of I'm the new kid, and well, it's just so easy. I just don't quite get the joke. That's what emoticons are for you know? A smiley or a quick "j/k" can shine a whole different light on things🙂
Not angry, just a bit confused.
S-uper_T-oast, I'm a little confused by your post "Particles, fancy formulas, and having Unconed's brain helps a lot too." I think you're mostly kidding, but I don't get the bit about Particles and fancy formulas. I didn't use particles, unless texer2 counts as particles. Fancy formulas? I totally credit where I got bits of code, presets, and tutoring from. I thanked everyone I could think of, except for god and my mother😉. I mentioned Unconed in a previous post, but except for learning where to place the color elements in the tree, I didn't use anything from Unconed. I did use a great deal of the information from Pak-9's manual however.
I also used a bit of info from an online tutorial that breaks down ellipses into plain english, with examples(used it to help with movements, dms, superscopes, and one of the texer files). Right now I'm just not comfortable with doing more than changing values and parameters(still learning how everything works).
On the other hand though, I really think you're just picking on me, on account of I'm the new kid, and well, it's just so easy. I just don't quite get the joke. That's what emoticons are for you know? A smiley or a quick "j/k" can shine a whole different light on things🙂
Not angry, just a bit confused.
Okay one thing i just have to mention: There really isn't a need to use complicated renders like 3D torus's or likes if you're just going to add a movement at the end which totally makes the whole thing unrecogniable. And especially if you use other people's stuff you can hardly justify the use of it.
It's like adding a mirror and a r=r*5 movement at the end of UnConeD's "Tokyo Bullet", it just destroys it completly and makes a mockery out of the original.
It's like adding a mirror and a r=r*5 movement at the end of UnConeD's "Tokyo Bullet", it just destroys it completly and makes a mockery out of the original.
I am almost always joking around here (just rummage around in the recycle bin for many good examples), but the mian ideas are there.
One way to make a fountain is to create a particle engine. This collection of equations treats each dot in a superscope as it's own individual point or particle, and keeps track of each particles indivdual position, speed, direction, color, etc... The formulas and routines that you write for the engine cause it to have different effects. Some things you can do are motion, gravity, direction, and speed. From those, you cause each specific particle to move in a specific way, and this (in your case), would make the fountain.
The unconed's brain part refers to the fact that his fountain presets are the ones that most readily pop to the top of my head. This is also a pretty advanced way of making superscopes and requires you to know a whole lot about the way a superscope draws the shape, and the coding you can use.
One way to make a fountain is to create a particle engine. This collection of equations treats each dot in a superscope as it's own individual point or particle, and keeps track of each particles indivdual position, speed, direction, color, etc... The formulas and routines that you write for the engine cause it to have different effects. Some things you can do are motion, gravity, direction, and speed. From those, you cause each specific particle to move in a specific way, and this (in your case), would make the fountain.
The unconed's brain part refers to the fact that his fountain presets are the ones that most readily pop to the top of my head. This is also a pretty advanced way of making superscopes and requires you to know a whole lot about the way a superscope draws the shape, and the coding you can use.
btw is there any tutorial available concerning this "individual particle(=point) treatment"? Id like to learn this technique. Till now i only know to work with:
frame:
counter=0
point:
counter=counter+1
x=equal(counter,1)*xcoord1+equal(counter,2)*xcoord2+...
y=equal(counter,1)*ycoord1+equal(counter,2)*ycoord2+...
frame:
counter=0
point:
counter=counter+1
x=equal(counter,1)*xcoord1+equal(counter,2)*xcoord2+...
y=equal(counter,1)*ycoord1+equal(counter,2)*ycoord2+...
Okay, so I'm making a mockery of things? Then explain how do I edit the original post to remove the attatchment? That way I won't be mocking anyone anymore.
Oh, and S-uper_T-oast, thanks for the explanation. I had a feeling you were just kidding around, I just didn't get the references🙂.
Oh, and S-uper_T-oast, thanks for the explanation. I had a feeling you were just kidding around, I just didn't get the references🙂.
You have the general idea right ^..^
Early particle generators were based on pesudo-random number gnerators were you would set up equations that would make sure to give the same numbers each frame for each particle, except with slight differences added to give it the required charectoristics(sp). Now, you can use the megabuf to do the same thing except much easier and with much more flexibility. All you have to remember is what you put were in the buffer and use the appropriate counters.
Early particle generators were based on pesudo-random number gnerators were you would set up equations that would make sure to give the same numbers each frame for each particle, except with slight differences added to give it the required charectoristics(sp). Now, you can use the megabuf to do the same thing except much easier and with much more flexibility. All you have to remember is what you put were in the buffer and use the appropriate counters.
did u make any of this yourself or just copy other peoples work? (note the comments?)... well its pretty cool... :-) just cant help thinking that you have copied others work
@ S-uper_T-oast
Do you maybe know a tutorial about the megabuffers? At the moment i only use that function for very simple things. Let's say i don't use it's "full potential" right now, that sounds better 😉
Do you maybe know a tutorial about the megabuffers? At the moment i only use that function for very simple things. Let's say i don't use it's "full potential" right now, that sounds better 😉
Nope, I don't know any megabuffer tutorials.
If it is not in either Pak's, pir's, or Atero's tutorials, there probably isn't one.
If it is not in either Pak's, pir's, or Atero's tutorials, there probably isn't one.
Bad Luck...
O.K. So i have to rack my brain myself. 🙁
O.K. So i have to rack my brain myself. 🙁
supertoast's megabuf/gmegabuf tutorial
for the sake of the tutorial, megabuf() and gmegabuf() are interchangeable in the descriptions, the only difference is what buffer they store too. megabuf() stores to a local buffer that is only accessible by the current component, gmegabuf() stores to a global buffer that is accessible by any component
Megabuf() is used to return a variable from a one million digit buffer.
By using the code
To assign numbers to the buffer, use the code
-Example
advanced stuff
Once you understand the basics of buffers, you can use more advanced commands to store and withdraw from them. Some useful things to learn are the exec2() and loop() commands.
-exec2( string1 ,string2 )
Exec2 basically acts as running to seperate functions at the same time. A way to show this is make a simple example.
This is an example of a point-per-point superscope, it takes each point in the series and assigns it a specific x and/or y value based on the position it has in the series. The variable k increases in value of .2 each pixel along the line, but since we are using the exec2() command, the points x-value is assigned to the amount of k then k increases by .2. The perframe expression k = -.8 acts a reset to out counter varible k so that it doesn't continue growing to infinity.
-loop( count , statement )
The loop command causes the statement to repeat count number of times. What this means is that if you use the code
-Usage with megabuf()
These three expressions can be connected together for limitless applications. An example of one would be
1 - loop 10 times through the statement
2 - the stament will execute the two strings every time its looped through
3 - it will first assign our counter variable k with k + 1
4 - Secondly, it will assign the megabuf spot k to the value of k
What you end up with is the megabuf spots 1-10 having the values of 1-10 sequentially.
notes
-k is an arbitrary variable used as a custom counter
-some of the terms are a little messed up (statment, expression, string, etc...) if anyone can come up with better wordings please tell me
-if you have any more question PM me
for the sake of the tutorial, megabuf() and gmegabuf() are interchangeable in the descriptions, the only difference is what buffer they store too. megabuf() stores to a local buffer that is only accessible by the current component, gmegabuf() stores to a global buffer that is accessible by any component
Megabuf() is used to return a variable from a one million digit buffer.
By using the code
the string will return the number (#) from the buffer.
megabuf( # )
To assign numbers to the buffer, use the code
This will assign the number value to the buffer spot #
assign( megabuf( # ) , value )
-Example
This will make a superscope with one point at (.8,-.3)
::Init::
n = 1; //Set n=1 to draw a single point
assign( megabuf( 3 ) , .8 ); //set the buffer spot 3 to equal .8
assign( megabuf( 145 ) , -.3 ); //set the buffer spot 14 to equal -.3
::Per Pixel::
x = megabuf( 3 ); //set the x-cordinate equal to the value of the buffer spot 3
y = megabuf( 145 ); //set the y-cordinate equal to the value of the buffer spot 145
::drawmode = dots::
advanced stuff
Once you understand the basics of buffers, you can use more advanced commands to store and withdraw from them. Some useful things to learn are the exec2() and loop() commands.
-exec2( string1 ,string2 )
Exec2 basically acts as running to seperate functions at the same time. A way to show this is make a simple example.
This will create a dotted line at y=0 from -.8 to .8
::init::
n = 9; //set the number of points to 9
:😛erframe::
k = -.8; //sets our arbitrary custom counter to -.8 every frame
:😛erpixel::
exec2( assign( x , k ) , assign( k , k + .2 ) ); //executes the two expression, x = k, and k = k + .2
drawmode = 0; //Sets the drawmode to dots\
This is an example of a point-per-point superscope, it takes each point in the series and assigns it a specific x and/or y value based on the position it has in the series. The variable k increases in value of .2 each pixel along the line, but since we are using the exec2() command, the points x-value is assigned to the amount of k then k increases by .2. The perframe expression k = -.8 acts a reset to out counter varible k so that it doesn't continue growing to infinity.
-loop( count , statement )
The loop command causes the statement to repeat count number of times. What this means is that if you use the code
It will go through the statement assign( k , k + 1 ) 10 times and would end up with the variable k being equal to 10.
loop( 10 , assign( k , k + 1 ));
-Usage with megabuf()
These three expressions can be connected together for limitless applications. An example of one would be
What this will do is
loop( 10 , exec2( assign( k , k + 1), assign( megabuf(k) , k )));
1 - loop 10 times through the statement
2 - the stament will execute the two strings every time its looped through
3 - it will first assign our counter variable k with k + 1
4 - Secondly, it will assign the megabuf spot k to the value of k
What you end up with is the megabuf spots 1-10 having the values of 1-10 sequentially.
notes
-k is an arbitrary variable used as a custom counter
-some of the terms are a little messed up (statment, expression, string, etc...) if anyone can come up with better wordings please tell me
-if you have any more question PM me
There, I did something pesudo-useful.
😁
😁
Thank you very much!
Your explanations are terse and easy to understand.
I should care more about loop and exec and stuff, when working on the megabuffer. I disregarded them, cause i was too lazy to learn how they work. 😉 But now i'll make up for them.
Your explanations are terse and easy to understand.
I should care more about loop and exec and stuff, when working on the megabuffer. I disregarded them, cause i was too lazy to learn how they work. 😉 But now i'll make up for them.
supertoast's megabuf/gmegabuf tutorialSure, everyone's writing up good easy to understand tutorials now when i've already learned it the hard way (experiment and fail) 😛
yup, same here, and I think it is also better to make the road yourself cause you never need an explanation afterwards. because megabuf is only logic, I mean take a loop, two assigns and some variables, and you can make any shape with it. it is the fastest way also for a superscope. anyone will understand using the megabuf when my pack is out, but I won't show you any preset till than 😉
Originally posted by Tuggummi
Sure, everyone's writing up good easy to understand tutorials now when i've already learned it the hard way (experiment and fail) 😛
Originally posted by hboy
yup, same here
Clone! Clooooooooneeeeee! 😱
I still wanted to do it the hard way... why did you post this? 😢
😛
😛
ST didn't explain how to make any dificult shapes, so i still have to do it the hard way. His tutorial was more like a general input.
I'm sure loops and megabuf is part of my guide isnt it?
Again, that's the easy way 😉
Originally posted by PAK-9You're right, sorry. I had in mind that i worked on all chapters of your guide. But actually i skipped some parts.
I'm sure loops and megabuf is part of my guide isnt it?
My fault... 😉
I freakign skipeepd some parts, but i learned some parties. fukc i learnmed from a pak-9 tutor, fuck me im so lame 🧟 But it was no good i still hd to earn fro mscratch pretty miach.... lol u duck pak-9 😛
er.. yea thanks
for whoever gets the point.. 😕
You get it if it's up to me 🙂
point: --> . <--
sorry 'bout the offtopic
point: --> . <--
sorry 'bout the offtopic
no, sorry this is the point to catch:
oh, one moment please, here it goes:
wait here:
catch it:
over there:
Got it: => ( . )
oh, one moment please, here it goes:
wait here:
catch it:
over there:
Got it: => ( . )
Sorry,
I figured the thread died, so now, I'm going off topic in a sense, but only because the topic changed. I didn't copy. What I used was a single movement from one of Tuggummi's presets, and jaaka's sphere. Things like color, and manipulation of shapes, etc. I did that(even if I'm still too new to really figure out exactly how I did it). I totally gave credit to what I did use, and untill I can figure out how to have the white with subtly swirly colors in the center of the sphere type shape(without using the sphere), the sphere will stay there.
I mean, I must not get it at all. I'm learning about x, y, and z coordinates and how they work within AVS. I'm also slowly but surely starting to wrap my brain around the math. I am learning how to make shapes, but it's taking some time. Solid shapes are semi-easy, so long as they have straight edges, but trying to fill a circle using superscope is still beyond my grasp(not complaining, just telling the truth is all).
So my question to Matt is, did you even read the initial post? Also, if you did in fact download the presets did you even bother to read the comment? Plain as day I give credit, and it's easy as pie to find the exact ape/sphere/movement I borrowed. Open them and you'll see that yes, while I did use bits from two, count them two other presets, what I made looks like neither of those presets(except for the one preset with interleaving, because I was trying to figure out how Tuggummi did something, and hey, I still haven't figured it out). But even that one doesn't really look like the original(precisely because I haven't figured it out, but when I do figure it out, then I won't be using it in any way similair to how Tuggummi would).
Reading what Tuggumi said, I both agreed and disagreed with him. On the one hand, yes it would be better to lose the 3d sphere(for more than one reason I'm sure, it's probably sucking up a ton of cpu usage, and the fps could definitely be better). I didn't read his, or anyone but your post(MattFury), as saying I full on copied anyone. Face it, there's only so many ways to make a wheel, sphere, or even a simple circle. Heck there's only so many ways to make even a line. So what of it?
I thought I made it clear that I only want to know if I even have an eye for what looks good in a preset. I could spend years learning how to write code, and optimize it. If I don't have an eye for what looks good, then those years would be wasted as I could put them to better use learning to code something less artistic and more utillitarian than AVS presets.
I never said I was the shit. Never claimed to be a fucking genius. Allways said, and still say, I'm a beginner, and still learning. I wouldn't take offense, except for that I really did think of it as a learning experience. I was learning how to do different things. I still am.
I don't mind if the thread strays/strayed off topic, there's some usefull learning material in here.
I just can't help but resent the implication that all I did was copy. No I didn't write the whole damn thing from scratch. But guess what. I never claimed I did. Good Gravy, child. You really have a knack for getting my back up. All I ever did to you was try to be nice, even when everyone else was throwing so many flames, you must surely have been worried about a backdraft. Quick word of advice, learn to read the lines before you try to read between them.
What I got from the posts was two things(not including ^..^'s kind words of encouragement), was A. using the 3D sphere is a waste of resources, and B. information about particles and megabuff. Maybe I should try reading between the lines, but I think that would in and of itsself be accusatory.
I'm sorry I turned into a mega-bitch from hell there, but it gets on my nerves. I mean, I thought of the things I was using as being more like templates(that yes I did change some things in, but I thought that was allowed, really make it more clear). I mean if we're not allowed to do that(even when it's for learning purposes, I mean it's not like I went and submitted my newbie crapola to Winamp, then clearly state 'Don't do a damn thing with my code! No ifs ands or buts about it. Don't touch it, don't experiment with it, don't even think about including it in even an experimental project, you blitherring moron!' I'm sorry but if it's sugar coated with 'Give credit where credit's due' I will believe that's what's necessary. I'm just stupid like that(many other ways as well, I'm sure).
I figured the thread died, so now, I'm going off topic in a sense, but only because the topic changed. I didn't copy. What I used was a single movement from one of Tuggummi's presets, and jaaka's sphere. Things like color, and manipulation of shapes, etc. I did that(even if I'm still too new to really figure out exactly how I did it). I totally gave credit to what I did use, and untill I can figure out how to have the white with subtly swirly colors in the center of the sphere type shape(without using the sphere), the sphere will stay there.
I mean, I must not get it at all. I'm learning about x, y, and z coordinates and how they work within AVS. I'm also slowly but surely starting to wrap my brain around the math. I am learning how to make shapes, but it's taking some time. Solid shapes are semi-easy, so long as they have straight edges, but trying to fill a circle using superscope is still beyond my grasp(not complaining, just telling the truth is all).
So my question to Matt is, did you even read the initial post? Also, if you did in fact download the presets did you even bother to read the comment? Plain as day I give credit, and it's easy as pie to find the exact ape/sphere/movement I borrowed. Open them and you'll see that yes, while I did use bits from two, count them two other presets, what I made looks like neither of those presets(except for the one preset with interleaving, because I was trying to figure out how Tuggummi did something, and hey, I still haven't figured it out). But even that one doesn't really look like the original(precisely because I haven't figured it out, but when I do figure it out, then I won't be using it in any way similair to how Tuggummi would).
Reading what Tuggumi said, I both agreed and disagreed with him. On the one hand, yes it would be better to lose the 3d sphere(for more than one reason I'm sure, it's probably sucking up a ton of cpu usage, and the fps could definitely be better). I didn't read his, or anyone but your post(MattFury), as saying I full on copied anyone. Face it, there's only so many ways to make a wheel, sphere, or even a simple circle. Heck there's only so many ways to make even a line. So what of it?
I thought I made it clear that I only want to know if I even have an eye for what looks good in a preset. I could spend years learning how to write code, and optimize it. If I don't have an eye for what looks good, then those years would be wasted as I could put them to better use learning to code something less artistic and more utillitarian than AVS presets.
I never said I was the shit. Never claimed to be a fucking genius. Allways said, and still say, I'm a beginner, and still learning. I wouldn't take offense, except for that I really did think of it as a learning experience. I was learning how to do different things. I still am.
I don't mind if the thread strays/strayed off topic, there's some usefull learning material in here.
I just can't help but resent the implication that all I did was copy. No I didn't write the whole damn thing from scratch. But guess what. I never claimed I did. Good Gravy, child. You really have a knack for getting my back up. All I ever did to you was try to be nice, even when everyone else was throwing so many flames, you must surely have been worried about a backdraft. Quick word of advice, learn to read the lines before you try to read between them.
What I got from the posts was two things(not including ^..^'s kind words of encouragement), was A. using the 3D sphere is a waste of resources, and B. information about particles and megabuff. Maybe I should try reading between the lines, but I think that would in and of itsself be accusatory.
I'm sorry I turned into a mega-bitch from hell there, but it gets on my nerves. I mean, I thought of the things I was using as being more like templates(that yes I did change some things in, but I thought that was allowed, really make it more clear). I mean if we're not allowed to do that(even when it's for learning purposes, I mean it's not like I went and submitted my newbie crapola to Winamp, then clearly state 'Don't do a damn thing with my code! No ifs ands or buts about it. Don't touch it, don't experiment with it, don't even think about including it in even an experimental project, you blitherring moron!' I'm sorry but if it's sugar coated with 'Give credit where credit's due' I will believe that's what's necessary. I'm just stupid like that(many other ways as well, I'm sure).