Hello There, Guest! Register
Enjoy our site and services? You may donate to help fund server and domain costs. Donate Here for special benefits. You have donated $

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
LeapPad2 now is working quite well as a retro emulator console
It looks like it is your Atari800:

~/retroleap> grep -r LIBRETRO_ATARI800_SITE *

package/libretro-atari800/libretro-atari800.mk:LIBRETRO_ATARI800_SITE = $(call github,JabberwockPL,libretro-atari800,$(LIBRETRO_ATARI800_VERSION))

How do you get smaller screens working in retroarch? Gameboy and NGP look bad at a width of 480.

I tried this in retroatch.cfg, but nothing changes:

# T or F makes no difference

video_aspect_ratio_auto = "false"

#22 in older RA, 23 in post 1.7.5
aspect_ratio_index = "22"

video_aspect_ratio ="22"

#2x orig 160
custom_viewport_width = "320"

#almost 2x larger than orig 144
custom_viewport_height = "272"

# 480 - 320 / 2
custom_viewport_x = "80"
custom_viewport_y = "0"
If the Atari core is from my core, then it means the handling of keyboard is different. The pause problem is one thing, but the bigger issue will be lack of handling of the function keys, which are quite often used by games.

As for screens, I just change the Fullscreen Width and Height options in Settings/Video. Note that the settings are not saved when you power off, only if you quit from menu. I would prefer a per-game settings (for MAME) or at least per-core, but I do not think this is possible.

Well, theoretically, it _might_ be possible, if someone has figured out how to turn on hardware acceleration. But this is very unlikely - any info on that is either lost or closely guarded.
You can have your per-core settings persist if you launch retroarch cores from a script and just use a different retroarch cfg file for each one.

Persistent, per-core settings and easier ROM browsing are why I'm using gmenu2x to launch cores. You can still get into the RA gui (HOME+Up )after launching this way, but don't often need to once you've made your settings.

Of course, there's no gui for making gmenu2x launchers, but you only have to make a few of them.
For example, with gambatte:

#Use a different file for each core.

SDL_NOMOUSE=1 retroarch -s /roms/saves -S /roms/saves -v -c $RETROARCH_CFG -L /usr/lib/libretro/gambatte_libretro.so "$*"

lrgambatte (gmenu2x launcher text file in /gmenu2x/sections/applications)

I've just tested and confirmed that launching with this script from gmenu2x makes any changes you do in the RA menus and the volume level stick. Maybe RA saves its CFG file on exit?

Are you sure you don't want to use gmenu2x?
As an aside, I successfully did my own build of Retroleap and thought I'd include PCSX ReARMed just for giggles. I had to amend two of the source files while making due to errors with a duplicate function, but the end result is actually pretty impressive given the hardware!

I used a combination of PocketISO and PSXTOPSP to create a 60MB PHP of the Playstation game Vandal Hearts, and this is very playable despite slightly choppy music. This can be fixed by setting the Frameskip to 1, but then it messes up the in-game dialogue boxes! I'll continue experimenting in any case, but a pleasant surprise that this emulator seemingly runs quite well! Undoubtedly game-dependent tho. This is on a LeapsterGS as well, I should point out.
I will look at gmenu2x. Good work on PSX, just to think how it would run with hardware acceleration...
(01-05-2020, 02:58 AM)Jabberwock Wrote: I will look at gmenu2x. Good work on PSX, just to think how it would run with hardware acceleration...

Hi guys.
What is the button layout on this thing?
We have A, B, Dpad and that’s all?
Is this any better in performance then LeapsterGS?
The button layout is given in the github readme (link in the first post).

Performance-wise it is identical, the only differences are the bigger screen and more storage.

Forum Jump: