@orehruoy OK, I am really without options here, sorry. But, as I said earlier, if it's not working even launching directly from Retroarch.exe it's not a problem on the script itself or the config files from EmulationStation.

@saltyy Well i think its no use to try to fix a error that i dont understand, it appers every time even if i reinstall it, and tbh, there a a lot of errors on the pi ^^

and... the error is about a ps3 controller, mine is a ps4 so its kinda wrong ^^

@nismo , Hi there! I'm absolute noob and I'm not a native english speaker, so please be patient with me! I'm using the ES portable build from herb fargus on windows 10 and I'm realy interested in the mentioned launcher which would make my Retro Gaming Experience much more enyoable! Any chance to get this launcher somewhere here in the forum?

0_1531220276394_wfh.jpg
JUST LIKE THIS.

Pi Model or other hardware: OdroidXU4
Power Supply used: 5v 4A (as recomended)
RetroPie Version Used: 4.4.1
Built From: Ubuntu 16.04 minimum
USB Devices connected: mouse + keyboard
Error messages received: (none)
Log found in /dev/shm/runcommand.log (if relevant):
Guide used: (linked below)
File: (noted below)
Emulator: (Name of emulator - if applicable)
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)
How to replicate the problem:(noted below))

@BuZz After waiting for FBA to get neocd support, I finally got around to trying it. It doesn't support chd and it doesn't support cd audio. Any chance for a binary of lr-mess in the future? It takes over a day to compile and tends to fail the last time I tried, and atm it seems to be only emulator with proper neocd support.

@darishzone No worries. :)

We don't - lots of hurdles to support multiple users. I don't want to add additional script parameters btw so no need to do a pr at this time. Thanks.

You can set vars with sudo __blah= ./retropie_packages.sh

@battaglia01

https://github.com/RetroPie/EmulationStation

Hey @A12C4 Hows the grid view coming along? anything new with it as yet?

Actually, thinking about this further, it might really be best to move the scanLineWeight * BLOOM_FACTOR out of the pow call. All this does is apply a nonlinear filter to the scanlines (why?), which should increase aliasing artifacts.

Another thought I had considered was using a quadratic Taylor series approximation to the gamma filter given by x^a ~= x*(1+(a-1)(x-1)), which works pretty well as in this quadratic approximation. A cubic approximation is even closer (but may not be necessary), as shown. But I note that someone seems to have had a similar idea here with these new "zfast" shaders, so perhaps those are already doing this sort of thing...

Oh, I agree - I based it on what Brunnis himself was doing comparing the press vs LED tests: differences were minuscule. See it here: https://forums.libretro.com/t/an-input-lag-investigation/4407/524

But he did have a 240fps cam. I'm not sure if I can be bothered myself, it's just an idea. Overall it's all just out of curiosity and old benchmarking habits, which I have since the days of 3dfx cards :P I don't need this to prove anything to myself or others, since I can live with this lag as it is at the moment.

One test though I would definitely would like to conduct is to take some people who claim that are "sensitive" to lag and do some blind trials on multiple setups with various slight differences. I think the results could surprise a few, especially those who swear that 1 -2 frames of lag makes games unplayable for them :)

Nice, but so where is this advanced speed hacks menu then?

Looking at the menu source at https://github.com/libretro/pcsx_rearmed/blob/40c380a8e8080ecb38159ee5aad1ce149e9889fc/frontend/menu.c , there seem to be a ton of options missing, such as plugin selection, memory card options, advanced speed hacks etc.

It looks like these options were part of a native menu system of the standalone emulator which is disabled/unsupported in Retroarch. I made an issue here: https://github.com/libretro/pcsx_rearmed/issues/176
You can see on this blog how the menu options in the original emulator looked. They appeared on a press of ESC.
https://retroresolution.com/2016/01/01/playstation-emulation-on-the-pi-enhancing-the-experience-with-the-options-menu-part-one-basic-features-and-save-states/

Since the native menu system is based on a menu rendering library not available in Retroarch (libpicofe), the solution is to map all the missing options into the Retroarch Quickmenu. Currently, only some of the options are mapped to the Quickmenu.

@pjft said in Recent RetroPie Documentation Changes - PSX - Emulator Info and BIOS Info.:

Either that or my defaults were already overwritten by today's change :)

That could be the case. Mine was 'Auto' and I didn't run the update beforehand.

Thanks for giving me a lead. and noted on the retroarch, i know they got it locked up pretty good.