| |
Nightlord
Account closed
Registered: Jan 2003
Posts: 131 |
UFLI?
Hi everyone,
I tried to google around in order to learn how ufli works but could not find anything. I know how fli, afli, shfli, shifli and finally xfli works.
can someone please explain how ufli works and what are its limitations. i tried to look at the displayer code of that veronica picture. i see sprites involved. but i do not understand the code... |
|
... 131 posts hidden. Click here to view all posts....
|
| |
Cruzer
Registered: Dec 2001
Posts: 1051 |
iUFLI-MAX i definitely possible, as long as the gfx that needs to be interlaced is small enough to be switched by software each frame... or alternatively just eor $d016 by 1 each frame :) |
| |
HCL
Registered: Feb 2003
Posts: 731 |
Yes Werner, i was wrong! It is possible at least if you only consider the amount of memory needed. However i fell into the FLI-sudoku, trying to fiddle with Ninjas code to make it use only two video-banks instead of all 4. 5-10 sheets of paper wasted and the only result was my girlfriend going totally nuts at me for spending the whole weekend doing *nothing* (as it appears to her).
So, i'm starting to doubt that there is a possibility to do that interlaced UFLI thing, but a *normal* one sould be no problemo.. Hmm, Cruzer seems to think it's possible, but at the same time he's talking about d016 (!). Guess he's totally out walking ;).
|
| |
Cruzer
Registered: Dec 2001
Posts: 1051 |
@HCL: Sorry, I forgot that you also had to eor $d000, $d002 ... $d00a with $01 to make it all flicker correctly. ;) |
| |
JackAsser
Registered: Jun 2002
Posts: 2038 |
And adding to the soduko...
First, each 42-line segments need unique screens with their own set of sprite pointers, otherwise the same sprite data will simply wrap (the sprites wraps 4 times).
Secondly, every 4th line has a 5 char FLI bug, not 3char (not entierly sure why?!?). Probably not possible to circumvent.
Considering these two facts you can forget Ninja's code and you will have to find your own set of 1337 instructions.
Also in Ninja's case he can re-adjust the initial bit values each time he multiplex the sprites, UFLI-max mode can't, you will have to stick with the patterns all 168 lines or so.
|
| |
Clarence
Registered: Mar 2004
Posts: 124 |
"Secondly, every 4th line has a 5 char FLI bug, not 3char (not entierly sure why?!?)."
Yes, but only under Vice.
|
| |
HCL
Registered: Feb 2003
Posts: 731 |
@JackAsser: It's not that complicated, you can reuse the sprite-areas since only each 4:th line is used during the FLI-timing. It's not straight to see this since the sprite-crunching makes the sprites behave strangely. As i said, in Soul i made 126 lines without any bank-switching, but for the last 42 i guess you'll have to do a switch :(. |
| |
JackAsser
Registered: Jun 2002
Posts: 2038 |
Gnah, me teh stupid.... HCL, if you read what was written in this message before, kindly ignore it. :D |
| |
WVL
Registered: Mar 2002
Posts: 924 |
you teh stupid! ;) |
| |
Cruzer
Registered: Dec 2001
Posts: 1051 |
Ok, I think I have the idea for the ultimate PC gfx editor for weird C64 FLI/sprite-modes, which would work for all conceivable modes people might come up with...
It should allow FLI each line, 3 chars bug (or maybe 0, so it could also be used for 40 chars wide stretched FLI), 26 chars high (208 pixels), and 8 sprites, that's also 208 pixels high each.
For each rasterline it should be possible to adjust FLI multicolor on/off, d016 scroll bits, bg-color (which only has effect in multicolor mode of course) and for each sprite these parameters should also be flexible for each line: x-position, x-expansion on/off, multicolor on/off, fg/bg priority, and sprite color.
This would of course allow the user to create some gfx that was impossible to display on the C64, but it should be the user's responsibility to keep within the boundaries of whatever displayer he/she wants to use. It should also be up to the user to make a converter that could place the gfx correctly in the memory. The editor should just export it as a standard FLI screen, 80 std. sprites, and some tables with the different data that can be adjusted for each line.
To help the user not to draw anything "illegal" it might be useful to also be able to set FLI on/off and FLI bug size for each line. Support for interlace could also be added. |
| |
JackAsser
Registered: Jun 2002
Posts: 2038 |
Tell me when you're done... |
| Previous - 1 | ... | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | ... | 15 - Next |
