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
The core is doing some weird logic when calling SET_GEOMETRY like subtracting 352px.
The base_width and base_height are not the same as the width and height that are the correct ones.
Actually it also calls input_set_geometry, which sets geometry_width and geometry_height with the proper values, but those variables are never used in the core.
Retroarch is able to properly display the game because it is setting geometry also based on the W and H coming from the video_refresh cb which reports the correct resolution, but these values mismatch with the SET_GEOMETRY ones.
I was about to fix this, but apparently it is done on purpose, meaning that perhaps something needs to be changed in the frontend too if this is changed.
I was about to fix this, but apparently it is done on purpose, meaning that perhaps something needs to be changed in the frontend too if this is changed.
The core is doing some weird logic when calling SET_GEOMETRY like subtracting 352px.
The base_width and base_height are not the same as the width and height that are the correct ones.
Actually it also calls input_set_geometry, which sets geometry_width and geometry_height with the proper values, but those variables are never used in the core.
Retroarch is able to properly display the game because it is setting geometry also based on the W and H coming from the video_refresh cb which reports the correct resolution, but these values mismatch with the SET_GEOMETRY ones.
The text was updated successfully, but these errors were encountered: