You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When choosing the "Hybrid (Focus Top)" and "Hybrid (Focus Bottom)" screen layouts under the core options, a couple bugs happen:
Specifically under the "Software Renderer" render mode plus the "Show Opposite Screen" option, the cursor should not appear in the bottom right corner where nothing shows up as shown on the first video.
Specifically under the "OpenGL" render mode plus "Hybrid (Focus Bottom)" along with "Show Opposite Screen", the cursor inputs does not match where the cursor is pointing. As you can see on the 2nd video, I tried to type the word "test". It seems as if the actual inputs are shifted to the left, beyond what can be seen on the RetroArch window.
This was tested on a fresh new install of RetroArch in fullscreen mode in one monitor (running a 2 monitor setup).
I can confirm this issue was present since the first versions of MelonDS DS, so it shouldn't be a specific version bug.
I have tested every combination possible of Hybrid Screen layouts under original MelonDS and everything works as expected with no issues, so MelonDS could be used as a base to know the expected mouse/cursor behaviors under Hybrid screen layouts.
Cursor should be correctly positioned in the main bottom/touch screen window under the Hybrid screen layouts. If 2 bottom/touch screens are shown at the same time, ideally, the cursor should be shown on both.
Cursor movement & inputs should match what is seen on the screen under the Hybrid screen layouts, exactly like how it is on the original melonDS.
What version of melonDS DS are you using?
1.1.8
Does the problem happen in standalone melonDS?
No, it's a bug specific to melonDS DS.
What happened?
When choosing the "Hybrid (Focus Top)" and "Hybrid (Focus Bottom)" screen layouts under the core options, a couple bugs happen:
This was tested on a fresh new install of RetroArch in fullscreen mode in one monitor (running a 2 monitor setup).
I can confirm this issue was present since the first versions of MelonDS DS, so it shouldn't be a specific version bug.
I have tested every combination possible of Hybrid Screen layouts under original MelonDS and everything works as expected with no issues, so MelonDS could be used as a base to know the expected mouse/cursor behaviors under Hybrid screen layouts.
test-01-software_renderer.webm
test-02-opengl.webm
What should've happened instead?
Which platforms do you see the problem on?
Which versions of the OS?
Windows 10
Which libretro frontend are you using?
RetroArch 1.19.1 (Stable)
Terms
The text was updated successfully, but these errors were encountered: