Posts by 5schatten

    Download this dc541e5.zip then extract it and copy the resources folder to /storage/.config/emulationstation/ or use the Windows Explorer and type in \\enter-htpc-name\Configfiles\emulationstation and copy it this way.

    Looks like a folder with vital files is missing.

    BlaBla1973

    Use the windows network or SMB or whatever to enter \\yourdevice\Configfiles\emulationstation\resources and check if there is a file called opensans_hebrew_condensed_regular.ttf anyway I have no clue what's wrong with ES since it says it can't find a appropriate font face...

    When I start ES in debug mode so terminal and run phoenix:~ # emulationstation --debug it tells me this:

    Code
    lvl2:     EmulationStation - v2.8.0rp-dev, built Sep 19 2018 - 09:01:25
    lvl2:     Parsing XML file "/storage/.emulationstation/resources/mamenames.xml"...
    lvl2:     Creating surface...
    lvl2:     Created window successfully.

    So I suspect ES tries to read the file mamenames.xml but fails. Since you've updated from a really old build it's possible that something screwed up because I've switched Emulationstation to Emulationstation-Retropie.

    Run cd ~ && ls -l -a | paste and afterwards cd ~/.config/emulationstation/resources && ls -l -a |paste in a terminal and post your links. So I can see if the links to the ES folders are there and if all files are in the directory.

    LeapOfFaith

    Well what are you trying to do? ES is just a frontend and starts the games, mostly libretro cores, as you like. If you want to run Retroarch in "nokms" mode all the time you have run touch /storage/.config/retroarch/nokms in a terminal as described in the FAQ.

    Hi there

    Long time Kodi user but only now looking at the emulator side of things.

    Tried to install the Escalade build but it won't start any games for me.

    Was trying to install this build as it seems more up to date, but get a "failed to start xorg server" error.

    Using an Nvidia GT520 (admittedly quite old), maybe it's not supported anymore?

    Any help would be appreciated, thanks!

    My build comes with a xf86-video-nvidia-legacy driver v340.107 that should support your card.

    Quote

    GeForce 500 Series:

    GeForce GTX 590, GeForce GTX 580, GeForce GTX 570, GeForce GTX 560 Ti, GeForce GTX 560 SE, GeForce GTX 560, GeForce GTX 555, GeForce GTX 550 Ti, GeForce GT 545, GeForce GT 530, GeForce GT 520, GeForce 510

    Post your logfiles and maybe we figure out what's wrong.

    Hi there.

    I really love this release. I've actually wanted this for a long time, but now I know it exists. It did take some tinkering to get the sound to work, but now I am all god.

    I do experience some stuttering on gamecube and ps1 games, which I honestly think should not be there. I am running the generic x86 build on my NUC I5, 7th. gen. Gamecube and PSX one games seem to run at 100% speed, but sometime it stutters. I would be more inclined to accept a general slow perfomance as an indicator for my pc not being fast enough. Can anyone explain or help with optimizing tips.

    Can you run dmesg | paste in a terminal & post the link? What do you use to run GC or PSX games? Dolphin? Libretro-dolphin? Beetle-PSX or PCSX_rearmed?

    I probably should explain why I wanted access to the autoconfig folder:

    My controller was not set up automatically in retroarch after configuring in ES. In retropie this is done automatically I believe? It's been a while since I set that up so could be wrong. I had a look in my retroarch config folder on my RP install and copied the files out of there into autoconfig on LE which I thought would work however the retroarch.cfg points somewhere else...

    Now I tried setting up the controller in retroarch and it places the config file in autoconfig/udev which doesnt seem right to me but it works anyway.

    Another thing, in ES my shoulder buttons normally page up and down on the games lists however in this version not so?

    What kind of controller do you use? Can you enter sdl-jstest -l | paste in a terminal when the controller is connected and post the link?

    Do you stream the video over your network? Well maybe it's samba related :/

    ERROR: Read - Error( -1, 103, Software caused connection abort )

    Beta 05 comes with Kodi 18 beta 02 so I guess it's related to these changes.

    Hi,

    Afther the update to : LibreELEC-Generic.x86_64-9.0-RR-201837-024c078-Beta06.tar my emulationstation stops working.

    Here are some logs :

    and this one :

    Code
    lvl0:     Error - File type unknown!
    Segmentation fault

    Have you added new games...? Since it looks like Emulationstation fails to read a irregular file name:

    lvl0: Could not find appropriate font face for character 32 for font :/opensans_hebrew_condensed_regular.ttf

    I've made no changes to ES in the last versions...

    Whats inside this directory? \\yourdevice\Configfiles\emulationstation\resources

    Does ES work if you downgrade to Beta 05?

    • Intel (i915) using VAAPI on Linux 4.18+

    what is intel i915? what cpu:s from intel will support the new LE10(kodi 19)?

    i915 is just the name of the Intel IGP driver which is integrated into the Linux kernel.

    Since Intel offers more or less reliable open source driver support and their IGPs support basically all media formats you can choose whatever you like as long as the Linux kernel features this CPU too.

    Also check out this https://en.wikipedia.org/wiki/intel_quick_sync_video#hardware_decoding_and_encoding

    Anyway ask again next year or whenever you're going to upgrade because the future is unclear and AMD is a strong competitor (again)

    It's nVidia's responsibility to support Linux standards; not our responsibility to re-engineer our entire distro to support nVidia.

    Probably right but still a problem for the Nvidia user base, even if it's small. But what about AMD? I've read UVD relies on VDPAU too? Maybe it's outdated https://en.wikipedia.org/wiki/unified_video_decoder#linux https://trac.ffmpeg.org/wiki/hardware/vaapi but will AMD fully support VAAPI then?

    Kodi 19 will probably ditch VDPAU support in favor or VAAPI. Nvidia does not support VAAPI so there will no more Nvidia support in the future. LE10 will be based on Kodi 19 so it will also drop Nvidia support.

    You can savely upgrade to LE9 since it still supports VDPAU and Nvidia. It is possible that LE9 handles VC-1 HW decoding properly because it uses newer software libraries and newer drivers for your AMD card. So try the new builds and see if anything improves.

    If you don't mind software decoding and probably higher cpu load then stick to LE8.2.5 and you will be also fine.

    Sorry to ask,dont follow, why will it stop? will there be no support(VDPAU) for Nvidia cards with LibreELEC 10?

    Development Update – LibreELEC

    https://en.wikipedia.org/wiki/vdpau

    https://en.wikipedia.org/wiki/nvidia_nvdec

    It's basically all about the open source software philosophy. Nvidias open source software solution VDPAU is superseded by proprietary NVDEC which relies on proprietary Nvidia drivers and because that's not a wide supported standard like VAAPI they punish Nvidia users for buying this kind of hardware./shrug

    So in the end either oss developers have more work to integrate and maintain a special Nvidia only software decoder or otherwise Nvidia has to change his open source policy and release some suitable open source drivers. As both is unlikely you better think about a hardware upgrade. Intel or AMD offer a lot of suitable low power CPU that work very well in a HTPC.

    Beside that... you own this card? HD7770-2GD5 | Grafikkarten | ASUS Deutschland if you do then VC-1 should be supported by UVD but for linux still vdpau is used to decode this type of media. https://en.wikipedia.org/wiki/unified_video_decoder#linux

    I've checked the mesa-vdpau libs & LE 9.0 comes with all needed libs so try LibreELEC (Leia) v8.90.005 ALPHA – LibreELEC this new Alpha build and check if your card is working.

    I only load the default config files at WHDLoad because otherwise the resolution / or the image could be wrong placed. But everyone has to adjust the default files for their needs if it comes to resolution and stuff, they are just "templates" with working, but might imperfect working settings. For the games itself the default configs only apply if you load any game beside WHDLoad.

    For WHDLoad itself amiberry looks for game specific settings in the whdload_db.xml WHDLoad Auto booting · midwan/amiberry Wiki · GitHub so if you want to run a game with diffrent settings you have to change the whdboot/hostprefs.conf but thats something you have to adjust for yourself because that's highly individual. I guess the Amiberry wiki is quite good for a start.

    I guess you can correct the edges of your tv in your tv settings look for geometry settings since these can correct image flaws. Google for "crt geometry corner convergence" I guess this could be handy.

    The HDMI line only applies if you have a TV in CEA mode that does not run at 50Hz. How long do you wait for the game to start? If you have no patches for the game I guess it's normal to see failed patches or something like "set patch failed". It takes about one minute to boot Willy here and about 1:30 if you start it the first time on a RPi 3B and so it should take the same time at your system.

    Do you have these files (symlinks) in your ~/.config/amiberry/whdboot/save-data/Kickstarts directory?

    Code
    raspi3:~/.config/amiberry/whdboot/save-data/Kickstarts # ls
    foo.txt          kick34005.A500   kick39106.A1200  kick40068.A1200
    kick33180.A500   kick37175.A500   kick40063.A600   kick40068.A4000

    And ~/roms/bios/Kickstarts looks like this?

    Code
    raspi3:~/roms/bios/Kickstarts # ls
    kick33180.A500.rom   kick37175.A500.rom   kick40068.A1200.rom
    kick34005.A500.rom   kick39106.A1200.rom  kick40068.A4000.rom

    Works for me on two RPi 3 systems by the way /shrug

    Well if you've updated to Beta06 there is always a log file because the start script will always log what kind of game you're trying to boot, what kind of Config is loaded and stuff. But of course you have to start your system, run amiberry and then look for the log file, if you restart and look for a log you have to run amiberry again.

    Starting "Adventures Of Willy Beamish" should look like this:

    Code
    Kodi already frozen, nothing to do.
    Powering on HDMI with explicit settings (CEA mode 19)
    Trying to boot this game: /storage/roms/amiga/Testing/WHDLoad/Adventures Of Willy Beamish.lha
    Loading a WHDLoad (.lha) file...
    Loading Amiga 500 config.

    Cael

    Change to your Amiberry directory and clean up all files in whdload/save-games so basically delete all files that have s similar name as a game and also delete the files located in whdload/save-games/kickstart

    Also post the amiberry.log located in /var/log

    The problem is that Amiberry creates several files and won't update them. So if you change something like paths or configs it will screw things up. Shouldn't happen again in the future but unfortunately can happen because I reworked the whole start and config stuff.

    I've tested Willy Beamish lha and Syndicate as zip so it should work. I once had a bootloop because I renamed the Kickstarts but the symlinks pointed to the old files so I guess that's your problem too.

    I am used to arch/debian, and don't trust much outside such well known repo's.

    But I guess I can create a vm and run the installer from inside there.

    So basically you don't trust this project enough to run an "USB stick" creator binary that is restricted/limited by the user rights of your account but you want to run the distribution on a dedicated system were it has full control over your hardware? :/

    Btw you use arch? Hopefully without aur? Anyway since you already found the image... Otherwise I would suggest this Compile [LibreELEC.wiki] so you could inspect/audit the whole code before your compile and install it. /shrug

    Beta 06 is online:

    • updated to latest LE9.0 upstream
    • updated generic kernel to 4.18.8
    • updated Samba to v4.9.0
    • updated nano to v3.0
    • updated xf86-video-amdgpu / xf86-video-ati to v18.1.0
    • updated xf86-video-intel to git 25c9a2f
    • added workaround for libretro-mame2016 -> added libretro-database to scrape games
    • reworked fs-uae start scripts & configuration -> read the FAQ
    • added fs-uae support for Interchangeable Preservation Format (.ipf) -> delete your es_systems.cfg before you update