Posts made by lhari84

@Akkeoss Sorry, posted too quickly. There's a new section "GPU Plugin" in settings, found it there. Thank you very much for the update!

@Akkeoss Hi, I've updated from RB 8.1.1 to 9.0 an still can't find the option (again). Has there gone something wrong? Thanks

@tobiwan_1984
I've found a workaround, at least partially... If you press both L2 and R2 button, after loading the game, it will work. But sometimes there occurs a malfunction that enables a shader.

@lhari84
Some more details, in my case it's a SF30 Pro, with latest firmware released for it, 1.34.
Futher, it's set to Android mode (like recommended?)

@tobiwan_1984
Hi, I got same issue. In my case I recognized that when I configure the controller, Buttons R2 and L2 are recognized as "Axis" and not "Buttons". So I exluded them for testing and afterwards it worked.

Anyway, I would like to use these controllers including L2+R2 buttons. In the past they worked, but I can't remember if recognized as "Axis" or "Buttons". Hope the Recalbox Team has a solution for it.

@karlo8321 To get rid of my BT problem - too low BT range with Pi 4B and/or RB 8 - I've tried 3 different USB BT dongles that worked fine in past with Pi 3B. None of them is working at all with Pi 4B and/or RB 8. Not any bluetooth device is found, as soon I connect one of these dongles.

I hope it's just a software issue, as I would prefer using the interneral BT of Pi 4B anyway. I've never had a range issue in the long past, just used BT dongles with Pi3 B (non +) because of the bad latency. With Pi 3B+ everything was fine. I switched to RB 8.0.x in parallel with the switch to Pi 4B, so I can't tell if hardware (Pi 4B) or software (RB 8.0.x) causes the range issue. Anyway, the fact that my USB dongles do not work at all should be caused by software.

@zing said in Pi 4 Bluetooth controller range issue:

Are your dongles on the compatibility list?
https://wiki.recalbox.com/en/hardware-compatibility/compatible-devices/usb-dongles

Not at all, only the "Asus USB-BT400 Bluetooth 4.0". But even though the green checkmark, there is note "Works with customizations to the Broadcom firmware - doesn't work from stock." - So it really may not work out of the box.

Anyway, I have two dongles with CSR-chipset, one from deleyCON, one from tinxi, which worked perfectly in Recalbox versions about 2-3 years ago, even though they are not on list.
I'm sure this is because they are using the same chipset as other dongles that can be found on the list, for example the Digitus:
https://shop.okluge.de/digitus-bluetooth-4.0-tiny-usb-adapter-class-2-csr-chipsatz-bluetoothstick-stick.html

Best solution would be if it's really a bug and I don't even need a dongle as a workaround at all
My current workaround is to use the 8Bitdo SF30 Pro only, as it provides a larger range then the other ones for any reason (not as large as before with Pi 3B+ and RB 7.2.2., but sufficient for my needs).

@zing
This seem to be other issues. My main problem is just the low range. If I'm close enough (too close for my needs), everything works as it should.

Anyway, I also could not pair a Logitech keyboard. No PIN request at all - so no pairing. In the past (about 2 years ago), it worked by connecting by SSH while pairing process. There the PIN was shown up and could be entered on keyboard and confirmed by return. Currently nothing appears in CLI.

Another experience I've made:
No external bluetooth dongle seem to work: I have 4 different BT 4.0 dongles with 3 different chipsets. In Pi 3B (no +) times, where internal BT was very crappy, it was enough to connect the dongle and it worked. Now, not any controller is found in pairing mode when any dongle is connected to USB port.
I've tried to use one of the dongles as a workaround for my range issue.

Thanks for your answer anyway.

Found some hint that USB 3 can cause issues and plugged SSD into USB 2 Port. It made things better but it's still not like it used to be with Pi 3. It's so annoying when a new piece of hardware only makes troubles

Hi,

I got another issue with my new Pi 4 & NesPi 4 Case & Recalbox 8.0.2 setup:
Today I've paired all of my Bluetooth controllers:

• Sony DualShock 4 (v2)
• 8Bitdo N30 Pro (v1)
• 8Bitdo SF30 Pro

Now the problem is that first 2 have only a range of about 1,5 meters, maximum!!
The 3rd one (SF30 Pro) offers a normal range, it works without issues in the whole room.

