Posts by 5schatten

Quote from wvxx

Hey there 5schatten and guys,

First of all thanks for your hard work in making this build happen, this is exactly something I've been looking for

As much as I enjoy using it, I'm also facing a couple of issues which I couldn't resolve myself so I finally gave up and decided to ask for your assistance.

So here it goes:

- PSX and Dreamcast emulators are terribly laggy including crackling sound which I just can't stand, it sounds terrible and my head starts to crack the moment I hear it. I messed around with different drivers and latency settings to no avail. A very small improvement is what I managed to get. Interestingly, this does not happen with windows version of retroarch installed on the very same pc (tested with gl/d3d and wasapi for audio), so my feeling here is that it might be related to drivers. Are there any different drivers available to test? I doubt I'll be able to install them due to read-only fs, correct?

- Second issue I have is with PPSSPP, basically I'm not able to make it stretch to fullscreen, it takes up only around 1/4 of it in the bottom left corner. Settings are fine according to instructions I've found on the net. I also noticed that now after changing some of them, games no longer boot up, I can only see intro and then it gets back to emulationstation I guess removing the configuration file would resolve the issue, but it still won't utilize entire screen...

So of all the emulators I tested already, only SNES works flawlessly. I'd love to play some classic PSX/DC games so I would really appreciate some help (and my wife too, she just loves spyro ).

My hardware is as follows:

AsRock Q1900B-ITX (integrated Celeron J1900 and Intel graphics)

4GB RAM

Audio going through HDMI via AVR, works fine for movies/music etc.

I'll happily provide all kinds of logs if you tell me what is needed.

Thanks a lot for any help in advance!

Display More

Check the emulator FAQ I've added some configuration details to libretro-pcsx-rearmed and change Beetle-PSX to PCSX ReARMED which should run fine. You can't install Windows drivers on Unix/Linux systems so you have to deal with it. If it performs better on Windows it's probably related to optimization issues. Anyway your J1900 is really really slow even compared to my 10W low-end HTPC j3455 UserBenchmark: Intel Celeron J1900 vs J3455 which delivers about 60% more performance.

If PPSSPP does not start in fullscreen delete the .ini files in \\yourdevice\Configfiles\ppsspp\PSP\SYSTEM\ and apply an update of my builds so the default config should be restored. The default config in ppsspp.ini should contain a line FullScreen = True which forces fullscreen in PPSSPP.

Also what resolution does your TV use? 1080p or 4k?

Quote from niabi

Yep, did that, correct hashes and all, but oh well if it doesn't run well I won't bother anymore with it, I'll stick with the standalone.

Yeah I guess you are right, but I don't find evdev to be that complicated and you only have to do it once, unless you change controllers a lot. Then the emulator runs at a very decent speed, so I won't complain, I still get to play Giga Wing

Giga Wing -> FinaBurn Alpha?

Quote from niabi

I tried that, several times,unless my bios files are corrupt, but they do have the correct hashes, the standalone reicast works with my DC images, but using your build (or mine) I can't get the freaking libretro one to work, don't know why.

and I agree standalone Reicast is a mess to configure the gamepad, but its not that hard and once you do it it runs very good on the S905 (not perfect of course) which is surprising.

I am actually trying to port the script that they use in Retropie to configure the controller for different emulators from ES itself, if that works then the controller would be a non-issue

You placed the bios files dc_boot.bin & dc_flash.bin in the ...\bios\dc\ subfolder? Even if it runs I have some graphical glitches so I guess it doesn't link correct to libGLESv2 or something but naomi stuff like boots fine even though it's quite slow.

The whole evdev controller config is a mess so they should rework the SDL backend what's IMHO the absolut basics if you provide an emulator

Quote from Cael

