Hi,
I recently gave OpenMSX a try and really like it.
There's only one larger issue that's keeping me from really really liking it, and that's that in Windows 10 full screen mode with vsync does not really work for me. Windowed mode sort of works allright, but as soon as I switch to full screen mode there are scaling issues (it seems to open a borderless full window in windows?) and I haven't been able to find a vsync setting either.
I read what I could on this forums and on GitHub issue tracker whether there will be any improvements to full screen mode and vsync implementation when using on Windows 10, but as far as I understood that's a planned future development path (hope I'm correct).
Anyway, I'm also using Retroarch, which has come a long way over the past years, and has developed amazingly, giving access to opengl, direct3d, vulkan with a (huge) archive of very nice shader possibilities, vsync, low latency audio, fencing etc for low input latency (including a "frame delay" option to have input latency very close to real hardware). It's just very nice to use with also support from the developers who are keen on helping developers create an "upstream" core. Once done it can be run on a wide array of devices from android, to linux, to windows to handhelds and consoles.
Recently the author of Mesen, a great and accurate Nintendo NES emulator, created an upstream libretro core, and while reading his development posts in the forum I was surprised that he mentioned that (to his own surprise) it only took him a day to create the core.
Please see the author (Sour) his forum post here:
and to quote his introduction:
After being asked several dozens of times if/when I was going to port Mesen to libretro (and seeing a lot of people saying it couldn’t be done because “lol C#”), I finally got around to doing so. It barely took a day (and less than a thousand lines of code), so now I’m left wondering why I didn’t get it done earlier :-)
Given this I'm hoping there's willingness among the OpenMSX devs to look into creating an upstream OpenMSX libretro core also. As a developer you pretty much "own" an upstream core, in the sense that you're the one to validate any pull requests. With the added benefit's that the platform more easily attracts the attention of developers who may help improving the core.
Hopefully this is something that OpenMSX devs are willing to explore, and maybe it will be similar to Sour's experience "It barely took a day (and less than a thousand lines of code), so now I’m left wondering why I didn’t get it done earlier :-)".