3DS emulator for Pi users based on "Borked 3DS"
-
@DTEAM Are the scroll bars showing up in your configuration windows? If not, is it possible that the cmake flags didn't work?
It would help to see a photo of exactly what the problem is, as I am having difficulty understanding it. On my Pi, the configuration menu is a fairly small window that doesn't come close to filling the whole screen. Also, I can click and drag the menu border to change its size. In the default layout, the text spacing adjusts to fill whatever available space there is inside the window.
-
At the bottom of the second picture, the box of the Advanced tab stop just after 0.000 ms and it's not possible to go below that.
-
@DTEAM After investigating further, the problem is on my end. I am going to re-work it and try posting a new commit. Is the problem limited to the Graphics -> Advanced tab or are there others? I believe that the System tab already has scrolling bars enabled.
-
@gvx64 said in 3DS emulator for Pi users based on "Borked 3DS":
@DTEAM After investigating further, the problem is on my end. I am going to re-work it and try posting a new commit. Is the problem limited to the Graphics -> Advanced tab or are there others? I believe that the System tab already has scrolling bars enabled.
It's others. For some, you have the scroll bar, but even if you scroll down, you don't have access to all the options. I'll try to give you a more detailed overview tomorrow.
-
-
@DTEAM I appreciate the detailed analysis. Can you let me know the exact screen resolution that you are using that is resulting in this issue? For me to be able to resolve this issue, it is important that I can reproduce it on one of my Pi4's. Once I am finished trying to get shader acceleration functionality working I will see if I can get this problem to reproduce on my Pi's.
-
My screen is 800x480 and my "emulator resolution" is 640x480
[Layout] anaglyph_shader_name=rendepth (builtin) anaglyph_shader_name\default=true custom_bottom_height=480 custom_bottom_height\default=true custom_bottom_width=640 custom_bottom_width\default=true custom_bottom_x=80 custom_bottom_x\default=true custom_bottom_y=500 custom_bottom_y\default=true custom_portrait_bottom_height=480 custom_portrait_bottom_height\default=true custom_portrait_bottom_width=640 custom_portrait_bottom_width\default=true custom_portrait_bottom_x=80 custom_portrait_bottom_x\default=true custom_portrait_bottom_y=500 custom_portrait_bottom_y\default=true custom_portrait_top_height=480 custom_portrait_top_height\default=true custom_portrait_top_width=800 custom_portrait_top_width\default=true custom_portrait_top_x=0 custom_portrait_top_x\default=true custom_portrait_top_y=0 custom_portrait_top_y\default=true custom_second_layer_opacity=100 custom_second_layer_opacity\default=true custom_top_height=480 custom_top_height\default=true custom_top_width=800 custom_top_width\default=true custom_top_x=0 custom_top_x\default=true custom_top_y=0 custom_top_y\default=true factor_3d=0 factor_3d\default=true filter_mode=true filter_mode\default=true large_screen_proportion=4 large_screen_proportion\default=true layout_option=0 layout_option\default=true mono_render_option=0 mono_render_option\default=true pp_shader_name=None (default) pp_shader_name\default=false render_3d=0 render_3d\default=true screen_bottom_leftright_padding=0 screen_bottom_leftright_padding\default=true screen_bottom_stretch=false screen_bottom_stretch\default=true screen_bottom_topbottom_padding=0 screen_bottom_topbottom_padding\default=true screen_top_leftright_padding=0 screen_top_leftright_padding\default=true screen_top_stretch=false screen_top_stretch\default=true screen_top_topbottom_padding=0 screen_top_topbottom_padding\default=true small_screen_position=2 small_screen_position\default=true swap_eyes_3d=true swap_eyes_3d\default=false swap_screen=false swap_screen\default=true upright_screen=false upright_screen\default=true -
How is the performance on the Pi 4? I've been tempted to upgrade to a 64-bit system but not sure I can be bothered, as 32-bit seems to be where the performance caps out anyway...
-
@StonedEdge With an aggressive overclock (e.g. 2300MHz/900MHz+) some 3DS games are playable on the Pi4, mostly RPGs. In addition to that you will need to optimize every setting possible as well as make use of any possible cheats that can speed up gameplay. For example, the 150% speedhack in Pokemon Sun is enough to get the game playable on my Pi4, which was a pleasant surprise. Less demanding RPG's like Etrian Mystery Dungeon, Etrian Odyssey, Pokemon Mystery Dungeon, Pokemon ORAS all seem to be playable even if they are not quite at full speed. That said, games like Mario Kart and Smash Bros are just out of the question as really any slow-down is completely unforgiving in games like these. If your interest is mainly RPG's and you are comfortable with overclocking, then I would say that it might be worth it for you to get Borked3DS working on your Pi4.
That said, I believe that the bigger motivation for you to make the jump to 64-bit should be for Gamecube emulation as that is lower hanging fruit than 3ds. Gamecube emulation is a measurably less demanding than 3DS in large part because dolphin has the CPU override feature that works far better than it does in Borked3DS to speed up games on slow hardware (honestly, dolphin is just a better piece of software than citra was and it has far better optimization for use on a variety of devices).
-
@gvx64 said in 3DS emulator for Pi users based on "Borked 3DS":
@DTEAM I appreciate the detailed analysis. Can you let me know the exact screen resolution that you are using that is resulting in this issue? For me to be able to resolve this issue, it is important that I can reproduce it on one of my Pi4's. Once I am finished trying to get shader acceleration functionality working I will see if I can get this problem to reproduce on my Pi's.
If it's to hard to set it blindly, I'll connect my Pi to a PC screen to do the setup. The arrow control on the screen with a joystick and the hotkeys combo settings with gamepad are more important than my issue I think. Thanks for your hard work.
-
@DTEAM No worries, this task is still on my radar. Once I start on it I want to begin by copying your screen resolution and seeing if I can reproduce the problem on my Pi. The problem you are describing is potentially more than just an issue of the config window being too large to fit the window size on the lower res since the text spacing and size is supposed to automatically adjust based on the window size. The fact that yours is getting cut off tells me that there is some potential issue in the window re-sizing functionality.
I am planning to work on your issue once I am finished with the Hardware Shader Acceleration. I really want to get the Hardware Shader Acceleration working on the Pi as it can (at the very least) allow users to precompile shaders and potentially provide other significant performance gains.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.