|
|
Atari coding BBS
| Re: Videl resolution question |
|---|
|
Posted by: ggn
|
Aug,21.2014-14:47
|
Well, from my experience, screenspain isn't REALLY hard to get to grips with, it just need a bit of experimentation. I'll try to jot down here my experiences (and of course people are free to correct me or add more infos):
A screenie btw is on http://www.pouet.net/content/screenshots/51188.png
- Doublescan enables y doubling of pixels. It halves the vertical resolution, but gives you fatter pixels so you can cover more screen estate with less memory.
- Interlace does just that, and gives you twice the amount of vertical pixels.
- Videomodus is self explanatory, your target monitor.
- Farbtiefe is number of colours (thank you, cpt Obvious!)
- Pixeltakt is how fat are the pixels horizontally, this halves or quarters horizontal resolution.
- Videotakt is the videl clock. Now I've not played with this too much but I suspect the higher setting (32mhz?) should steal more bus cycles but give bigger resolutions. I think it's tied to 'pixeltakt'.
- On 'display' you enter your desired resolution.
I usually don't edit the rest of the editable values.
Then when you press 'testen' the program changes to the resolution you entered. Neither the program nor videl know if your resolution is supported by the monitor, so you might get picture or you might get a smudge (or if you're really really lucky blow up the monitor).
If you get a picture, then you get 4 parts of a crosshair that shows you the edges of your screen buffer. You can move those around with 2-4-6-8 on the keypad. I think you can stretch or shrink horizontally or vertically, just play around with the keypad keys. I think * kind of centers the display? (sorry, it's been a while so it's a bit hazy!).
If you like the result then press enter on keypad and all your changes will be reflected to the main screen.
I'm not sure how DHS produced video.dat that contains their screen modes, perhaps they concatenated .scp files? Personally I export to .scp (for reference) and then save to .s and include it to my source code. I got a tip from earx to wait for a vertical blank before setting $8266.w, so the code from screenspain is modified to something like:
* ###########################################################################
* # #
* # 'Screens Pain' coded 1993 by Chris of AURA & Scandion of the Mugwumps #
* # #
* # --- It's an INDEPENDENT-Product --- #
* # #
* ###########################################################################
* Monitor: VGA
* 320*240, 256 Farben, 60.0 Hz, 31470 Hz
move.l #$C6008D,$FFFF8282.w
move.l #$15029A,$FFFF8286.w
move.l #$7B0097,$FFFF828A.w
move.l #$041903FF,$FFFF82A2.w
move.l #$3F003D,$FFFF82A6.w
move.l #$03FD0415,$FFFF82AA.w
move.w #$0200,$FFFF820A.w
move.w #$0186,$FFFF82C0.w
move.w $0468.w,D0 * / wait for vbl
.wait468_v: * | to avoid
cmp.w $0468.w,D0 * | falcon monomode
beq.s .wait468_v * \ syncerrors.
clr.w $FFFF8266.w
move.w #$10,$FFFF8266.w
move.w #$05,$FFFF82C2.w
move.w #$A0,$FFFF8210.w
Anyway, that's my experiences, next please!
|
[All messages in this thread] [Start new thread]
What's the anti-troll code?
That's your personal code to be able to add comments and messages on the dhs.nu site.
Don't have a code or forgot it? Fix it here.
|
