|
Post by tokra on Jan 22, 2015 8:50:23 GMT
The progressive download looks that way because for interlace-mode you have TWO colormaps and TWO bitmaps to load. So 4 files per picture. I load each into memory and use a copy-memory-to-VDC-memory-routine for each file (which I "borrowed" from you - with your permission back in 2012 ;-))
Only the new 800x600 mode is monochrome. The YouTube shows all the modes of this Demo (640x480 interlace in 8x2 color resolution, 640x576 interlace in 8x3 colors, 480x252 non-interlace in 8x1 colors, 600x400 non-interlace in 8x2 colors, 720x700 monochrome and the new 800x600 monochrome). I suggest watching the YouTube in FullHD, you will be able to read the on-screen messages that way :-)
The 800x600 mode uses 644 total vertical lines (or 651 depending on how the VDC sees it, not really sure). That is just above PAL (625 lines) and may still work on some PAL-TVs.
|
|
|
Post by tokra on Jan 21, 2015 11:12:14 GMT
I have a 1541U V2 and it works perfectly fine with my C128. I saw that with newer firmware versions you may need to adjust one or two settings in the setup, but that's no big deal. I don't think the V2 has RR-Net though
|
|
|
Post by tokra on Jan 15, 2015 17:09:49 GMT
|
|
|
Post by tokra on Jan 13, 2015 18:02:03 GMT
I have recently updated my little VDC Mode Mania demo with another graphics-mode: 800x600 Interlace Monochromeincluding 4 demonstration-pictures. This mode will work best on a Commodore-1084 monitor, as you can squeeze the image horizontally as well as vertically. The mode should work on nearly all 80-column-display devices though, even if not the full picture is visible. Using a Commodore 1901 e.g. the left and right border will be cut off as this monitor can only display about 750-760 pixels width. Have fun trying the new version: DOWNLOAD
|
|
|
Post by tokra on Nov 24, 2014 15:27:20 GMT
I would for sure welcome a patch to the recent firmware. "Unseen" is active on forum64.de and has mentioned the problems with burst-mode there in several threads. If I understand correctly 1571 and 1581 behave differently to some of the same burst-commands, making things difficult. Also he has recently mentioned that the binary-"nightlies" he posts at www.sd2iec.de are tested as much as any previous version was tested. So, he just changed the naming, but now most people are still using the nearly 3 year-old 0.10.3 version as the last "official", while the nightlies have 3 years of bugfixes and improvements in them. Anyway, contact info can be found at the top of the SD2IEC-README file at www.sd2iec.de/gitweb/?p=sd2iec.git;a=blob;f=README;hb=HEADI would already be a happy camper if the ML-code hack was available for a more recent firmware version, but can live with your hack as is just fine :-)
|
|
|
Post by tokra on Jun 30, 2014 12:19:08 GMT
Is that even with the ram refresh set to zero? Yep, RAM-refresh just will get you one or two more characters. I remember specifically testing this when I created the VDC-FLI mode. I think without RAM-refresh set to zero you will only get 58 or 59 characters width.
|
|
|
Post by tokra on Jun 29, 2014 21:26:11 GMT
Hey Mirkosoft, if you're reading this, you said your C128 reports revision 2. Is this with a 8568? I.e., the "new" VDC of the DCR which has the extra register of sync polarity? I was curious because I have never read what that difference between revision 1 and revisions 2 is. Well we know the "new" VDC has the extra register, so maybe that is why it is revision 2? Of course, anybody who knows about this can comment, but I thought Miro might know directly. Anyway, thanks for all respones on this sub-topic! The revision number is reported by the 3 lower bits in $d600. Version 0 would be the very early 8563 with the register 25 scroll-register set up differently. Version 1 is the 8563 with register 25 set-up as we know it and the most common version in flat C128s and plastic C128Ds. Version 2 is the 8568 in the C128DCR which also came with 64K VDC-RAM. Sometimes you will see these referred to as revision 7, 8 and 9 respectively. Revision 7 was the first one going to production apparantly and as such was called version 0 and is reported as such by $d600.
|
|
|
Post by tokra on Jun 29, 2014 21:07:09 GMT
I quickly copied my notes from the original CSDB-entry of VDC-FLI: "This mode came about trying to figure out how the (brilliant) "Risen from Oblivion"-demo does its own FLI-mode. By hardware the VDC only supports a maximum of 8x2 color-blocks by setting register 9 of the VDC to two rasterlines. If you try to set it to 1 rasterline to get an 8x1 mode the VDC won't activate the display and you only get a blank screen. The trick to force the VDC to display is to watch bit 5 of$d600 (VBLANK) and switch register 9 to one rasterline right after the VLANK-period has finished and back to any other value once VBLANK starts again. This fools the VDC into displaying the 8x1 mode. However since the VDC now has to fetch the character- as well as the attribut-byte for every rasterline you can only address a screen of 60 chars wide (=480 pixels), otherwise the screen gets garbled. The register 9-switcher is realized as a quick and dirty 47 byte assembler routine. If you want to do it proper you will have to set up a VDC-raster-interrupt and for that you first need to measure your specific VDC-chip's speed. That is what "Risen from Oblivion" does when you start it." Too bad the commodore128.org-forum seems gone for good together will all the discussions :-( Anybody heard from BDD?
|
|
|
Post by tokra on Jun 24, 2014 0:23:34 GMT
|
|
|
Post by tokra on Jun 10, 2014 20:11:21 GMT
Just a suggestion ;-)
|
|