MSX1 boot "logo"

Page 10/13
3 | 4 | 5 | 6 | 7 | 8 | 9 | | 11 | 12 | 13

By gdx

Prophet (3035)

gdx's picture

12-05-2018, 02:39

Parn wrote:

I think it looks really good, but what do you mean by closer to the original?

Because I'm wrong in data conversion. I'll fix it soon.

By gdx

Prophet (3035)

gdx's picture

12-05-2018, 11:33

Fixed, and I reduce data. (About 80 bytes less!)

10 COLOR,4,4: SCREEN 2
20 CLEAR900:DEFINT A-Z: VDP(1)=VDP(1)AND191
25 LINE(22,40)-(233,118),1,BF
30 FOR Y=48 TO 109
40 C=1:PSET(22,Y),C
50 READ V$: V=VAL("&H"+V$)
60 IF V<128 THEN LINE-STEP(V,0),C: C=C XOR14: GOTO50 ELSE LINE-STEP(V-128,0),C
70 NEXT Y: VDP(1)=VDP(1)OR64
80 IF STRIG(0)=0 THEN80
90 END
100 DATA 23,0D,0F,0D,18,36,17,93
110 DATA 23,0E,0D,0E,15,3A,15,94
120 DATA 22,0F,0D,0F,12,3D,13,94
130 DATA 22,0F,0D,0F,10,3F,12,94
140 DATA 22,10,0B,10,0F,41,11,93
150 DATA 22,10,0B,10,0E,43,0F,93
160 DATA 21,11,0B,11,0C,44,0E,94
170 DATA 21,11,0B,11,0B,46,0C,94
180 DATA 21,12,9,12,0B,47,0B,93
190 DATA 21,12,9,12,0A,49,9,94
200 DATA 20,13,9,13,9,49,8,94
210 DATA 20,13,9,13,8,4B,6,94
220 DATA 20,14,7,14,8,4C,5,93
230 DATA 20,14,7,14,7,4D,4,94
240 DATA 1F,15,7,15,6,4E,2,94
250 DATA 1F,16,5,16,6,E3
260 DATA 1F,16,5,16,5,14,28,A7
270 DATA 1F,16,5,16,5,12,2B,A6
280 DATA 1E,17,5,17,4,11,2C,A5
290 DATA 1E,18,3,18,4,11,2D,A3
300 DATA 1E,18,3,18,4,11,2E,A1
310 DATA 1E,18,3,18,4,12,2E,A0
320 DATA 1D,19,3,19,3,14,2C,9F
330 DATA 1D,1A,1,1A,4,24,1C,9D
340 DATA 1D,1A,1,1A,4,27,1A,9B
350 DATA 1D,1A,1,1A,4,29,19,99
360 DATA 1C,37,4,2A,17,99
370 DATA 1C,37,4,2B,17,97
380 DATA 1C,37,5,2B,17,95
390 DATA 1C,37,5,2C,17,94
400 DATA 1B,39,5,2C,15,95
410 DATA 1B,39,6,2C,13,97
420 DATA 1B,39,7,2B,13,98
430 DATA 1B,0F,1,19,1,0F,8,2B,11,9A
440 DATA 1A,10,1,19,1,10,8,2A,10,9B
450 DATA 1A,10,1,19,1,10,0A,29,0E,9D
460 DATA 1A,0F,3,17,3,0F,0C,27,0E,9E
470 DATA 1A,0F,3,17,3,0F,0E,26,0C,9F
480 DATA 19,10,3,17,3,10,10,23,0B,A1
490 DATA 19,10,3,17,3,10,1F,14,0A,A3
500 DATA 19,0F,5,15,5,0F,21,13,8,A5
510 DATA 19,0F,5,15,5,0F,22,12,8,A5
520 DATA 18,10,5,15,5,10,21,12,7,A7
530 DATA 18,10,5,15,5,10,21,12,6,14,1,94
540 DATA 18,0F,7,13,7,0F,20,13,5,14,2,94
550 DATA 18,0F,7,13,7,0F,1E,15,5,13,4,94
560 DATA 17,10,7,13,7,41,5,13,6,94
570 DATA 17,10,7,13,7,41,4,14,6,95
580 DATA 17,0F,9,11,9,40,3,14,8,94
590 DATA 17,0F,9,11,9,3F,4,13,0A,94
600 DATA 16,10,9,11,9,3F,3,13,0C,94
610 DATA 16,0F,0A,11,0A,3D,3,14,0C,94
620 DATA 16,0F,0B,0F,0B,3D,2,14,0E,94
630 DATA 16,0F,0B,0F,0B,3C,3,13,10,94
640 DATA 15,10,0B,0F,0B,3B,3,13,12,94
650 DATA 15,0F,0C,0F,0C,39,3,14,12,94
660 DATA 15,0F,0D,0D,0D,38,3,14,14,94
670 DATA 15,0F,0D,0D,0D,37,4,13,16,94
680 DATA 14,10,0D,0D,0D,36,4,13,17,94
690 DATA 14,0F,0E,0D,0E,33,5,13,19,94
700 DATA 14,0F,0F,0B,0F,31,6,14,1A,94
710 DATA 14,0F,0F,0B,0F,2D,9,14,1B,95

