If I don't get me wrong, Tilburg fair is now finished and openMSX 0.4.0 is still not released ...

I've checked on both openMSX sites : only version 0.3.4 is available and the features list is still not updated (some features are no more exclusive ... see blueMSX 1.3.0 !)

What happens ???

To precise my previous posts :

blueMSX has also support for :

- National mapper type used for internal software

- interlacing, real or deinterlaced

- MSX Bunsetsu Henkan Jisyo ROM (National FS-SR021/FS-4000/FS-4500/4700F)

- 12×12 dot kanji (National FS-4600)

Besides, blueMSX has a timing model that is very similar to the EmuTime model , doesn't need a pixel accurate rendering to get good working the scope part of Unknown Reality and doesn't have performance problems with the Moonsound implementation (in brand new version 1.4.0)

So, it's really time to update the openMSX page !

Quote:

To precise my previous posts : blueMSX has also support for : - National mapper type used for internal software - interlacing, real or deinterlaced - MSX Bunsetsu Henkan Jisyo ROM (National FS-SR021/FS-4000/FS-4500/4700F) - 12×12 dot kanji (National FS-4600) Besides, blueMSX has a timing model that is very similar to the EmuTime model , doesn't need a pixel accurate rendering to get good working the scope part of Unknown Reality and doesn't have performance problems with the Moonsound implementation (in brand new version 1.4.0) So, it's really time to update the openMSX page !

Sorry mars, but bluemsx 1.4.0 isn''t working exactly that good. if I insert a .dsk file it says: can't start msx-emulator.

Is your download complete ? You must have an autoinstallable zipped file of 3.463 Kb.

Will download it again...it was 3.547 (?)

I will check that ... maybe some changes of last minute !

downloaded it again and still doesn't work! No hard feelings mars,but I think you should have waited with your comment on openmsx until blue-msx is 100%. Although I think blue-msx was allready better and user-friendlier than openmsx.

No hard words, please and don't mix all the problems together !

I've just checked the version 1.4.0. The correct size of the file is 3.459 K

If you install this version in a different directory than version 1.3.0, there's no problem at all ! Some differences in the .ini files could explain your problem ...

See all the advices of Daniel Vik on the news page !

Thanks mars, have changed some things and now it's working and I take my words back!!! ;-)

Good MSX fun with blueMSX ... try the Alto demo for example !

FYI, many of the openMSX creators were still having dinner when you posted that message.
You sound like some kind of maniac!!

We were aiming for a release before Tilburg, but there were too many things to do so we had to postpone the release. You can expect 0.4.0 within a week. As always I'll submit a news post, so you can read about it here on MRC as soon as it's released.

Quote:

Besides, blueMSX has a timing model that is very similar to the EmuTime model , doesn't need a pixel accurate rendering to get good working the scope part of Unknown Reality and doesn't have performance problems with the Moonsound implementation (in brand new version 1.4.0)

Hmm, since the scope part of UR uses a vertical screen split, it means some VDP settings change during the drawing of one line. If you only render at line accuracy, it means this change will not be made, since the settings are constant for the whole line. This will break the scope. So, you really need pixel accurate rendering for this (or another way to catch changes of VDP settings while drawing one line).

AFAIK the MoonSound emulation in particular doesn't have performance problems.

blueMSX does the rendering on a pixel basis but updates info from some VDP registers (in particular the vertical scroll register for UR) on a line basis. I have an experimental version that works on the horizontal screen split in UR but I had some timing problems so it will take a little while before it will show up in a release.

It is not that hard to do pixel accurate VDP rendering and it does not require that much extra CPU time. The hard part is to get the entire VDP timing in place and openMSX has done a great job whith this. blueMSX will have it soon too. Its just a matter of time.

At the moment I'm prioritizing other things. E.g. fixing SRAM support in Koei roms (not supported by openMSX) because I believe that this is more important for many users. Of course it is nice to get the scoope part in UR to work and it will be done soon too in blueMSX.

I've mainly been using the windows version of openMSX and there is a big problem with performance and audio quality in openMSX. It probably works much better under Linux.

Btw, I tested a beta of 0.4.0 and there are many nice improvments. And catapult looks really great. Congratulations !

Ha. I just got my harddisk with IDE210 and openMSX online.. And for me... THIS RULES! Bigtime! I have tried several ports.. But sorry for blueMSX.. OpenMSX is here to stay for me now.