Reply to Re: ffcreate2 is good
If you don't have an account, just leave the password field blank.
: : My experience with ffcreate2 is that it helps scene transitions, fades etc when going from one screen to another screen that has new bmps. I get flash frames of the old/new screen between fades if I don't use ffcreate. Just my 2 cents 
: Yeah, I've had that too, but FFCreate2 doesn't always get rid of them, just most of the time.
Ok, WC didn't understand.
Zipped FFCreate2 dir.ff: 166 KB
Zipped Raw BMP Files: 179 KB
I suspect this is because the ZIP format compresses files individually, and more compression can be squeezed out of BMPs that are all in the same file rather than split.
I was unable to test the original FFCreate, because it was trying to include the dir.ff file it was creating within itself.
Also, the reason why the screen doesn't flash when you use FFCreate2 is if you preload (or use) one seq in the dir.ff file, it will load all of the sequences in the dir.ff file into memory. And the flashing is caused by loading sequences into memory when the screen is faded down, as it will (briefly) display the image's pallete on the screen, I think.
: Yeah, I've had that too, but FFCreate2 doesn't always get rid of them, just most of the time.
Ok, WC didn't understand.
Zipped FFCreate2 dir.ff: 166 KB
Zipped Raw BMP Files: 179 KB
I suspect this is because the ZIP format compresses files individually, and more compression can be squeezed out of BMPs that are all in the same file rather than split.
I was unable to test the original FFCreate, because it was trying to include the dir.ff file it was creating within itself.
Also, the reason why the screen doesn't flash when you use FFCreate2 is if you preload (or use) one seq in the dir.ff file, it will load all of the sequences in the dir.ff file into memory. And the flashing is caused by loading sequences into memory when the screen is faded down, as it will (briefly) display the image's pallete on the screen, I think.
