New Online MSX emulator

Страница 34/48
27 | 28 | 29 | 30 | 31 | 32 | 33 | | 35 | 36 | 37 | 38 | 39

By Manuel

Ascended (15933)

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

18-04-2016, 22:49

openMSX source code says:

Quote:

// TODO figure out the exact timeout value. Is there even such
// an exact value or can it vary between different mouse
// models?
//
// Initially we used a timeout of 1 full second. This caused bug
// [3520394] Mouse behaves badly (unusable) in HiBrid
// Slightly lowering the value to around 0.94s was already
// enough to fix that bug. Later we found that to make FRS's
// joytest program work we need a value that is less than the
// duration of one (NTSC) frame. See bug
// #474 Mouse doesn't work properly on Joytest v2.2
// We still don't know the exact value that an actual MSX mouse
// uses, but 1.5ms is also the timeout value that is used for
// JoyMega, so it seems like a reasonable value.

By ppeccin

Champion (355)

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

19-04-2016, 17:32

Ok, that's good info. Thanks!

By ppeccin

Champion (355)

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

19-04-2016, 17:41

Guys, I'm having a little hard time choosing the correct system ROMs for WMSX, specially now that I'm including MSX2+ support.

As you may know, WMSX tries to emulate a generic machine, with International charset and 60Hz video by default (with options fort JAP charset and 50Hz)

I found (someone posted it here) a project with ROM sources that can be configured and built, and I was using it until now, but I noticed several problems with many games that only happen with the ROMs I built. Now I do not know which ROMs to use anymore...

I know there are emulators like BlueMSX that offer generic machine configs, but where do those ROMs come from?
How were they built?

Can someone shed a light on this?

Thanks

By mars2000you

Enlighted (5521)

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

19-04-2016, 19:16

The original Japanese generic MSX2+ machine in blueMSX is based on Panasonic FS-A1WX and FS-A1WSX. The firmware rom is replaced by the XBASIC2 rom. Moonsound ROM and PAC SRAM (this SRAM is in slot 2-2) are extras used for this generic machine.

[Slots]
0 0 0 0 34 "" ""
0 0 0 0 84 "" ""
0 0 0 0 24 "Machines/Shared Roms/KANJI.rom" ""
0 0 0 0 79 "Machines/Shared Roms/MOONSOUND.rom" ""
0 0 0 0 80 "" ""
0 0 0 4 66 "Machines/Shared Roms/MSX2P.rom" ""
0 2 2 2 78 "Machines/Shared Roms/MSX2PMUS.rom" ""
2 2 2 2 43 "" ""
3 0 0 64 22 "" ""
3 1 0 2 20 "Machines/Shared Roms/MSX2PEXT.rom" ""
3 1 2 4 42 "Machines/Shared Roms/MSXKANJI.rom" ""
3 2 2 4 57 "Machines/Shared Roms/PANASONICDISK.rom" ""
3 3 2 2 42 "Machines/Shared Roms/XBASIC2.rom" ""

By ren

Paragon (1338)

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

20-04-2016, 17:04

I reckon this is gonna be a hell of an update? Smile

By ppeccin

Champion (355)

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

20-04-2016, 17:51

ren wrote:

I reckon this is gonna be a hell of an update? Smile

You bet it!
Actually, Is more of a revamp than an update.

And we're just a few days from releasing it!

Paulo

By ppeccin

Champion (355)

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

26-04-2016, 17:33

Guys, is there such a thing as a Graphics6 (SCREEN 7) in YJK mode?
What is the expected behavior then?

I'm trying some game I found called Megadoom, and it seems to use this combination... (G6 mode with YJK)

By Poltergeist

Champion (276)

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

26-04-2016, 18:19

Megadoom uses a screensplit: The texts are screen 6 (or 7, not sure anymore) and the graphics are in Screen 12 (or something like that). It's not a special screenmode...

By ppeccin

Champion (355)

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

26-04-2016, 19:24

Yes, its a split, but it only changes bit 3 of register 25, and leave the mode bits unchanged.
The result is that you have part of the screen in normal G6 mode, and part with G6 + YJK.

That is the unexpected combination. What would be the correct behavior?
Does changing only the reg 25 YJK bit make the VDP go to mode G7 even if the mode bits are set to mode G6???
OR should we get an undocumented G6+YJK mode (with double the horizontal resolution of mode G7+YJK)

Could anyone test this with a simple BASIC program in a real V9958 machine? (I mean Grauw? Big smile)

Something like

10 SCREEN 7
20 LINE (10, 10) - (240, 180) : REM Should take only half the screen width
30 A$ = INPUT$(1)
40 VDP(26) = &h08 : REM Does something change? Is the line still taking half width?
50 A$ = INPUT$(1)

By Grauw

Ascended (8608)

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

26-04-2016, 19:33

ppeccin wrote:

Does changing only the reg 25 YJK bit make the VDP go to mode G7 even if the mode bits are set to mode G6???

I think so, that it overrides the screen mode to G7 in the bitmap modes (but as previous tests showed, not in the character modes).

MegaDoom probably does not change the mode registers because the line split needs to be fast.

ppeccin wrote:

OR should we get an undocumented G6+YJK mode (with double the horizontal resolution of mode G7+YJK)

I doubt it, I think I would’ve heard about it if such a thing existed.

ppeccin wrote:

Could anyone test this with a simple BASIC program in a real V9958 machine? (I mean Grauw? Big smile)

Hahaha Smile. Ok ok I’ll test it. The line is still half width, but the pixels are fat and interspersed and of different colours. That is to be expected, as two pixels in screen 7 take the same amount of space as one pixel in screen 8/12, and the spacing and colours look like YJK encoding doing its job.

Страница 34/48
27 | 28 | 29 | 30 | 31 | 32 | 33 | | 35 | 36 | 37 | 38 | 39