(2016-08-14, 08:06)trihy Wrote: Not sure about libreto and turbo buttons, but every nes emu supports turbo buttons, including nestopia, fce emu.
The idea behind a multi-emulator frontend like RetroPlayer and RetroArch is to turn every emulator into a "core" stripped of everything but core emulation.
This means that cores don't have turbo functionality. This is a good thing, because it would be a mess if every core did turbo differently (and most not at all).
Instead, the frontend implements turbo once and it works for all the cores. This is what RetroArch has done. When turbo is enabled, RetroArch pulses all buttons except for the D-Pads with a duty cycle of 50% every 6 frames (3 frames pressed, 3 frames unpressed).
RetroArch's implementation of turbo buttons is literally
23 lines of code. Copying stuff from other open source emulators, especially RetroArch, is trivially easy to do.
Keep an eye out for more of these kinds of features missing from Kodi!
(2016-08-14, 08:06)trihy Wrote: On .smc and .gen roms Im getting no emulator found. On add ons list shows 2 or 3 genesis emulators, but seems doesnt want to use them.
Are you trying to load .smc and .gen from a network drive or a .zip file? This requires support for Kodi's Virtual FileSystem. You can see which cores have VFS support in the
libretro core matrix. It's possible to add VFS support directly to cores, but this is an effort-intensive process that has to be repeated for each core.
When kodi fails to load a game because VFS support is missing, should we notify the user?
(2016-08-14, 08:06)trihy Wrote: Also, there is a way kodi could take exclusive use of the controller while kodi is on first plane? I have some mouse functions with xpadder on 360 controller that conflicts with kodi (ie I have mapped mouse movement to right analog stick and when on kodi, if I move right analog stick I get volume on screen but also the mouse arrow moving around the screen). Somes windows games have the same problem, but some others ignore xpadder and works just fine. So I dont have to close xpadder everytime I use kodi. Good for htpc users.
On Windows, Kodi uses two input APIs: XInput (more recent, for 36-like controllers) and DirectInput (for older controllers). Which one does your controller use? (Note that some controllers let you switch between the two.)