With my Pi 3 B+ & SuperPi Case & Recalbox 7.2.2 setup, I didn't have this issue with this same set of controllers.
Further, I have completely reinstalled Recalbox 8.0.2 and also tried both bluetooth drivers. I'm out of ideas why this happens. Are there any known issues with RB 8.0.2 / Pi 4 regarding that?

Thanks for your help!

Add. info regarding my last post:
In my case, executing the games.sh destroys the background in system view:
All 3 systems I've tested show up only a black background after reboot. Backgrounds in gamelist view are ok but still show up game themes I have disabled.

@micklabrique
Thank you so much, my missing piece was the following modification :

mount -o remount,rw /boot
echo "# Overlay setup for proper powercut, needed for Retroflag cases" >> /boot/config.txt
echo "dtoverlay=gpio-poweroff,gpiopin=4,active_low=1,input=1" >> /boot/config.txt
shutdown -r now

Hi @mYSt
I'm just fighting with enabling only specific games for each system:
I've changed affected games.sh files and wondered why still other games would be shown up. Afterwards I've checked the readme and found out that I have to run (all) the games.sh files.
If I do that, I receive errors:

What am I doing wrong?
Thanks in advance!

P.S.:
To be honest, I really like the artwork of v1.x more. I guess you have replaced a lot in v2.0 to provide more authentic pictures for each game version, that's understandable, though.
No problem at all, fortunately I can replace the background files in new version with old ones

@bkg2k That's too bad, hope you will not have to many issues because of that...

May I ask about another thing in this occasion, I'm still having issue with safe shutdown, please see my latest message in following topic:
https://forum.recalbox.com/topic/25776/safe-shutdown-not-working-nespi-4-case/7

@scavy Hi,

Now, after updating to 8.0.1, I still can't get it working. Is there anything I should/can do?
Both methods case=Nespi4case:1 overwriting and system.power.switch=... (common activation paramater in recalbox.conf) will not work.
Same as with 8.0, system will shutdown, but NESPi 4 case will not power off.

Changelog does not specify which Retroflag cases have been fixed, maybe NESPi 4 is not yet?

@bkg2k Great, this works, thank you very much!

@bkg2k Of course:

coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=E4:5F:01:75:FE:29 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 dwc_otg.fiq_fix_enable=1 sdhci-bcm2708.sync_after_dma=0 dwc_otg.lpm_enable=0 console=tty3 consoleblank=0 loglevel=3 elevator=deadline vt.global_cursor_default=0 logo.nologo splash label=RECALBOX rootwait fastboot noswap video=HDMI-A-1:D video=HDMI-A-2:D

@myst @Bkg2k
It seems with the update to 8.0.1, switching whole system to 720p will not work anymore.
As usual, I use following parameters:

hdmi_group=1
hdmi_mode=4
in /boot/config.txt

But Recalbox boots up in 2160p at 30Hz since the update to 8.0.1, no matter if parameters in config.txt exist, or not.

That's strange in a second way, I thought default configuration for Pi(4) should make it boot up with 1080p, but never ever with 2160p - even when the connected display supports it.

My current screen configuration is nothing special, a 27'' 2160p LCD monitor, connected by HDMI.

Hi,

As the following topic has been locked without eleminating all questions, I'd like to warm it up again:
https://forum.recalbox.com/topic/21488/atari-jaguar-pi4-requiere-bios?_=1643132316684

Recalbox (at least version 8.0) does not show up any (missing) BIOS information about Atari Jaguar at BIOS check feature.
Further, there is no information about needed BIOS for Jaguar in readme.txt in BIOS folder.

As in the topic mentioned above, I can confirm that about half of the tested games start up without any bios, the others just crash. Those which start up are running too slow to be really playable.

So I guess the situation is as follows:

• No BIOS needed for Jaguar at all?
• Used Emulator/Core (libretro-virtualjaguar) is not ready (yet?) to work properly on Pi 4?
• And/or it maybe will never work properly on Pi 4, because the complex original Jaguar hardware makes emulation quite difficult and/or needs more power for emulation than the Pi 4 provides.

Am I right or have I missed something?

Thanks in advance for your support.

@bkg2k @mYSt
Thanks for info, great to read that there is a chance for future optimization!
In the meanwhile I realized the issue regarding graphics memory vs. general memory. Tried to increase graphics memory to more then 512 MB in boot.txt and the system did not boot anymore So I have set it to 512 MB now. Too bad that the Pis are limited in this way.