Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!uwvax!daffy!cat30.cs.wisc.edu!pochron From: pochron@cat30.cs.wisc.edu (David Pochron) Newsgroups: comp.sys.amiga.programmer Subject: Re: Sprite Animation Glitches Message-ID: <1991May2.155342.1317@daffy.cs.wisc.edu> Date: 2 May 91 15:53:42 GMT References: Sender: news@daffy.cs.wisc.edu (The News) Organization: U of Wisconsin CS Dept Lines: 24 In article ersys!kumbach@nro.cs.athabascau.ca (Kevin Umbach) writes: >Basically all I do to change a sprites image is do a memcpy() >from an array into the sprite's image data area and I believe No no no no! Why are you using memcpy() to change the sprite images? You can just set up all the sprite image structures in the code, then all you have to do is a ChangeSprite whenever you want to change images. ChangeSprite just changes the pointer to the sprite data. It Is MUCH faster to do that than to recopy the sprites entirely into a fixed sprite space. Just make sure all the sprite image data is in CHIP mem. Most good C compilers let you specify where structure/array data gets stored at load time. >Kevin Umbach ersys!kumbach@nro.cs.athabascau.ca >Edmonton Remote Systems: Serving Northern Alberta since 1982 -- David M. Pochron | Transparent DWV pipe: For the man who wants to | see it all... pochron@garfield.cs.wisc.edu | (If you don't know what DWV is, get a life! :-)