@kevgal try updating from source the lr-vice package, the bug should be fixed.

@sleve_mcdichael said in lr-Duckstation disappear !!!????!!!:

~/RetroPie-Setup/scriptmodules/libretrocores/lr-duckstation.sh

i did the whole process, however this "extras" didnt appeared in Retropie Setup.

I´'m using RPI3

@mitu thanks you, I hope it will help.

P.S. seems like it helped, enabling v-sync doesn't causes sound issues anymore.

@geese-howard said in LR-FBNEO so slow to load/unload a game:

1.0.0.03 c8d75dc

This is not the latest commit, meaning you probably updated from binaries if you updated today, i recommend always updating from sources.

Also, i remember people mentioned having weird boot delays when using (8bitdo?) controllers in bluetooth mode, is that what you are using ?

@geese-howard said in LR-FBNEO so slow to load/unload a game:

Remap directory: "/home/pi/RetroPie/roms/arcade/mame2003-plus"

?

@sleve_mcdichael Yeah, it's a bit strange. I'll try that later and let you know what happens. Thanks as always.

@NelloHD said in Error after Update setup Script:

I honestly don't understand where to check the version.

You can check the log file produced during the update, it should be one of the log files in $HOME/RetroPie-Setup/logs. Find the file (they're time-stamped) and you can view it with zless $HOME/RetroPie-Setup/logs/<filename>.gz

how do i restore?

You can checkout a specific - major - version with

cd $HOME/RetroPie-Setup git checkout <version>

You can also rewind to a specific commit in time with

cd $HOME/RetroPie-Setup git checkout <commit-id>

but you need to know the commit-id.

Is your Pi is not connected to the internet/network/WiFi ? You may try accessing it from your PC, as described in the File Shares page, this way you'll be able to find the file in question.
Try reconfiguring again your gamepad from EmulationStation, from the EmulationStation menu (accessible pressing the Start button), go to Configure Input and re-configure the gamepad. See if that changes anything when you start the game.

@mitu said in Cannot access the internet.:

@ignatius Then the problem is your Wi-Fi connection to the router. Assuming you get an IP address from it, check the Wi-Fi AP for any MAC based access rules or firewalls that might isolate/block your Pi.

First of all, sorry for the delay in replying. I had a brief hospital stint. I gave up on trying to resolve this. Instead, I just chrooted the Pi system, and installed everything that way. It's not exactly the best way to accomplish this, but it works.

@AlphaBetaPie I see no such message in genplus-gx code so i suppose those messages are handled by the frontend (retroarch). FWIW, Kronos and yabause are using the newer libretro api for disc control, while genplus-gx seems to still be using the older disc control api, if i had to guess the difference is probably related to that. Nothing i can do about. Are you sure your retroarch is up-to-date ?

@buzztea said in Problem with the video scaling Option in RetroArch:

I did the same.
However, if I save the "custom" option for video scaling under "save core overrides", then it works. If I now change the video scaling option in another game to "core provided" and then save it under "save game overrides", then the next time I start this game I also have the "coreprovided" setting. Strange...

that's right. the game override takes priority over the core override (otherwise game overrides would never be activated once you have a core override)

@theotherdan said in SN30 Pro - Lag Problem with the SN30 pro:

The issue with the case was no shielding on the USB3 chip (As per the RetroFlag support). If the SSD adapter was plugged into the USB3 port, there was a range of about 3 feet. When I used the USB2 port, it worked as expected.

I feel it is worth adding to this.
I recently bought a plugable bluetooth adapter to add to an older PC that didn't have built in bluetooth. The packaging specifically said to plug the adapter into a USB 2.0 port instead of a USB 3.0 port to increase range.

I was puzzled by this but sure enough it is true. Here is a page that helps explain a little:
https://www.bluetoothandusb3.com/the-explanation

So best advice is to always use USB 2.0 ports for bluetooth, and possibly wireless devices in general when possible provided the device won't exceed the speed of a USB 2.0 port.

But nuts is pretty much where my head is at on this, yeah.

@Ashpool just to let everyone know, the author posted a revised file on that github site to fix this.
Nevertheless, appreciate everyone's attempts to help me with this. Cheers!

@sfriedrich the ps4 controller is supported. You can either use a micro usb cable or sync it up via Bluetooth. To do that, you have to put the controller into sync mode by holding the share and PS buttons down until the light on top starts flashing. Go to the retropie menu and then Bluetooth, and sync it up. It will come up as “wireless controller”, then just configure it as you would any controller in emulation station.
And no you don’t have to use a systems original controller. you can use any controller usb or Bluetooth , including ps3. Retropie makes a mapping for each emulator to use your controller that you are using. You just have to configure it in emulation station.

@genge094 said in keep getting stuck on one part of running retropie set-up script on raspbian:

@sleve_mcdichael thanks! I was able to get it to download on the full desktop OS but it boots into a black screen. I guess I would have to start a new topic for that one though.

Can you describe what you exactly did ?