openMSX 16.0 released

بواسطة Gloriou

Master (204)

26-08-2020, 10:59

Awesome work Guys
Much Appreciation!

بواسطة Manuel

Ascended (18233)

26-08-2020, 11:17

You're welcome and thanks for helping us testing openMSX before release. Keep it up and we'll try to improve things further!

بواسطة ray2day

Paladin (669)

26-08-2020, 12:52

Super! Litter Box works perfect on this version!

بواسطة ARTRAG

Enlighted (6564)

26-08-2020, 12:20

Tons of improvements and fixes! Greetings!

بواسطة The Apeman

Master (164)

26-08-2020, 12:39

Nice that python 2 is not needed anymore!

بواسطة Grauw

Ascended (10136)

26-08-2020, 13:29

Congratulations! A big release!

With the new super duper YM2413 Nuked.OPLL emulation core, playing PCM samples on MSX-MUSIC now works in openMSX too! Also the SFG register mirroring fix is nice, because accessing the SFG in a page other than 0 can be convenient. The single-trigger breakpoints are cool, and the VDP command execution debug probe too. And macOS HighDPI support, and all the new machines of course!

And so many other nice improvements :).

بواسطة mzoran

Master (136)

26-08-2020, 15:02

I must cry seeing how choppy video display is in openMSX. I could be due to integrated video card on my laptop but comparing full screen openMSX and WebMSX performance WebMSX is way better - not as a real hardware but ok.
Are there any settings that provide the fastest video performance ?
Right now it looks like someone is pressing pause button or frames are being dropped big time

بواسطة Manel46

Hero (629)

26-08-2020, 15:19

It must be the video card of your laptop.
A colleague has problems for the same thing, but on Webmsx.
Of course, the CPU must also play a role.
Here with nvidea quadro, no problem.

بواسطة ren

Paragon (1882)

26-08-2020, 15:46

Congrats, lot of work!

@mzoran: I believe enabling vysnc should give you performance/results similar to 0.15 SDL1, but it's not the same & YMMV. Have you tried togglin' that? (Should be enabled by default though.) SDLGL-PP renderer required. You could try the SDL renderer as an alternative.

You're on Windows (10)? What's your GPU hw? Do you have display drivers that allow for tuning/tweaking application 3D settings?

Anyway make sure your display is @ 60 Hz for NTSC or 50 Hz for PAL machines/content (exact frequencies as reported by Manuel a while back: https://www.msx.org/news/en/openmsx-0101-released#comment-23...)

Question @ team: when using a FreeSync panel/monitor, would openMSX play nicely with that?
So when going to 50 Hz from 60 Hz, the panel would switch to 50 Hz. This would only work in FS mode I think? (Would be (very) nice if it could also work when using openMSX windowed though.)

بواسطة Manuel

Ascended (18233)

26-08-2020, 15:58

@ren no idea how SDL2 handles that. Perhaps it's in some documentation? openMSX does nothing special for it anyway.

@mzoran Did you compare with other/older openMSX (development) versions?
Did you check the framerate you get? (E.g. with the toggle_fps or toggle_infopanel commands. With the latter you can also monitor how fast the emulation is running.) More info, please!

بواسطة ren

Paragon (1882)

26-08-2020, 16:16

Did some quick searching. FreeSync seems to work best (and for a while exclusively?) w/ DirectX, however: https://wiki.archlinux.org/index.php/Variable_Refresh_Rate

And this:

https://www.amd.com/en/support/kb/faq/gpu-754#faq-Limitation-of-AMD-FreeSync-on-Linux wrote:

FreeSync should not be engaged on desktop or video playback

بواسطة mzoran

Master (136)

26-08-2020, 16:34

@ren & @Manuel: I am working on a Lenovo ThinkPad with Win10. It says the card is Intel 620.
I have not tested with older release but can try if you tell me what version to use. Regarding driver settings there are none.
But I did find monitor refresh, it was set to 60Hz and I could choose 48Hz. Selecting 48 made things far worse.

using toggle_info_panel I get FPS at 50 or above and the lowest speed I've seen was 98% but is mostly at 100%.
I have tried turning off scan lines, blur, using simple scaler and using full screen expecting maximum performance but still see as if frames are being skipped. vsync is on

بواسطة Pencioner

Scribe (1476)

26-08-2020, 17:10

Shuck up and use openMSX!

بواسطة Manuel

Ascended (18233)

26-08-2020, 17:29

@mzoran: you could try with vsync off. The FPS shws the actual frames rendered, so if it's 50 for a 50Hz MSX or 60 for a 60Hz MSX, no frames are skipped. So it depends which machine you're emulating whether the value you get is OK or not.

You can also try the SDL renderer, but that is usually worse, as it means all rendering post processing is done in software and not on the graphics card in hardware.

بواسطة Vampier

Prophet (2386)

26-08-2020, 17:52

mzoran - feel free to experiment with the video settings till you find a setting that works for you. You can also set it to SDL instead of the SDL GL variant.

بواسطة edoz

Prophet (2394)

26-08-2020, 18:04

Wow cool... this year OpenMSX became my first used emulator.. i was a fan of BlueMSX, but since i get used to OpenMSX i don't start BlueMSX anymore

Thank you so much for all the effort.. it is a huge project and cost a lot of time for sure!

بواسطة Grauw

Ascended (10136)

26-08-2020, 19:37

ToughkidCST Kim: openMSX 16.0 released - Useful feature -1- short preview.

بواسطة Manuel

Ascended (18233)

26-08-2020, 19:51

edoz wrote:

Thank you so much for all the effort.. it is a huge project and cost a lot of time for sure!

It's our pleasure. Some estimates in this site: https://www.openhub.net/p/openmsx (although it doesn't seem to see our changes anymore since 8 months ago).