By Pippo

Champion (420)

Pippo's picture

13-05-2018, 00:19

Hi again to everybody.
Please, can you kindly give me your opinion about my release 1.20?
It is smaller than the previous and with video effect + other little things.
Many thanks in advance for your opinion.

Link:
https://drive.google.com/open?id=1fxF1qzg3tGZEO9WlnC_sXzIwMn...

By Manuel

Ascended (15750)

Manuel's picture

13-05-2018, 00:51

I'd use an animation effect that looks like an animation effect and not possibly (by accident) like an artifact due to a hardware limitation (which isn't there of course). So it must look intentional, if you ask me, to avoid confusion. After all, this thing is supposed to be impressive as well.

By Pippo

Champion (420)

Pippo's picture

13-05-2018, 11:11

Manuel wrote:

I'd use an animation effect that looks like an animation effect and not possibly (by accident) like an artifact due to a hardware limitation (which isn't there of course). So it must look intentional, if you ask me, to avoid confusion. After all, this thing is supposed to be impressive as well.

I see, Manuel.
I really don't know if I can do that you mean.
I will try.
Eventually, I will let you know....

By [WYZ]

Champion (406)

[WYZ]'s picture

13-05-2018, 14:13

IMHO Screen 1, which have a small color table, should be the best screen mode. The logo could be optimized by removimg the identical chars as Jannone's screen conversor can perform . I've tried and it results 94 diferent tiles with Parn's Logo but the pair form/colour changes in the same tile so it is almost impossible to do it by this way.( someone can help with this?)

So the final logo takes:

  • Tiles: 26*10 bytes
  • Pattern table: 94*8 bytes
  • Colour Table: 8 bytes

    1022 bytes aprox. wich seems to be too much

Just a mockup

By eimaster

Master (221)

eimaster's picture

13-05-2018, 14:40

Hi all
gdx
So:
VDP(1)=VDP(1)AND191
Makes screen 2 invisible while it is active to draw or print operations untill you finish. Then you display/show the finished screen by making it visible again by:
VDP(1)=VDP(1)OR64
That was for screen 2 but does that way applys to other screens like screen 0, 1, 3 and others?!

By Grauw

Ascended (8451)

Grauw's picture

13-05-2018, 15:30

WYZ: It’s more compact to store only the locations on each line of the transitions from black to white and vice versa. Just 6-12 bytes per line. The screen 2 colour table can change colours per line; all my effects are based on just playing around with this. Imo the size of the colour table doesn’t really matter, since it’s just a FILVRM call. Printing text in screen 1 will probably be easier though.

eimaster: Yes, all. See the VDP manual.

By santiontanon

Paladin (833)

santiontanon's picture

13-05-2018, 16:54

Also, if space saving is an issue, recall that the decompression routine of pletter is less than 200 bytes long, so, it might be possible to add it, and save additional space.

By Grauw

Ascended (8451)

Grauw's picture

13-05-2018, 18:00

Pletter reduces my logo data from 552 -> 371 bytes. So not enough reduction to compensate for the decompression routine size.

I also tried with logo data stored as deltas, and surprisingly it reduced it from 552 -> 415 bytes… I had thought it would compress more. Maybe Huffman performs better, if the routine + dictionary can be small enough. Storing 7 bits alone would already save 69 bytes, and I do see quite some repetition.

But I think storing vector data (like NYYRIKKI’s) may be a good contender. With just 50 line segments (=100 bytes) you can already get pretty accurate. The rendering speed needs to improve though, polygon scan line rendering algorithm seems a good choice. The output would be the data as I store it now. Do need code for edge sorting and scan line rendering though, that takes space as well.

(Heh, so close to a 3D logo animation Big smile.)

Page 10/13
3 | 4 | 5 | 6 | 7 | 8 | 9 | | 11 | 12 | 13