Disappointed about msxdev

i'm referring to the present, about almost no one developing msx2 games, that push msx2 at its limits on the same order of magnitute of msx1. (please do not consider spmanbow2, it's alone....)

Well, you have 3 options:
- inspire people to make an MSX2 game just for random sake
- inspire people to join this.
- MSXdev'08 with MSXdev'07 rules B-) (the rules being out of reach for us humble nobles tho ^^)

Our (infinite) 2nd Megachallenge entry will be an MSX2+ game, dunno if that'd suit your appetite? :P

I cannot ispire nothing, only i can express only my point of view: even if it looks strange, the major limit of msx2 is its compatibility with msx1.... :P

MSX2+ it's too easy. At the time of msx2 the standard, the standard reached it's full maturity.

(smooth scroll in all directions, no need to use hw sprites for games, great sound caps, even on some models a more fast z80)

PingPong, which rule stops you to create a runeable MSX1 game, but if it detects a MSX2 hardware, it loads more and more files with more graphics, sounds, enables effects, enables more color, screen5 instead sc2, etc etc etc?

screen 5 is NOT screen 2. It's very different in more and more aspects. Coding a game using screen 2 or screen5 depending on the system, is the same to code two different copies of the same game, often. Also sprite handling is different. Twice the effort to do.

The problem is not mine. (no time to code anything, especially now.) The problem is that more people are spending efforts to squeze the max from msx1. they have no more to spend for the msx2.

As you can see, there are no games that works in the way you propose, the majority of those simply switch to screen 4 to gain more sprites / scanline, or do neither this, taking advantage only of the msx2 palette....

For example, a game like GnG is simply undoable on msx1 with decent quality, so why wasting efforts to try to code it? It's not far better to choose the minimum msx configuration that can do this decently? (MSX2)
Of course, IMHO

I'm not blaming msxdev. Only i think that will be correct that the same level of interest should be applied to msx2,2+/TR.

Considering msxdev & actual scenario looks like msx == msx1. This is not true. msx = {msx1, msx2,msx2+,tr}

Must say I agree with that. It's good that we have msxdev, but it also has some problems:

* all active developers participate in msxdev
* msxdev's specs are limited to msx1
* those active developers that participate in msxdev won't do anything else the entire year, because of limited time

So msxdev does boost MSX activity. The problem is that all it does boost is MSX1, which is IMHO a step backwards. It's a kind of deadlock, which is a pity. The last MSX1+ game was Manbow2, and I think the game before that was Bombaman (which is already old).

There's no blame, but msxdev has become some kind of fixture, and therefore it's so influential it's hard to stop with all this MSX1 stuff.

Shall I start an MSX1 screen0 Basic ASCII art game compo?