You can't do stuff like x=d OnBeat - That's for Pixel section. For Frame, Init, and onBeat, the values are equal to every pixel/section of the screen.
The alternative is if(b,n1,n2) for such thing.
Texer works with any pixel you have on the screen.
UnripeLemon : You need a good dose of brainpower to bring you up to a level where you can actually understand how to code...
What texer does is scan the image for non-black pixels and draw the texture bitmap around that point, optionally masked by the pixel's colour.
The clearest example is my Milkyway II preset (which you'll probably have if you have texer). If you remove the 2 texers, you just get a bunch of dots.
You could actually compare it to the convolution filter, except a bitmap is used for the convolution kernel, and the radius is unlimited 🙂.
argh. the reason it's showing a white bar at the top of the screen is because you're trying to texer too much. use clear every frame or an effect list to fix that.
as for trails... ^^^
am i the only one that finds that painfully obvious?
way to pay attention, unripelemon.
There's been talk about the forums being down going on EVERYWHERE on winamp, in GD, in the AVS forums, on the chatrooms - fucking everywhere. Most importantly, however: "THE FORUMS WERE DOWN, WE SUCK." <- Front page of winamp.com
The reason the white bar appears at the top if you use Texer is because you are trying to re-texer a texered image.
Try moving everything in your preset in an effect list, and move the texer outside.
This thread is on the very edge of flaming and needs to die. Now. I'm only posting because it's at the top of the page so people, please stop posting now and let it die. And please no unoriginal, attempts at pathetic humour with a post saying "ok".