2016-05-10, 03:37
(2016-05-10, 02:36)Serg86 Wrote: - Current build (May 9th) doesn't bring the game to front when you start it.What game? What core? can you post a debug log?
(2016-05-10, 02:36)Serg86 Wrote: - (Only tested NES & SNES games) Aspect ratio is wrong. On a 1920x1080 display, the width is approximately 200 pixels less than it should be for 4:3. Not sure if these measurements are accurate as I don't know if the game displays black pixels on either side, but first coloured pixel to last, measuring a screenshot with Gimp resulted in 1234x1080. 1440x1080 is the correct resolution for 4:3 content. Playing around with the video settings of 4:3 content changes the game display as well. ~17% blackbar reduction acts as a workaround, it puts it very close to the correct aspect ratio.
Can you post a debug log? In it, you will see:
Code:
2016-05-09 18:19:09.158 Kodi[9079:303] Debug Print: GAME: ---------------------------------------
2016-05-09 18:19:09.159 Kodi[9079:303] Debug Print: GAME: Opened file /Users/garrett/Desktop/Desktop_ROMs/Chrono Trigger (U) [!].smc
2016-05-09 18:19:09.159 Kodi[9079:303] Debug Print: GAME: Base Width: 256
2016-05-09 18:19:09.159 Kodi[9079:303] Debug Print: GAME: Base Height: 239
2016-05-09 18:19:09.159 Kodi[9079:303] Debug Print: GAME: Max Width: 512
2016-05-09 18:19:09.159 Kodi[9079:303] Debug Print: GAME: Max Height: 512
2016-05-09 18:19:09.159 Kodi[9079:303] Debug Print: GAME: Aspect Ratio: 1.333333
2016-05-09 18:19:09.160 Kodi[9079:303] Debug Print: GAME: FPS: 60.098812
2016-05-09 18:19:09.160 Kodi[9079:303] Debug Print: GAME: Sample Rate: 32040.500000
2016-05-09 18:19:09.160 Kodi[9079:303] Debug Print: GAME: Region: NTSC
2016-05-09 18:19:09.160 Kodi[9079:303] Debug Print: GAME: ---------------------------------------The core has a resolution of 256x239, which is an aspect ratio of 1.071129707112971. Does that solve the mystery of your missing pixels? Can you use the "zoom" action to resize the game to fullscreen?
(2016-05-10, 02:36)Serg86 Wrote: - I use an iBuffalo Classic USB SNES Gamepad. The DPad is recognized as 2 axis rather than individual buttons, which is fine, except currently, axis on NES cores are used for rewind and fast forward. I can play without issue if I disable rewind. It also has no Guide button.
How did you map the dpad to the main controller? The debug log contains all input, so this might show us what's wrong.
(2016-05-10, 02:36)Serg86 Wrote: Which brings me to a suggestion. If it's not on your todo list yet, please consider mapable hotkey combinations. Recalbox has a, in my opinion, fairly elegant solution out of the box. They use the guide or PS button on controllers which have it. Using the DualShock3 as an example, PS Button + Start exits the game. PS Button + Cross opens the Retroarch menu and a few others. The SNES controller doesn't have a guide button, so the select button is used instead.
This would solve another issue with controllers such as these. If you play an SNES game with an SNES controller, because all buttons are used for gameplay, you can't get out of the game unless you have a different input device hooked up. I know this issue is not really that big, since most people have something else to control Kodi with, but it's nice to move from game to game without putting down the pad. Hotkey combinations would solve that.
In the settings, you could set one hotkey, then a separate button for every function you desire.
The button mapping process is split into two parts: everything is mapped to a 360 controller, then the 360 controller is mapped to Kodi actions. Only the 360-controller mapping can be changed in the GUI (by configuring the "Kodi" controller). The 360-to-Kodi-action translation is controlled by joystick.xml.
What this means is that we can have a "meta" button that allows input to escape the game and be passed to joystick.xml. We can use both the Select and Guide/PS buttons to cover all controllers. A setting in Game Settings can also allow combos to be mapped to "meta", so the user could escape actions by pushing both triggers. That way, the user can only configure which buttons are "meta", but they'll have to modify joystick.xml to change the Kodi action.
