Wanted: urgent bugs that need to be fixed

Página 1/4
| 2 | 3 | 4

Por Manuel

Ascended (18785)

imagem de Manuel

01-03-2014, 15:05

As we're preparing a bug fix release on openMSX 0.10.0 (which will be named 0.10.1), we ask you to report here bugs you found that need to be fixed urgently! Then we can still take it along.

Thanks!

Entrar ou registrar-se para comentar

Por sd_snatcher

Prophet (3505)

imagem de sd_snatcher

01-03-2014, 22:58

Ok, I'll stop and do some testing ASAP.

Por sd_snatcher

Prophet (3505)

imagem de sd_snatcher

01-03-2014, 23:13

Here are some bug reports:

1) On openMSX v0.10 the joystick emulation still ignores the output bit of the joyport.

2) Please check if the MIDI bug on Mac OS-X that prevented it to work with Munt was fixed.

3) On OS-X, openMSX v0.10: Double-clicking on a DSK or ROM file: openMSX is launched, but boots directly to BASIC. The game isn’t run.

4) OSD Menu shows duplicate machine entries on operating systems that use symlinks to certain machines

5) Using the US-International keyboard layout on Mac OS-X causes the MSX keyboard to malfunction. Sometimes keys get stuck, sometimes ghost keys are produced. Steps to reproduce the problem:

a) On OS-X, select the US-International keyboard layout
b) Boot openMSX running a Panasonic FS-A1WSX
c) on BASIC, try to type:

PRINT"Some Text"

The MSX will show:

PRINT*"Somesssssssssssssssssssssssssssssssss

(the "s" key will be stuck until you press it again).

Por SLotman

Paragon (1240)

imagem de SLotman

01-03-2014, 23:38

I wouldn't say its "urgent" - but when I tried "dir as dsk" with a folder that had the file "·22NCE.COM" (used to run M80/L80 on DOS/Windows) - OpenMSX will not boot that disk. It works (as far as I remember) on a real machine, and on blueMSX.

Por Manuel

Ascended (18785)

imagem de Manuel

02-03-2014, 13:26

Thanks for your input so far!

sd_snatcher:
1) Are you sure? It was supposed to be fixed... (but it seems I can confirm... JOYTEST still gives the "Unknown peripheral when moving the joystick in any direction)
2) Mac MIDI support is not entirely done yet. It's actually the last planned thing to do for 0.10.1.
3) That's a known problem indeed and still not fixed.
4) That cannot be fixed. It lists all machines that openMSX has at its disposal. If the user made symlinks in/to the places where openMSX looks for machines, there will be duplicates. It's not a bug...
5) Yes, there are such isses known with US International. However, this is in SDL. We cannot fix this until we move to SDL2 or implement some other keyboard driver.

SLotman: can you contact me by e-mail to work out the details?

Por Manuel

Ascended (18785)

imagem de Manuel

02-03-2014, 15:25

Ah, about the specific point 2 of sd_snatcher: that's fixed, mth just told me.
Point 3: we can't reproduce this when openMSX is not running yet. Are you sure there is no openMSX running in the background when you try this? (E.g. NekoLauncher might have some openMSX running in the background.)
Point 4: ah, it's the symlinks that openMSX creates... (for command line ease of use). How do you propose this should be solved?

Por sd_snatcher

Prophet (3505)

imagem de sd_snatcher

02-03-2014, 16:54

1) Yes, I am. I tested with JOYTEST both on the real hardware and on openMSX
2) Thanks! The MIDI support will be very welcome!
3) Yep, I checked the Activity Monitor. I'm sure it's not running on background. Not even Nekolauncher is running. Maybe it has something to do with Nekolauncher being present on the system? After all, both Nekolauncher and the standalone openMSX will be associated with the same extensions. BTW, this problem happens on the standalone openMSX (I don't think Nekolauncher has support for 0.10 yet, so my Nekolauncher contains the v0.9.1 inside it).
4) I'm sorry, I have no idea on how to help you with that. I wish I could, but I'm very green on TCL programming. Isn't there a parameter to ask to TCL to not follow symlinks?

Por Manuel

Ascended (18785)

imagem de Manuel

02-03-2014, 20:36

Point 4: this is not Tcl.... openMSX itself lists the machines. But do you think we should not let it follow symlinks? What if you symlinked it on purpose?

Por ren

Paragon (1928)

imagem de ren

02-03-2014, 22:42

Not urgent, a cosmetic thing, but needs reporting/fixing anyway.. Smile :

toggle_freq keeps reporting 'set to 50hz' even when freq has just been set to 60hz.
(In fact, it IS working in basic, but NOT while in a game or demo)

Tested: 0.10.0 & daily 02-27. Win7-64

(.. And somewhat of a feature request: I already find blur at setting '1' in SDLGL-PP too much.. Any chance the change from '0' to '1' can be made more gentle? Smile)

Por Sylvester

Hero (555)

imagem de Sylvester

02-03-2014, 22:57

About point 3, i have the same problem as sd_snatcher which is very annoying. It's very strange bug, because when I click on a .dsk file after the installation it works. And when I click on the file for the second time, it doesn't work any more Question btw i'm running osx 10.9.2 and also tested with 0.9.x, 0.8.x, all have the same problem. And I'm sure this feature worked in the past....

Por Manuel

Ascended (18785)

imagem de Manuel

02-03-2014, 23:00

sd_snatcher: the proper version of openMSX does get started when double clicking a ROM or disk image? (So, not the one of NekoLauncher or NekoLauncher itself.) Can you perhaps try after uninstalling NekoLauncher?

ren: weird, it works fine when I try it... However, the display seems to look at the whole VDP reg 9, instead of only bit 1. I'm fixing that, try the next build Smile Please let me know if that's better.

Página 1/4
| 2 | 3 | 4