its late.. 2 weeks late (me and the months of December and for that matter November and december) dont exactly mix. (i've been told i should seek help in at that time of the year again in diagnosing SADs, but happy new year 5schatten

I've been busy w/ my sort of "Personal Hell" both inner and outer since real late November,so i didnt really monitor for Updates. I went unchecked till December 31st, (new years eve when the Depression began to lift and i could ENJOY things once more) but the build i have in my Download history doesn't match your RC change logs... (so i hope it wasn't a broken-pulled build) the Filename is "LibreELEC-RPi2.arm-9.0-RR-201852-44f803a.img.gz" which seems to place this between RC3 builds "201851-1acbb17" and "201852-52323f1"

i made sure to go thru the builds i didn't recognize for any that indicated to delete something before updating. the only one i couldn't seem to do is for "RC4 201901-c30d584" and this change/deletion request: "completely reworked mupen64plus standalone -> superseeded by m64p -> delete your old mupen64plus config dir before you update!" (simply i couldn't find the folder (so i guess i should be good either way.

(Would be nice if there was a script like in the old days of XBMC on the Xbox that could check for updates and display whats new,but for here, it'd pull from Google Drive download to the Update directory , Display whats new , if anything is marked "Delete before updating" it would delete then restart. sounds too much work to make it to save a few moments of "Get up off laze-arse, check forums, read change logs for if an update Requires configs to be deleted, copy update over, Update")

but either way i hope the month of December treated you fairly and that sofar 2019 is starting off well for you!

Better late than never Happy new year too.

Well if there is no mupen64plus standalone directory then probably because it's not listed as a common or ARM SBC emulator so it's only available for Generic builds. About the automatic updates keep in mind that this is still a somewhat beta/WIP build. I'm still reworking stuff and try to handle things better than others did in the past so I'm steadily changing stuff in the underlaying system. I could have said well check your mupen64lib paths and update them but just telling perople to delete a folder is the safe way to do this.

I could change a lot of stuff to "auto update" but then you would lose the ability to adjust settings or I would overwrite your custom config with every update what is not a convinient way too.

Quote from niabi

Mind sharing how you got it to work? I am unable to make it work.

Well get valid bios files & place then in the correct diretory and it will start. But it runs like §%$§&§ for most games but blame libretro overhead for that The standalone core would maybe perform better but it's IMHO a pile of shards without a proper SDL2 implementation which allows at least an easy controller configuration

SDL code completely broken · Issue #1322 · reicast/reicast-emulator · GitHub

Make SDL input usable · Issue #1371 · reicast/reicast-emulator · GitHub

Quote from Marciano

Thanks good to know i will try a nuc8i7 then.

With pcxs2 is it possible to remap the esc button on my ps3 controller to exit games?

I can’t find any hotkey settings in pcxs2 controller settings.

NUC8i7HVK? Well if the Vega M is supported it should kick some asses

Hmmm I don't know if it's possible but haven't had a deeper look into this usecases since I always used a mini keyboard for inputs.

Quote from Marciano

I modified es_systems.cfg and now it runs fine.

I also try some ps2 games and they are running great at 720p.

I have a nuc7i5bnh (kabylake) and trying to get 1080p but then it begin to stutter. Also with dolphin.

Is it my hardware that isn’t capable of runnnig games full speed at 1080p or am i missing some settings.

Well don't go crazy... it's "just" a NUC with an i5-7260U which is about as fast as my desktop i3-6100 so the IGP can't handle 1080p or higher resolutions for Dolphin or else.

Quote from Marciano

Thanks will take a look at that.

No problem starting games from ES is allright but it tought the other way was easier todo but not to set it up

Other question how/where to set up N64 games?

when in ES i try to start a N64 game it brings me back to ES nothing happend.

My roms file names are like this: 007 - GoldenEye (Europe).n64

Display More

Logs. A standard installation with unmodified es_systems.cfg runs N64 games out of the box.

Quote from Marciano

Well i use this command in my skin

Code

/storage/.config/dolphin-emu/dolphin-mariokart.py

dolphin-mariokart.py

Python

#!/usr/bin/python
import subprocess
subprocess.call("systemd-run /usr/bin/dolphin.start /storage/roms/wii/MarioKartWii.wbfs", shell=True)

Does it needs ALSA to start also?

Well read what ALSA actually is and you will understand why it's crucial... one way or another.

https://en.wikipedia.org/wiki/advanced_linux_sound_architecture https://wiki.archlinux.org/index.php/advanced_linux_sound_architecture

If it works with ALSA/PA in Emulationstation or else and not from this script there is basically not much I can do. Normally it should shut down Kodi, set the environment and start the emulator but if it doesn't well... the scripts are not intended to work this way

Quote from Marciano

If not then game is not starting with custom skin command.

Is Set to ALSA dolphin crashes that's why

I found that option in ES thanks.

I'm using my tv remote to control my NUC trough CEC

Then your custom command doesn't run the script correctly and there is no ALSA device available which leads to a crash.

Quote from Marciano

if advanced.conf backend set to ALSA dolphin with sound in ES.

So why did you set it to Pulse in the first place?

Quote from Marciano

I see your point but i'm trying to setup for my little boy so he doesn't have to going into ES and select game first with ps3 controller to navigate/select game and then take the wii mote it's just too much handling for him right now.

Well as I said have a look at the ES menu / UI Settings / Start on system & select Wii. Should be convinient & easy to handle too. Or what do you use to control your HTPC?

Marciano

Check Configfiles\dolphin-emu\Dolphin.ini if you find Backend = ALSA or Backend = Pulse this should match the configuration of advanced.conf anyway check first if Dolphin runs fine with sound in ES.

If you use hdmi:CARD=PCH,DEV=0 so your first HDMI output number 0 as sound output device your asound.conf should be fine. So try to set ALSA as audio backend in advanced.conf and also ALSA in your Dolphin.ini normally this is done automatically but I have no clue what this indirect-launch-per-python-over-systemd-script-magic screws up.

To be honest I don't see what's the point of this whole thing I mean sure if you use a custom skin you need to launch commands individually but screwing up the whole system instead of launching ES with Wii as "start up system" set what just takes seconds... well makes no sense to me. What's the benefit? Save 5s and some menu scrolling?

Build RC4 | 201902-22cb18c is online for Generic & RPi

• upgraded Generic/RPi kernel to 4.19.14
• updated vulkan-loader to 1.1.97
• fixed Emulationstation scraper (WIP)
• added several configuration options to advanced.conf
• if a newer advanced.conf is shipped with an update it will replace the existing one with a default conf
• you can now set individually refresh rates for Amiga / Atari / C64 / Dolphin to match PAL(50) or NTSC(60)
• you can disable the demo games (2048 / MrBoom)
• you can disable id games ( PrBoom /TyrQuake )
• updated Pegasus-Frontend theme path for autoupdates -> delete your theme folder in ...\Configfiles\pegasus-frontend\themes to avoid double listed themes
• updated several libretro-cores
• updated dolphin & citra

Quote from Marciano

Backend in advanced.conf was set to ALSA and chanced it to PulseAudio and that works.

But then no sound in dolphin so i setup asound.conf like you said in OP.

Then set rr autoconfigure audio to false still no sound.

Strange thing is when backend set to pulse audio and in dolphin the audio is set to pulse.

When i im dolphin change backend to ALSA sound is working.

But when i close dolphin the last audio backend setting in this case ALSA isn’t saved

It’s always back to pulse.

Display More

Well it should be obvious why it's always Pulse in Dolphin when you set PulseAudio in an overall configuration file. If you set the audio backend to PulseAudio and change it manually in Dolphin it will most likely just crash and if you use ALSA as backend and set it to Pulse in Dolphin there will be no sound.

Make sure your asound.conf is configured and use either PulseAudio or ALSA as backend but stop changing audio backends in the emulators.

Quote from Marciano

5schatten I put this dolphin.py in my custom skin and set the right path to it

Python

#!/usr/bin/python
import subprocess
subprocess.call("systemd-run /usr/bin/dolphin.start /storage/roms/wii/MarioKartWii.wbfs", shell=True)

In the beginning it was launching mario kart from submenu in skin just fine couple of times but now somehow it looks like kodi is just restarting when starting game.

Sometime it will start from submenu but most of the time kodi is restarting but there is no crash_log.

I found in /var/log/dolphin.log this

Code

QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::setRenderHint: Painter must be active to set rendering hints
Xlib:  extension "NV-GLX" missing on display ":0.0".
Xlib:  extension "NV-GLX" missing on display ":0.0".
terminate called after throwing an instance of 'std::system_error'
  what():  Invalid argument
Aborted

I don't know if this is related but it's the only dolphin log i can find.

but i don't understand why in the beginning is was working fine and now the game wouldn't start anymore cause i id not change anything.

Or maybe kodi doesn't like this way of starting games with dolphin....

I hope you can point me in the right way.

btw i already tried advanced laucnher but with this i have also the same issue.

First couple of times game starting fine and later nothing.

Thanks!

Display More

Well this is a somewhat awkward setup but normally every start script is self contained so it should be possible to run them from any terminal or other launcher. Dolphin probably fails to run because the audio backend is misconfigured. Try to set either PulseAudio or ALSA in advanced.conf and leave the audio backend configuration in Dolphin untouched.

Dolphin Emulator on Arch Linux crashes when launching a game

Quote from Drarkklain

is there a way to permanently disable the demo games in all frontends?

Not in all so they will be always listed in Retroarch but I'll add some config flags to advanced.conf in my next builds to disable them for ES & PF if you don't want or need them.

Quote from bigboo

Linux 4.20.1 Kernel Released With Various Fixes - Phoronix

"alsa fixes"

LE ditched kernel 4.20 in favor of 5.0 linux (RPi/Generic): update to linux-4.20 by MilhouseVH · Pull Request #3087 · LibreELEC/LibreELEC.tv · GitHub so I'll do the same.

Quote from Marciano

thanks i tried that but nothing happends

Because you need to apply a rom afterwards. This cli script has no interface so starts the rom directly if one is available. There is a reason why stuff like ES has been invented.

Quote from Marciano

Thanks but what command to use in CLI

<command>/usr/bin/m64p-cli.start %ROM%</command>

Quote from Marciano

how to use this in CLI?

Is this for setting up mupen64plus standalone in CLI gui?

If yes how to start this?

It's the command line for es_systems.cfg