بواسطة tfh

Prophet (2999)

26-08-2020, 20:41

Works like a charm... Thanks, OpenMSX team!

بواسطة santiontanon

Paragon (1519)

26-08-2020, 20:46

Very nice! Great work! From a developer's point of view I cannot say "thank you" enough, as most of the development work we do would be impossible or very difficulty without the help of openMSX!

بواسطة mcolom

Master (181)

26-08-2020, 21:31

A great thank you to all contributors! It's really true that it aims for perfection

بواسطة mariocavalcanti

Expert (96)

26-08-2020, 22:32

Great news! Congratulations!

بواسطة mzoran

Master (136)

27-08-2020, 11:35

So I did a bit more testing using the same laptop and the desktop with a proper graphics card.
My first mistake was emulating a 50Hz machine. Without having monitor set to 50Hz or using technologies such as AMD's FreeSync with the appropriate monitor this will never be fluid.
Next I switched to C-BIOS JP machine which runs on 60Hz and my monitor is also at 60Hz. This setup does give occasional fluidity but again with stutter. This is visible in info panel where frame rate drops to 55. I can't explain this since CPU was at 3% utilized and GPU was also doing nothing.
Back to laptop with the same machine and refresh rate with openmsx 0.12. This version performs better. If I switch to SDL renderer in openmsx 16 I still think 0.12 looks better.
WebMSX is nearly flawless with only an occasional tear or stutter.
Bottom line is that one should probably get a newer GPU + monitor that can adapt refresh rates so both PAL and NTSC machines have a chance of running smoothly.
However there is still this strange stutter in openmsx compared to webmsx.
Are you able to somehow profile execution to determine what causes frame drops (is it SDL calls) ?
Thanks and sorry for bitching

بواسطة wilsonpilon

Champion (277)

27-08-2020, 12:42

Great guys! Nice job on this powerful emulator.

بواسطة edoz

Prophet (2394)

27-08-2020, 13:40

I was just downloading the new MSI file.. and without reading it i did the install.. (i had different version installed)
But afterwards my Icons are not working anymore ... let's read the manual now

Edit...: It seems OpenMSX was updated but Catapult was removed but not reinstalled somehow.. Running the setup second time and choose option repair was solving the issue.

بواسطة ren

Paragon (1882)

27-08-2020, 15:09

@mzoran, the changes & smoothness (of scrolling) has been subject of discussion. First report on page 13 by the Grauw. (Note that he mentions sync_to_vblank_mode, but that setting has been ditched in favor of an auto vsync detect feature (adaptive, full, none, in that order)).

Grauw asked others to test the scrolling of his WIP RPG.

I recognize the occasional stutter thing (where e.g. Grauw would report smoothness throughout on MacOS).

