I've a i7-4770 (12 years old) with gtx1660 (2 month old, same issue with gtx770) on windows 10 x64.
I'm using openMsx 0.15.0 (I don't know if it's a development version)
With SDLGL-PP it's smoother. Where is the vsync option ?
Thanks.
Hello
- I'll tried opeenMSX 0.15.0.886 with : renderer sdlgl-pp, scaler 3xsimple, vsync on. Same issue with aleste, a very very little lag on scrolling.
- Other issue, always with aleste, i'm shoting with shift and W keys. I release keys and make a reverse. My ship is firing and I take control with just cursor key. No need to push fire keys, my ship continue to fire.
- At last, a weird issue, not reproductible easily, I'll push right cursor key to move and suddenly, it's stop. I need to release et push.
RibbSayan, can you try this? First, open the console with F10; then enter: set kbd_mapping_mode POSITIONAL then press F10 again to close the console, and let us know if that solves any keyboard issues.
As for the scrolling lag, are you emulating an NTSC MSX machine? If not, can you try just in case?
Also, what's the frequency of your video mode? If it's not 60 Hz, using NTSC may not work well.
Yes, Changing machine from Philips NMS 8255 to Panasonic FS-A1GT, the lag disappears.
Set "kbd_mapping_mode POSITIONAL" solve the reverse issue.
Thanks a lot.
Just an FYI. I installed MacOS 11.0 Big Sur (Public Beta) and Xcode 12.0 beta and performed a full clean build of openMSX-0.15.0-887 which went fine and is also working fine!
I'm receiving an error when running Catapult using Windowsx64 64-bit Builds from version 893:
openmsx-0.15.0-893-g94d47c9af-windows-vc-x64-bin.zip
to the current build: openmsx-0.15.0-899-ga6abc7320-windows-vc-x64-bin.zip
I found an issue (not sure if it is a bug yet) with openMSX 16.0-rc1 on macOS. I think it is related to privacy features Apple is adding to the OS since Catalina (I am on Big Sur beta right now).
The issue is that the command "diskmanipulator create hd.dsk 256M" fails with the error:
Couldn't create image: Error opening file "hd.dsk": Read-only file-system
It may be related to me having symlinked the .openMSX folder into Documents/openMSX (and when I start a new version of openMSX I have to grant access to Documents). I did this because Documents folder is on iCloud and it is synced between my Macs and Windows PCs. That way my config/systemroms/machines/extensions are always the same on all machines.
Maybe openMSX has to request write privileges before trying to write?
