Please help testing upcoming openMSX release!

Страница 61/61
54 | 55 | 56 | 57 | 58 | 59 | 60 |

By NYYRIKKI

Enlighted (5889)

Аватар пользователя NYYRIKKI

29-08-2021, 21:07

wouter_ wrote:

I assume there's a connection with the vram fetch timings. Notice how the data for the (bitmap) pixels is fetched in 32 blocks of 8 pixels.

Yes, this seems very likely and logical.

Quote:

It's hard to correctly emulate this behavior without _much_ more information on the exact inner workings of the V99x8

Indeed this seems a bit hard as you can not even say that this register works like this and that register like something else. The screen modes seem to affect things and if you take ie. register 25 it seems that bit 0 (SP2) has this 8-pixel fixed place to affect while ie. bit 3 (YJK) and 4 (YAE) seem to affect immediately without any delays:

SP2:

YAE:

By Grauw

Ascended (10156)

Аватар пользователя Grauw

30-08-2021, 00:18

Those are interesting findings!

By sdsnatcher73

Prophet (2328)

Аватар пользователя sdsnatcher73

30-08-2021, 07:27

Great job reverse engineering the VDP NYRIKKI! This will surely benefit emulators and FPGA implementations, so thank you!

By ren

Paragon (1883)

Аватар пользователя ren

30-08-2021, 10:30

Regarding save_msx_screen error on Yupipati #1373: I can confirm using a recent dev build, FS-A1GT. It also happens on NMS 8250 (the only other machine I tested with).

By Dolphin101546015

Champion (335)

Аватар пользователя Dolphin101546015

30-08-2021, 18:27

Pencioner wrote:

Could it be related to non-latin (cyrillic) symbols in file path? (just a guess)

No, I not using non-latin symbols. (forever for any developments)

By Dolphin101546015

Champion (335)

Аватар пользователя Dolphin101546015

30-08-2021, 18:36

Manuel wrote:

I suggest you get on to that, my dear Dolphin101546015!

My dear Manuel, so you consider this problem only mine, and I will solve it alone.
It's pity, because it just means that I need to stop using OpenMSX for development unless I have other solutions.
Thanx. Sad

By Manuel

Ascended (18240)

Аватар пользователя Manuel

30-08-2021, 20:06

No, I consider the problem unsolvable without your help and then you blame us for not having it fixed for you already....

By NYYRIKKI

Enlighted (5889)

Аватар пользователя NYYRIKKI

31-08-2021, 06:39

Dolphin101546015 wrote:
Pencioner wrote:

Could it be related to non-latin (cyrillic) symbols in file path? (just a guess)

No, I not using non-latin symbols. (forever for any developments)

As you seem to be pretty much alone with this problem, I have a feeling that it is your RAM-drive that messes up things (even when using HDD) Can you try to uninstall it and see if that changes anything? ...or maybe try some other vendors RAM-disk solution?

I can only say that I've used dir as disk feature for years doing very similar things you do. I've used different versions of Windows & openMSX on many machines with different antiviruses etc. and I've newer had any issues, no matter if I read or write, on basic or other programs. RAM disk is anyway something that I've not ever tested. I think only way to solve this is to find the component that causes this issue for you and practically it seems you are the only person who can do it as you are the only one who can see these problems. In the end it might be hardware problem, you windows might be corrupted, there can be broken driver, it might be caused by openMSX or it can be some combination of these. It might be good idea to start by looking if there are some errors in Windows event viewer.

Страница 61/61
54 | 55 | 56 | 57 | 58 | 59 | 60 |