UnConeD

14th November 2003 20:25 UTC

Colormap and Texer
Colormap and Texer will be included in AVS2.7 as a separate .ape file (not integrated like channelshift and the others).

These are the final versions so you can use the new features. You don't need to spread these around anymore.

Texer 2 should be included into AVS as well (as .ape file), but I need to finish the help before I can send off the final version. Waiting for the last APE API update.

http://acko.net/dump/apes.zip

Changes to cmap:
- Fixed bug where cmap wouldn't cycle if you closed the avs editor while editing a cmap.
- Removed links to acko.net (no n00bies on acko plz :weird: )
- Added cycle speed for cmap
- Added noskip option: if turned on, a transition will always be completed until the next is started, even if more beats occur during the transition.

Texer:
- No functional changes

sidd

14th November 2003 23:24 UTC

noskip feature will be very good.
Thanks for this.

Deamon

15th November 2003 09:17 UTC

great to hear it'll all be in wa5, and that we don't need to spread them around with installers.

Great work, UnconeD :up:

sidd

15th November 2003 15:35 UTC

about the noskip feature. If we wanted to synch effects so that, for example, a dm morphs at the same time, we would need to build in our own noskip code into the dm.

So, how does the morphing between maps work? is the speed static, or is it per frame? And if so, how could we come to an equivilant in ssc/dm code.

dirkdeftly

15th November 2003 18:09 UTC

and why don't you ever add a function that will still switch even when there's still morphing going on, but will do a smooth interpolation into the next map instead of cutting off the previous map altogether?

[Ishan]

16th November 2003 06:45 UTC

yeah well i would like to see a smooth transition option there.(is it too tough to code?)

horse-fly

16th November 2003 08:31 UTC

hm... here is a bug in texer, xor sometimes doesn't give the xor effect... i attach file. i get reds and blues, but never any greens

sidd

16th November 2003 10:52 UTC

I found this also. Dont worry though ucd, after a bit of experimenting, i found its not the XOR code that is at fault, its the resizing.

The bilinear filtering over the resized texer image is enough to change each channel by a the smallest amount, and we all know how touchy XOR is.

What i suspect was happening is that the green parts ar turned down maybe just one point (of 255), and the other parts get their green channel marked up just a point or two. Now the binaries is all messy. so after it is xored it is completely weirded up.

//edit.. looks like i was somewhat wrong. Example, get a single white texer bit on a black background. Put xoring on. Put resizing on.

Purple???!?? :eek:

i guess my theory doesnt really account for this. Anyone know wtf is happening here?

//edit2 conclusion: when resizing in enabled, green color channel is ignored for XOR blend mode only.. :igor:

sidd

16th November 2003 10:57 UTC

here: a nice pretty display of xoring over 3 texers

now, put on the resizing and cry.

needs tehtuggtexers

QuadHeliX

16th November 2003 17:17 UTC

Thanks Unconed!! Hey guys is there a tutorial on this. I want to make something really cool! mees not a rocket scientist.

horse-fly

16th November 2003 20:30 UTC

Originally posted by siddhartha_one
here: a nice pretty display of xoring over 3 texers

now, put on the resizing and cry.

sidd

16th November 2003 21:03 UTC

oh, btw everyone else. This is a texer2 bug, nothing to do with this thread.
:eek:

fragmer

18th November 2003 11:05 UTC

O__o The size of these files blows me away - 40kb colormap (I remember it was 68) and 28 (!) kb texer... a LOT of code optimizing I guess :p

Yathosho will like new versions - PimpBot generated installers will be even smaller :D

Thankyou thankyou!

UnConeD

18th November 2003 19:34 UTC

You didn't really pay attention now did you.

Oh and the size reducing is because of me flicking around with compiler settings. Optimizations won't affect code size much.