Some of my (latest) findings / chaotic testing can be found on page 37) (So that's Nvidia, Win7-64, ye olden dual core PC ;))

Note that FS behaviour has also changed, from exclusive to windowed.
So overall It seems 0.15 (and before) worked a bit better/performant (for me) in this regard.

I'll do some new tests, since I upgraded drivers 'n stuff in the meantime.

ps. What also can help (but can also make things worse), on Win7 anyway, is disabling desktop compositing via net stop uxsms (admin rights required). And then there's also the High Precision Event Timer (HPET) thing you can 'play' with / investigate...

بواسطة mzoran

Master (136)

27-08-2020, 16:58

@ren: I'll switch to the other thread, thanks

بواسطة Takamichi

Champion (488)

27-08-2020, 17:38

With the Catapult I chose MSX type: Panasonic FS-A1, Extensions: ROM Hunter Mk2 and set the rom hunter mkii 8kb rom but pushing Start displays;
Fatal error: Error in "ROM_Hunter_Mk2" extension: Couldn't find ROM file for "ROM Hunter Mk2" ROM_Hunter_Mk2.rom (sha1: 77b886b3ed4048a099099d6b9b0d4cca3a05dce1).

What am I doing wrong? Emulation seems to start and run fine when the Rom Hunter MK2 extension is NOT chosen.
Another thing that has been since before 0.16: Pushing the hankaku/zenkaku language input key when openMSX is running causes [ character to be entered forever like [[[[[[[[[[. Pushing the language input key again stops that. I know that key exists only on Japanese keyboard, but can you guess why and solve? Edit: This key is where ~ key is on the US keyboard and +- is on the UK one. Do these keys cause same problem?

بواسطة ren

Paragon (1882)

27-08-2020, 17:18

@Takamichi: you need to put the .rom image (with the correct sha1) in a system_rom file pool, trying to load it via a cartridge slot won't work.

بواسطة gdx

Enlighted (4802)

27-08-2020, 17:50

The DMG for the Mac version can't mount.

بواسطة Bengalack

Champion (416)

27-08-2020, 17:57

Thank you so much for the continuous effort! This software, and this version is great, and: invaluable!

بواسطة Manuel

Ascended (18233)

27-08-2020, 20:53

edoz wrote:

I was just downloading the new MSI file.. and without reading it i did the install.. (i had different version installed)
But afterwards my Icons are not working anymore ... let's read the manual now

Edit...: It seems OpenMSX was updated but Catapult was removed but not reinstalled somehow.. Running the setup second time and choose option repair was solving the issue.

What did you mean with 'my icons are not working anymore'?

بواسطة Manuel

Ascended (18233)

27-08-2020, 21:07

Takamichi wrote:

With the Catapult I chose MSX type: Panasonic FS-A1, Extensions: ROM Hunter Mk2 and set the rom hunter mkii 8kb rom but pushing Start displays;
Fatal error: Error in "ROM_Hunter_Mk2" extension: Couldn't find ROM file for "ROM Hunter Mk2" ROM_Hunter_Mk2.rom (sha1: 77b886b3ed4048a099099d6b9b0d4cca3a05dce1).

What am I doing wrong? Emulation seems to start and run fine when the Rom Hunter MK2 extension is NOT chosen.

As ren explained: in openMSX you have extensions which define which ROMs they need. So when an extension is used, openMSX wil find and load the ROM(s) needed for it, no need to insert it manually. Put the ROM in the system roms folder where you also put all your other system roms.

Quote:

Another thing that has been since before 0.16: Pushing the hankaku/zenkaku language input key when openMSX is running causes [ character to be entered forever like [[[[[[[[[[. Pushing the language input key again stops that. I know that key exists only on Japanese keyboard, but can you guess why and solve? Edit: This key is where ~ key is on the US keyboard and +- is on the UK one. Do these keys cause same problem?

It's unfortunate you didn't report this before (or maybe I missed it?). I understand this is not what you would expect to happen when pressing this key. But, and please don't take things wrong, what would you expect to happen when pressing it?

Furthermore the following data is useful to know;
- which MSX are you emulating when seeing this phenomenon?
- what happens on another MSX type, e.g. European vs Japanese?
- did this also happen with openMSX 0.15.0, or were you talking about developer builds?
- which keyboard mode are you using? See Menu -> Misc settings -> Keyboard mapping mode
- to debug in detail (none of the developers have a Japanese keyboard...) you can do this:
1. open the console with F10
2. type the command: set kbd_trace_key_presses on
3. press F10 to close the console
4. hit the hankaku/zenkaku key. After 10 seconds, hit it again.
5. there should be output logging on the cmd prompt like window. If not, please start openMSX from the command prompt.
6. paste the output logging here. Or wherever we can find it :)

Thanks!
- to debug what's going on,

بواسطة Grauw

Ascended (10136)

27-08-2020, 21:15

gdx wrote:

The DMG for the Mac version can't mount.

Works for me when I download the DMG from openmsx.org. Then again, I was the one who built it, but that shouldn’t matter… Can you try to re-download it?

Can another macOS user confirm if it works for them?

بواسطة Grauw

Ascended (10136)

27-08-2020, 22:07

Grauw wrote:

ToughkidCST Kim: openMSX 16.0 released - Useful feature -1- short preview.

ToughkidCST Kim: How much different openMSX v16.0 vs v0.15.0 YM2413 emulation - Comparison

بواسطة Manuel

Ascended (18233)

27-08-2020, 22:25

It might be me, but I don't hear any difference

بواسطة fondacio

Master (154)

27-08-2020, 22:57

Grauw wrote:

gdx wrote:

The DMG for the Mac version can't mount.

Works for me when I download the DMG from openmsx.org. Then again, I was the one who built it, but that shouldn’t matter… Can you try to re-download it?

Can another macOS user confirm if it works for them?

Yes, downloaded from openmsx.org and works fine. Now to find a usable launcher...

بواسطة Manuel

Ascended (18233)

27-08-2020, 23:19

Why do you want a launcher?

بواسطة MarMSX

Resident (40)

28-08-2020, 01:29

Thanks to all openMSX developers and collaborators.
openMSX is essential for my MSX projects.

بواسطة gdx

Enlighted (4802)

28-08-2020, 01:44

Grauw wrote:

gdx wrote:

The DMG for the Mac version can't mount.

Works for me when I download the DMG from openmsx.org. Then again, I was the one who built it, but that shouldn’t matter… Can you try to re-download it?

Can another macOS user confirm if it works for them?

Doesn't work (SHA1=a85ae7bb7df43cd234535ffac8629812e44a02f3).
Apple seems to have changed the format of DMGs. Old systems cannot mount it. :(

بواسطة Gradius2

Hero (626)

28-08-2020, 05:27

BUG:

"- added copy/paste functionality: with CTRL+Win+V (Cmd+V on Mac) or the middle mouse button, the clipboard text will be pasted into the MSX and with CTRL+Win+C (Cmd+C on Mac), the current MSX text screen will be copied to the clipboard"

CTRL+Win+C doesn't works!

بواسطة edoz

Prophet (2394)

28-08-2020, 09:56

Catapult was removed but not reinstalled somehow.. i had to do setup - repair in windows to install catapult again. But after that everything was fine and my configuration was like before.. not sure why.. maybe it had something to do with run as administrator

بواسطة Grauw

Ascended (10136)

28-08-2020, 10:27

Gdx what macOS version are you on then? Would be handy to specify . I'm on 10.15 Catalina.

بواسطة Sylvester

Hero (539)

28-08-2020, 11:41

Nice job! I also use macOS 10.15 Catalina and the DMG works.

بواسطة thegeps

Paladin (881)

29-08-2020, 00:19

I'm so busy on Freedom Fighter that I had no time to try it until now! I'll do it tomorrow. Anyway I know it will be great, as always! Thanks to all that gave their contribute.

بواسطة Vahan

Expert (75)

29-08-2020, 03:16

Does this new version have Disk Drive support?

بواسطة Takamichi

Champion (488)

29-08-2020, 08:25

I threw the rom hunter mkii rom into the share -> systemroms folder, chose Rom Hunter Mk2 extensions, started Sanyo MPC-10, Rom Hunter mk2 menu showed, I inserted a 16k game rom (ASCII Moon Landing) to Cart B. I chose [2] and hit a key but nothing seems to be happening. I hear tape noise if I hit the PLAY button on Catapult. Am I doing everything right?

About autotyping issue, firstly it wasn't [ but ] that is autotyped most of the cases (see below). The issue has been at least since 0.15.0 but I noticed only recently when my friend told me about it. The hankaku/zenkaku key is VERY frequently accessed and it's very likely you hit it with openmsx thinking you're working with some other application.

This happen with any MSX type, as far as I tried.
Gradiente Expert DD Plus displays C with cedilla below, instead of ].
In case of CF-1200 and A1GT, when I keep the real ] key down, openMSX keeps displaying [][][] instead of ]]]. If I push [ down, openMSX displays @]@]@]@. Note on real keyboard @ is left next to [ and [ is right above ].
In case of Gradiente Expert DD Plus, pushing ] results in c]c]c]

I said pushing hankaku/zenkaku again ends the autotyping but actually I have to consecutively push the h/z key then ]. In many cases even that doesn't solve.
Gradiente Expert DD Plus never stops even by doing that. Upon attempting so, it displays ccc] OR ccc[ then continues cccing. I also noticed [ key types ' which isn't auto repeated even if the key is pushed down. Is it ` the "backquote"? (see below)
Under any MSX type, switching to other Windows application causes openMSX to stop autotyping. When that happens "Key released, keyCode: 0x400060, keyName: BACKQUOTE,RELEASE" is displayed as the key trace.
Where is " Menu -> Misc settings -> Keyboard mapping mode"? I can't find it on catapult.

The test result from Status Info screen;
Key released, keyCode: 0x400123, keyName: F10,RELEASE
Key pressed, unicode: 0x0000, keyCode: 0x00060, keyName: BACKQUOTE
Key released, keyCode: 0x400060, keyName: BACKQUOTE,RELEASE
Key pressed, unicode: 0x0000, keyCode: 0x00060, keyName: BACKQUOTE
Key pressed, unicode: 0x005d, keyCode: 0x0005d, keyName: RIGHTBRACKET
Key released, keyCode: 0x40005d, keyName: RIGHTBRACKET,RELEASE

F10 is me pushing F10 to hide the commandline Third line appeared after I've pushed h/z key after 10 seconds. ` backquote is probably the character I get by typing @ key (right next to P on my keyboard) with Gradiente Expert DD Plus. It might be a clue.
For your information, when I type real backquote on CF-1200 msx type, I push shift and @, and the trace is;
Key released, keyCode: 0x420040, keyName: AT+SHIFT,RELEASE
Key released, keyCode: 0x400130, keyName: LSHIFT,RELEASE

بواسطة thegeps

Paladin (881)

29-08-2020, 12:22

Something wrong (again) with my notebook... I get this

Couldn't activate renderer SDLGL-PP: Failed to create openGL-3.3 context: Could not create GL context: Operazione completata.

Trying to switch to SDL renderer instead...

on V 0.15 SDLGL-PP works... (but I can't go fullscreen, otherwise it crashes)

بواسطة knm1983

Hero (558)

29-08-2020, 12:26

Manuel, can't mount a DMG image on my Mac with SO El Capitan 10.11.6, the error says "openmsx-16.0-mac-x86_64-bin.dmg file system that cannot be mounted"

Any idea??

بواسطة gdx

Enlighted (4802)

29-08-2020, 12:46

Same for me.

بواسطة Grauw

Ascended (10136)

29-08-2020, 13:24

Gdx you’re also on macOS 10.11? I asked before but you didn’t answer. I’m trying to look for information on the internet about this issue.

بواسطة Grauw

Ascended (10136)

29-08-2020, 14:19

Can you guys on old macOS versions please try this dmg?

http://www.grauw.nl/etc/msx/openmsx-16.0-mac-x86_64-bin.dmg

I think hdiutil’s default file system changed from HFS+J to APFS, and APFS is not supported on macOS versions before 10.13.

بواسطة Manuel

Ascended (18233)

29-08-2020, 15:00

Vahan wrote:

Does this new version have Disk Drive support?

openMSX has had disk support for ages. Please check http://openmsx.org/manual/faq.html#rundiskstapes

بواسطة gdx

Enlighted (4802)

29-08-2020, 15:04

Thank you Grauw! You have found the solution, your image works.

بواسطة Manuel

Ascended (18233)

29-08-2020, 16:17

Great, I replaced the file on GitHub with the new binary. @knm1983 please download again and try again.

بواسطة Manuel

Ascended (18233)

29-08-2020, 16:36

thegeps wrote:

Something wrong (again) with my notebook... I get this

Couldn't activate renderer SDLGL-PP: Failed to create openGL-3.3 context: Could not create GL context: Operazione completata.

Trying to switch to SDL renderer instead...

on V 0.15 SDLGL-PP works... (but I can't go fullscreen, otherwise it crashes)

Yes, in openMSX 16.0 the minimum required OpenGL is 3.3. Next release we will try to relax this again to OpenGL ES 2.0, which will make it also usable on mobile devices (in the end).

بواسطة Manuel

Ascended (18233)

29-08-2020, 17:07

Takamichi wrote:

I threw the rom hunter mkii rom into the share -> systemroms folder, chose Rom Hunter Mk2 extensions, started Sanyo MPC-10, Rom Hunter mk2 menu showed, I inserted a 16k game rom (ASCII Moon Landing) to Cart B. I chose [2] and hit a key but nothing seems to be happening. I hear tape noise if I hit the PLAY button on Catapult. Am I doing everything right?

This option is to record the ROM to tape, so for that you need to insert a new tape in the MSX. In Catapult you can press the Record button and browse for a location for a new tape image. E.g. call it moon.wav. After that, press the key and the ROM Hunter program will save the cartridge to tape (this takes a LONG time!). When it's done, it will get back to the menu.

After that, you can start an MSX with the ROM Hunter Mk 2 again and choose option 1. Insert the tape moon.wav in the cassetteplayer and it will be loaded and run.

Quote:

About autotyping issue, firstly it wasn't [ but ] that is autotyped most of the cases (see below). The issue has been at least since 0.15.0 but I noticed only recently when my friend told me about it. The hankaku/zenkaku key is VERY frequently accessed and it's very likely you hit it with openmsx thinking you're working with some other application.

How do you think this key should be mapped to the MSX?

Quote:

Where is " Menu -> Misc settings -> Keyboard mapping mode"? I can't find it on catapult.

It's not in Catapult, it's in the openMSX menu. When openMSX runs, move to the top left corner of the screen and a menu button will appear. Click or tap it and you open the menu in which you can find the setting above.

Try to change the setting to POSITIONAL and see if it makes any difference. (This mode will not do its best to map keyboard mappings of host PC to MSX, but just uses a positional (hence the name) concept: you can type with your PC keyboard without looking at what's on the keys, just pretend you're behind the MSX keyboard.

As for the kdb_tracing you pasted: thanks a lot, that is very useful. I'll study it in more detail later, but I already have some questions:
- Can you confirm thatpressing the h/z key generates keyCode 0x00060 (which is a BACKQUOTE, according to the logging)
- Can you try to type only the h/z key on the CF-1200 and tell me what that outputs in the tracing? (The @ stuff is a bit confusing for me.)
- I wonder what generates the RIGHTBRACKET key. Can you check that out? (So what is the simplest thing you do to get RIGHTBRACKET keyName logging, without actually pressing the ] key.

Thanks a lot.

بواسطة Takamichi

Champion (488)

29-08-2020, 18:53

I managed to dump and load Moon Landing, after trials and errors to find I should push Record before setting the rom image to Cart B. I know there is no meaning in dumping a rom image out of one but emulation is another thing

As for autotyping, the key left to 1 on the US keyboard is... backquote key explained here, at the exactly same position with h/z key on the Japanese keyboard. openMSX is likely to be misunderstanding the backquote key is constantly pushed.

Since then I tried Sharp HB-8000 v1.1 I expected to find ~ being autotyped because c-cedilla of Brazilian characters v1.0 (7EH)is replaced by ~, but in reality [ (not ])was autotyped.

About mapping: there is no equivalent on Japanese MSXs because they have the ESC key there and the hankaku/zenkaku toggling is achieved by pushing CTRL + SPACE together and not by any single key, so on an emulator the h/z key either must be ignored completely (recommended) or behave as if CTRL+SPACE are pushed together.

I tried POSITIONAL setting. No improvement but worse. On GT \ is entered instead of ] and [[[ autotype continues. KEY did not work either. h/z-then-] does not stop autotyping under both KEY/POSITIONAL mode, this trick only works on CHARACTER mode. Note when I change the setting to KEY then return it to CHARACTER, the key mapping becomes European and not Japanese.
Keycode; I tried this realtime keycode display site, the code changes every time the h/z key is pushed.
243 event.key: Hankaku event.location: 0 event.which: 243 event.code: Backquote
244 event.key: Zenkaku event.location: 0 event.which: 244 event.code Backquote
Google translating here might help understanding h/z behavior.
Typing the h/z key on CF-1200 msx type, the status info is; Key pressed, unicode: 0x0000, keyCode: 0x00060, keyName: BACKQUOTE
* this line isn't followed by "BACKQUOTE, RELEASE".
There seems to be no way to enter ] without pushing ] key. When the h/z key-then-] trick to stop autotyping succeeds, these 3 lines show in the Status Info at the same time.
Key pressed, unicode: 0x0000, keyCode: 0x00060, keyName: BACKQUOTE
Key pressed, unicode: 0x005d, keyCode: 0x0005d, keyName: RIGHTBRACKET
Key released, keyCode: 0x40005d, keyName: RIGHTBRACKET,RELEASE
Edit: the h/z key-then-] solution works actually by holding down the h/z then pushing ] in that state. When I am holding down the h/z key, following two lines keep repeating;
Key pressed, unicode: 0x0000, keyCode: 0x00060, keyName: BACKQUOTE
Key released, keyCode: 0x400060, keyName: BACKQUOTE,RELEASE
Then I push ], then the followings are displayed and the autotyping ends. openMSX is thinking ] release = backquote release. The second line is repeated if I hold down the ] key longer.
Key pressed, unicode: 0x0000, keyCode: 0x00060, keyName: BACKQUOTE
Key pressed, unicode: 0x005d, keyCode: 0x0005d, keyName: RIGHTBRACKET
Key released, keyCode: 0x40005d, keyName: RIGHTBRACKET,RELEASE
Key released, keyCode: 0x400060, keyName: BACKQUOTE,RELEASE

بواسطة knm1983

Hero (558)

30-08-2020, 07:44

Thanks Grauw and Manuel , later I try , this weekend I’m out from my house, when return I can try.
Thanks a lot guys.

بواسطة ray2day

Paladin (669)

30-08-2020, 16:01

No problems her on MacOS Catalina 10.15.6

بواسطة Takamichi

Champion (488)

31-08-2020, 13:47

One more key glitch that happens with any MSX type; when I push the CAPS LOCK of the PC keyboard the Caps led of the Catapult flashes on and off, and when I hold down a character key, say A, the emulated MSX displays aAaAaA... To achieve the normal caps lock state I have to push CAPS LOCK with a SHIFT key held. Both right and left SHIFT works. Key trace when only CAPS LOCK is pushed:
Key pressed, unicode: 0x0000, keyCode: 0x0012d, keyName: CAPSLOCK
Changing CAPS lock state according to SDL request
CAPSLOCK,RELEASE is absent. When CAPS LOCK + left SHIFT are pushed:
Key pressed, unicode: 0x0000, keyCode: 0x00130, keyName: LSHIFT
Key pressed, unicode: 0x0000, keyCode: 0x2012d, keyName: CAPSLOCK+SHIFT
Changing CAPS lock state according to SDL request
Key released, keyCode: 0x400130, keyName: LSHIFT,RELEASE
Key released, keyCode: 0x40012d, keyName: CAPSLOCK,RELEASE
Changing CAPS lock state according to SDL request
Note pushing CAPS LOCK on Japanese windows activates two byte zenkaku entry mode, while SHIFT+CAPS LOCK causes 1 byte entry mode to remain and capitalize all subsequent entries, like CAPS LOCK alone does in other countries. Pushing CAPS LOCK alone is key code = 240 event.key = Alphanumeric while SHIFT+CAPS LOCK is key code = 20 event.key=CapsLocK.

Side note: Pushing hankaku/zenkaku key wit MSX type = NMS8255 causes ` to be autotyped and no key combination can stop that.

بواسطة manolito74

Paragon (1190)

31-08-2020, 14:14

It's a pity that this new version comes with TSX suppor. :-(

بواسطة Bodhi1969

Expert (90)

02-09-2020, 23:58

I don´t know if it´s an issue but in order to use my computer keyboard I always have to type a character into the Input Text field within Catapult.

If I forget this no keyboard input nor other interaction is possible.

بواسطة Manuel

Ascended (18233)

03-09-2020, 00:04

That's absolutely abnormal. Can you please give more information?
So, what exactly doesn't work and what does work? A video that shows the issue?

بواسطة Bodhi1969

Expert (90)

03-09-2020, 07:21

Well. as I wrote I use OpenMSX under Wine and Linux Mint, which is an Ubuntu derivate. I usually start OpenMSX via Catapult and have to write a charakter into that field "Input Text" field before I can write within the emulator or even use another key in there. Don´t know if a video is neccesary. Same raection if I start via OpenMSX.exe directly.

بواسطة Manuel

Ascended (18233)

03-09-2020, 07:32

First question: why use wine and not just a Linux executable?
Then: how do you proceed when using openMSX without catapult? Does the menu work? Can you open the console and type there? Does it matter which MSX you emulate or and which MSX software you're running?

بواسطة Bodhi1969

Expert (90)

03-09-2020, 08:56

Manuel wrote:

First question: why use wine and not just a Linux executable?
Then: how do you proceed when using openMSX without catapult? Does the menu work? Can you open the console and type there? Does it matter which MSX you emulate or and which MSX software you're running?

I will compile it later and see if the behaviour is another. Then I give a reply.

Do OpenMSX and Catapult have to be compiled separatly?

بواسطة Manuel

Ascended (18233)

03-09-2020, 13:18

They are separate projects, so yes. Doesn't your distro have it already? Please also check whether it works with the distro's version.

بواسطة knm1983

Hero (558)

03-09-2020, 14:35

Manuel, DMG work ok on my Mac with 10.11.6 El Capitan , and OpenMsx too.
Thanks Manuel and Grauw

بواسطة Bodhi1969

Expert (90)

03-09-2020, 15:24

Manuel wrote:

They are separate projects, so yes. Doesn't your distro have it already? Please also check whether it works with the distro's version.

Hi, Manuel,
well, I tested it with my distros OpenMSX which is 15.0 - Here everything works fine

Question is if my initial question / issue can be considered as solved, now?

بواسطة Manuel

Ascended (18233)

03-09-2020, 22:36

No, it cannot. Please try to compile 16.0 and run it on your Linux system to see if it still occurs.

بواسطة Randam

Paragon (1415)

04-09-2020, 13:03

Thanks for the new update. Looking good and trying it out.

Saw one issue in catapult on my surface laptop. It zooms low res programs automatically to 200% (due to high resolution). Most of catapult works fine with this, except for the icons/ pictures on the first tab: the LEDs, the diskette icon, the eject icon, the rom icon and the hdd icon. They are shown smaller.

بواسطة Bengalack

Champion (416)

04-09-2020, 15:41

Wanted to post that copy didn't work in the console, but then I read:

Quote:

added paste functionality to the console (CTRL+V/Cmd+V on Mac)

So, I guess only paste is implemented. I believe I can use "save_to_file"-script instead when in absolute need. But is copy from the console on any roadmap?

بواسطة Grauw

Ascended (10136)

04-09-2020, 17:09

There’s set_clipboard_text command as well.

From keybindings.tcl:

# copy/paste (use middle-click for all platforms and also something similar to
# CTRL-C/CTRL-V, but not exactly that, as these combinations are also used on
# MSX. By adding META, the combination will be so rarely used that we can
# assume it's OK).
set my_type_command {type [regsub -all "\r?\n" [get_clipboard_text] "\r"]}
bind_default "mouse button2 down" "$my_type_command"
if {$tcl_platform(os) eq "Darwin"} { ;# Mac
	bind_default "keyb META+C" {set_clipboard_text [get_screen]}
	bind_default "keyb META+V" "$my_type_command"
} else { ;# any other
	bind_default "keyb META+CTRL+C" {set_clipboard_text [get_screen]}
	bind_default "keyb META+CTRL+V" "$my_type_command"
}

بواسطة Manuel

Ascended (18233)

05-09-2020, 00:39

Bengalack: you can also output any console command to stderr and copy it from the terminal/cmdprompt (when openMSX runs from one) or from the Catapult last tab like this:
puts stderr [command]

That's what I always do when I need output.

بواسطة Bengalack

Champion (416)

05-09-2020, 20:39

Sounds good! Thanks, @Grauw and @Manuel

بواسطة imulilla

Rookie (17)

09-09-2020, 23:15

I have updated my fork with TSX based on NataliaPC's to version 16, for now only windows

can be downloaded from

https://github.com/imulilla/openMSX_TSXadv/releases/tag/16.0951

Apart from TSX support, it has been added to be able to choose the block to load from the tape. In the case of
The .CAS you can choose any block, and in the case of .TSX you can choose the blocks
preceded by a "Group start" block (ID21).

To show the list of blocks, use the command "cassetteplayer listsections" and to choose
the "cassetteplayer section" block plus the block number (eg: "cassetteplayer section 2").

It also includes support for IPS patches within a "Custom Information Block" (ID35) block.
which will be applied to the next block, for now it cannot be deactivated

بواسطة Manuel

Ascended (18233)

17-09-2020, 22:27

thegeps wrote:

Something wrong (again) with my notebook... I get this

Couldn't activate renderer SDLGL-PP: Failed to create openGL-3.3 context: Could not create GL context: Operazione completata.

Trying to switch to SDL renderer instead...

on V 0.15 SDLGL-PP works... (but I can't go fullscreen, otherwise it crashes)

Can you try this with the latest openMSX development build? Should be much better now.

بواسطة Bodhi1969

Expert (90)

30-09-2020, 08:48

Charakter-input required to write within emulation:

Manuel wrote:

They are separate projects, so yes. Doesn't your distro have it already? Please also check whether it works with the distro's version.

Hello Manuel, I now tested this behaviour with different combinations. It only occurs when using the bin.zip-files.
When using the msi or a linux installation, all works fine and typing in charakters works from the start.

بواسطة Manuel

Ascended (18233)

30-09-2020, 09:35

OK, thanks for testing. Not sure what's going on there though, but it looks like the normal installations work fine.

بواسطة Bodhi1969

Expert (90)

30-09-2020, 11:40

Manuel wrote:

[...] but it looks like the normal installations work fine.

As far as I tested, yes.

بواسطة Bodhi1969

Expert (90)

30-09-2020, 18:49

To be even more precise: I also tested again in a virtualbox with windows 7 and there the input of text works without any problems. So it seems to be a problem in connection with Wine. If so, you could mention this in the documentation.

بواسطة Manuel

Ascended (18233)

30-09-2020, 22:48

Well, I'm very surprised someone would be using openMSX with Wine, whilst that is totally unnecessary I think you're the very first and only one (Well, I hope so. I don't think we should spend time on supporting this use case, if you don't mind...)

بواسطة albs_br

Champion (341)

15-01-2021, 21:39

I'd like to make a suggestion: to put a small image of each machine available on openMSX catapult, plus a small board with absic specs (MSX generation, RAM size, FM y/n, etc). Maybe even filter by these specs.

بواسطة Manuel

Ascended (18233)

16-01-2021, 00:20

The last thing is partly implemented in a newer version of Catapult that was written in Python wth Qt, but never properly finished or released. Some people use it though. It runs in Python 3 with the Qt5 library. I have no idea how to set it up in Windows, though... Source code here: https://github.com/openMSX/catapult

The 'normal' Catapult isn't under active development anymore, only some maintenance is done. We focus mostly on the OSD menu nowadays.

بواسطة Crow

Supporter (11)

04-04-2021, 19:25

Is openMSX 16.0 coming to Linux Mint (20.1, Ubuntu based) soon? There is a "flatpak" version of it, but it "wastes" some 2,5 gigabytes of hard disk space...

بواسطة Manuel

Ascended (18233)

04-04-2021, 22:21

https://packages.ubuntu.com/search?keywords=openmsx&searchon...

openMSX 16.0 is in Ubuntu 20.10. I don't know how closely Linux Mint follows Ubuntu and we have no influence on it.

On the other hand: soon there will be openMSX 17.0 :)

About the flatpak: really, 2.5GB?? How can that be? Then you might be better off compiling it yourself :)

بواسطة Crow

Supporter (11)

05-04-2021, 10:02

Manuel, thank for your reply. I tried compiling it myself, but all I get was a several errors

بواسطة Manuel

Ascended (18233)

05-04-2021, 10:39

I can help you with if you tell me which errors...

بواسطة Crow

Supporter (11)

05-04-2021, 13:40

Manuel, I sent e-mail to you.

Share

التعليقات (90)