#Pixel won't work in R3
6 messages in this thread
Gus, I've downloaded your PIXEL.IXP as I'm in need of exactly this
effect. But I can't get it to work with my 3DS3. Judging by the accompanying
documentation file it should be quite simple to use. Am I missing something or
am I too dumb to invoke an IXP in VP? Or is it an R2 IPAS and never meant to
run under R3?
Thanks,
Volker
It should work just fine in R3. The only difference is that it doesn't handle
48 bit images (only 24). That shouldn't be a problem as the (d)effect groups
pixels in blocks any way. I think I've written a new PIXEL.IXP (I can't even
remember what I have written). I remember dealing with increasing pixelation
based on the keyframe and that was after I uploaded that routine (that's easy
to know as I uploaded pixel.ixp 6 hours after I received the IPAS tool kit, so
anything I have done was _after_ that!).
Let me check…
Gus,
<< I think I've written a new PIXEL.IXP (I can't even remember what I have
written >>
If you have the time I would really like to see many more of your ipas routines
that you can upload…
Mark Yankee
Gus, hmmm….., maybe I should elaborate a bit on the missing
effect…. I have two entries in my VP Queue, the first being a bitmap image,
the second being process PIXEL_I with setup 1 to 20 (ah, having you on the line
is a good chance to ask: what's the meaning of Flat color: yes/no?). After
starting VP it seems that Pixel wants to do something (at least VP render says
"Calling External Procedure" for a moment, after "Loading Image File") and the
result is not a stable image (animation) but jittering slightly. (Funny side
effect BTW: after the rendering all of my mem is used up – 59 megs seem to be a
tiny little bit of an overkill for a 320×200 image… once during my pixel
tests 3DS actually started swapping…!!! (Say!))
Could some entry in the 3DS.SET file have an undesired or hidden effect
on your pixel.ixp (or even worse: on any IPAS module)?
Ah, and sorry for bothering you with this stuff long forgotten….
Thanks,
Volker
There is something definitely broken there. It might be that the PIXEL_I you've
got was generated by Watcom which had a memory problem like that in the early
days. I will take a look and upload a newer version using Metaware.
>> I will take a look and upload a newer version using Metaware. <<
hey, thanks for all your efforts in helping me. I really, really appreciate
this. Once again ASOFT (in this case that means you, Gus) proves its
invaluability to a poor, lost soul in the cold infinite world of computer
animations…
Regards,
Volker