cain might aswell have a 3rd record: having the most annoying demos ever!

What is a screensplit?

a screensplit usually refers to splitting the screen in two parts using a screen mode change (for example in space manbow, status is screen 5, rest is screen 4). But you can do other splits as well, like colorsplits, with which you can show more than 16 colors in screen 5/7 (or create a fake cylindrical effect like in Bombaman ). Sprite splits are possible, to show more than 32 sprites on screen. A vertical scroll split, to create cylindracal effects (like in Unknown Reality), horizontal adjust, to create a waving effect. And there are probably more of them

This is very interesting! How stable is it? Is it working on all MSX2 / MSX2+ / TurboR machines?

no, companies compiled different release-builds for each msx-type ever made..

*sigh*

prolly most funet screensplit-games don't work on your msx if you don't have the exact msx-type

dhau: http://map.tni.nl/articles/split_guide.php

And yes, it works on all MSX types but MSX 1, it is upwards compatible so no differences between MSX models. They all use the same VDP after all (the v9938 or the v9958). Screensplitting is a common technique on MSX, and also on the v9990 (Gfx9000) and Gameboy (Advance), SNES, MegaDrive, etc.. And even on MSX 1 you can use screensplits, with a trick described in the article.

~Grauw

Thanks, it is very interesting!

A while ago I coded a screensplit for MSX Turbo R in R800 mode, in NBASIC! That's the most unstable screensplit I've ever seen, though...
It made about 8 lines blittering Hehe... Well, it was quite fun to see it was possible in (N)BASIC, but splitting in BASIC in general isn't a smart idea, I guess...

Assembler must be a bit better, since you know exactly how many tacts each block of code takes, so you can fill in usefull instructions without violating timing, or if not enough space, just NOP until it's good to go again

I think that the first publicly seen screen split was made by Elvis Presley. He used to shoot the TV with his shotgun. That is a true screen-split.

Barbiturics are more precise than assembler, don't you think so?

I think we are talking about different split screens. Besides, you can't really call a TV screen that was shot with a shotgun a spleet screen. I think a more appropriate term is "trashed screen". I beleive it is also possible to have this effect in MSX game or demo in a static picture with pseudo-transparent colors faking a hole on black monitor

I didn't heard much about Barbiturics, can you please provide more information on it?

Well, perhaps that word doesn't exist in english You know, spanglish happens

"Barbitúricos" is the generic name for soft and legal drugs that are sold at the chemistry, like all sedants and other not-very-healthy stuff.

Oh, cool! Now I get it. But I only drink alcohol, and very rarely (once a quarter), and one bottle of beer puts me down for good

Quote:

Assembler must be a bit better, since you know exactly how many tacts each block of code takes, so you can fill in usefull instructions without violating timing, or if not enough space, just NOP until it's good to go again

That is the worst way you can code a screensplit. It will instantly break on different CPU speeds such as 7MHz or the R800. It is much better to use the timing flags and interrupt the VDP offers.

~Grauw

Now that you mentioned it I think it's ture... So VDP should be the core of sync, so that game will run exactly the same on EMSX2 and CIEL3++ at 50MHz as on stock MSX with 3.57MHz CPU