Randam - the Sedai Linux is a full version - my can deactivate the reverse function to free up memory if you want... but I never ran into issues. Also running openMSX in the Raspian GUI (or Pi OS as it's called now) is a bad idea - it will slow down the openMSX emulator a lot. Starting from the command line is the best option - but for the pi4 it won't work until the firmware is updated. (see previous post)
I'm using Raspbian Buster / Retropie with the Emulation Station front-end. It's a GUI, but not the one you mean I think? I'd like it to be a showcase of MSX software that can be easily accessed through a menu with box art etc. I have done this for the Pi 3 already which I've described here (Dutch): https://www.jeroenderwort.nl/msx-mini-een-msx-console-met-hd...
Quite a few people asked for the disk image, to relive their MSX memories.
Now we have the Pi 4. People will be using that more and more (myself included). I noticed already that the Pi 4 has a few challenges when it comes to software compatibility. So not only openMSX suffers. I doubt it is due to inefficiencies of the OS itself, it must be a driver/library issue. Confirmed yesterday that openMSX 0.15 runs just as well as openMSX 0.14 for me, it was just the scaling that killed the performance. Still does. Without scaling it works, but it's a degraded experience compared to what the Pi 3 can do, unfortunately.
Confirmed yesterday that openMSX 0.15 runs just as well as openMSX 0.14 for me, it was just the scaling that killed the performance. Still does. Without scaling it works, but it's a degraded experience compared to what the Pi 3 can do, unfortunately.
Well, that's a relief... Scaling is quite expensive if you're not using OpenGL. It also means a lot of data is to be pumped to the video card. If that path is not optimal, you may suffer. That might be what's going on behind the scenes on the Pi 4 here. (Just a guess, I have no experience with the Pi 4, but Vampier, who does have lots of contacts in that scene, said the Pi 4 was indeed quite a nightmare to get right.)
Yes I experienced frame drop before the MacOS 10.15. On my old Laptop which is MacOS 10.12 and OpenMSX 0.14
I have the same problem. I never gone deep in the openMSX settings, so there is perhaps something simple to do... ?
Video settings are :
Scaler Simple
Scale Factor : 3x
Scanline : 20%
Glow : 0%
Deform : Normal
Noise 0%
Stretch : a bit less than all border pixels
If you do this, you can monitor the frame rate:
Menu -> Advanced -> Toys and Utilities -> info panel
Then leave the menu and see the amount of FPS at the bottom left. How stable is it? Is it as expected?
Also, can you check the amount of CPU openMSX uses on your system, with whatever tool is used for that on macOS?
Other things you can try:
- different scale factor (it's in the video settings menu you found)
- different renderer. But the one you use now is default and if your GPU works well, is the fastest.
the goal is to catch the ghost as many times as possible within the time limit.
Use only Arrow keys)
Test
Start the game from MSX-DOS. Push Space key and let the game playing itself.
The Pacman sprite goes to the left exits the screen and returns by the edge of the right screen, without stopping.
Visually, I see big jerks on the sprite at times. These jerks often recur.
However, the openMSX monitoring panel indicates a constant framerate between 29.8 and 31 FPS.
The emulation speed is set to 100. But in the panel I see that sometimes it goes down to 96% to go back to 102%.
OpenMSX uses 6% of the CPU resources of my MacBook Pro, constantly.
Changing the openMSX scale do not change anything.
Of course, on a real MSX2, I do not see any slowdown or jerks on this demo.
give me your diagnosis.Doctor Manuel ! ;)
