Please help testing upcoming openMSX release! | MSX Resource Center (Page 10/65)

Ascended (19466)

28-10-2018, 20:36

Actually, wasn't this a known issue? https://github.com/openMSX/openMSX/issues/865 seems to be exactly this: the CIEL uses the /WAIT pin of the VDP, but that isn't emulated. The only workaround for now is to disable VDP access timing restrictions.

By sd_snatcher

Prophet (3659)

28-10-2018, 23:52

Wow! That was more than 5 years ago. I totally forgot that it was already reported.

Well, since the /WAIT isn't being emulated, should't openMSX disable the access timing restrictions for this machine by default? Only until the /WAIT is implemented.

Either that, or rename the machine to WIP_CIEL_Expert-Turbo, since we can't consider the machine is finished the way it its now.

Think of the average user: they'll just boot a "turbo" machine, and it will show corrupted VRAM data. They'll think that either the MSX2+ can't support turbos, or that the real machine also doesn't work properly.

By Manuel

Ascended (19466)

21-11-2018, 22:27

eimaster wrote:

openMSX for Android on screen button 1, 2, and arrows are not working in Games! I just can play with Android Haker keyboard which is not practical because the keyboard eats up half of the game screenplay beside it is a bit slow. I don't know what happened! I used to play normally before (using the previous build, but since I installed the new build I cannot play or make things move with on-screen arrows and buttons 1 and 2!
Can anybody help identify the problem so it can be fixed?!

Can you please test the latest build? It has been renewed and is now using:
- the latest Android NDK (r18b) to build, with the clang compiler targeting the armeabi-v7a. Requires Android 4.1 or higher.
- the latest Android SDL port (commandergenius)

Of course, everyone else is also free to try this build. We can really use some testing with this one!

By sd_snatcher

Prophet (3659)

23-11-2018, 19:47

Here goes another bug report to help you with this release:

When run with the R800 processor (or turbo Z80), the presentation of the Laydock-2 game glitches. The image flashes and the music is played out of pace.

The problem seems to be related to this ancient e-mail by mth. Nowadays, openMSX kills a pending line interrupt as soon as the IE1 flag is set to zero. But the real VDP seems to do this only at the end of the line.

The result is that the presentation won't glitch on turbo machines on openMSX.

WebMSX implements this characteristic as described by mth, and the glitches show up correctly on that emulator when the turbo is enabled.

Thanks Peccin for his help to understand the problem.

By Manuel

Ascended (19466)

23-11-2018, 23:54

What do you mean with "Nowadays"? Has this been changed for the worse? So, is this a regression?

By sd_snatcher

Prophet (3659)

24-11-2018, 14:23

No, there's no regression that I'm aware of. Maybe it was just a poor way to express it from my part. I probably should have used "currently" instead of "nowadays".

I just meant that this is the openMSX current behaviour. This way if someone bumps on this thread some years from now, they'll know that this was the behaviour up to that point.

By Manuel

Ascended (19466)

24-11-2018, 17:14

For new issues, please make a ticket, especially if you have already an account

By Manuel

Ascended (19466)

01-12-2018, 15:50

Any other pressing issues? Or can we just release? Did you people try the overhauled Android port?? It could use more beta testing!

By Manel46

Paladin (674)

04-12-2018, 01:04

Manuel.
I am testing the cursors in the bitmap modes of the V9990.
The colors and the EOR with the image color does not work in the emulator. it comes out black or dark blue. If it works on the real hardware.

By Manuel

Ascended (19466)

04-12-2018, 21:32

The EOR bit isn't implemented yet, probably because there was no MSX software yet that used it