Posts by Cael

    haven't been ontop of things but updated recently, that pesky Time sync problem seems to be gone for damn good!

    but i don't know if this is a RetroArch thing or not while it DOES have an Auto config for an OG Xbox controller, it's all sorts of messed up, (connected over a handmade connector cable)

    attaching a Config that Adheres to Xinput mappings (X is X on Gamepad, A is A etc) but in Cores? the functionality isn't duplicated, but the button naming IS , like for D Pad up and Down its listing as HAT # 0 Up HAT # 0 Down but, it shows Key Up for both, you haveto assign manually per Core via the function Icon rather than Name.

    (i know this is Niche-case not many are going to go mutilate a spare Breakaway cable to make this or spend 10$ on a cable just to use a OG Xbox S / Duke controller, and i'm only trying it out as i had to get a replacement for my OG Xbox's controller)

    Microsoft X-Box pad v1 (US).zip

    In Retroarch I am unable to download cores and there are no cores preinstalled either. How am I able to download them?

    is this the recent build he posted at my request? (edit tested on my Pi4, the only thing that indeed doesnt work is "Download a core" (which understandably wont work, No Pi4 cores reside yet on the libretro buildbot server, thus if you could, no core you downloaded or overwrote would launch)

    if you are using the 10/17/19 build, go hit the Releases , a new build was posted at my request to MagicSeb (again thankyou MagicSeb i still cant get a new VM up n running, a problem i'll haveto face when im back home X_X)

    if you ask me Raspbian Buster which is the core to base Lakka/LibreELEC for the 4, needs more time to mature. theres alot of Issues for video playback under it with its default WM. (ones i get even under Lakka) the Pi4 has felt Rushed and so much atm is showing how rushed it was.

    Do I have to install it by writing directly to the sd card or is it possible to update an existing installation by throwing your image into the .update folder?

    just like any LibreElec version except vanilla, you update by tossing either the .img or .tar into the Update foldervia network or on-device over a USB storage etc. i would say much like with 5schatten 's builds for the 2 and 3, w/ first time updating, flash the .img to the SD card rather than trying to update from vanilla "Lakka" , after that as above, is all good n golden to toss either archive into the Update folder.

    however if you start compiling updates yourself. big ones start from scratch (make clean & PROJECT=RPi DEVICE=RPi4 ARCH=arm make image ) initial/from scratch builds will take along time on older hardware/limited VM's so beware of that (on my System an AMD FX 8320E 16GB Ram, with a VM given only half that and a 120GB HDD Image. times are in the ballpark of 7 HOURS for a fresh image, significantly less when its a small update.

    gonna go out of the limb Escalade, your users are likely primarily PC Users (reguardless the manufacture,) so if thats what users want for x86_64 generic platforms, fine let em choose which they want. but 5schatten builds target not just the average PC but various SBC's as well, if he so called had to switch to full wayland (and do honestly correct me if im wrong on this), thats shooting out a likely large chunk of those who choose to use his builds. Personally i perfeer RR on my Pi 2 3 and 3B+ while i use Magicseb's for the 4 untill everything eventually smooths out for the 4.

    just my two cents *shrug*

    Standalone Windows version for RPCS3, i can tell you i had no issues w/ my AMD FX 8320E CPU/ GTX 760 OC (before it died, but i had alot of studders while it built shader caches.) and even better performance w/ my newly installed GTX 1650. i'd put the bar sadly for acceptable performance however atleast a 900 GTX Series GPU for Nvidia, cant say for AMD.. all my AMD GPU's are old AF.(Radeon HD5750 is the newest i got)

    You can also build the images on Ubuntu 18.04 I updated last week for Generic and RPI. S905 did not build though build errors Im guessing this is down to the updates to linux ?

    if you mean about my comment about manually updating" then its not that they haveto be built, but that you haveto place the nightlies down on the Update folder n reboot, cant use the update function in the LibreElec Program App,

    4 hours in No crashes. BUT one problem Has regressed, Wifi refuses to work ("Input/output Error") but the fact we've narrowed it down to either it's the later firmware OR its the newer Kernel, gives a huge leap to fixing the real issue. (and even helps make your image more stable and Lakka even better,)

    i finally captured lastnight a Kernel Panic (Deadlock) after 2hrs30Mins of playing a SNES game and usally when idle or playing for about that long if i exit to Kodi and reboot its good. and i Haveto if it just Quits-to-Kodi (becomes verry crash/Kodi-restart Prone if i dont) i had this morning as i passed out w/ a game running, and Kodi Rebooting caused a similar Kernel panic (was first time it's failed to properly reboot)

    Here's the one from RetroArch crashing:

    and the one from Kodi:

    i have copy over the cores from your current build to raspbian-buster and they seems to work well there for i think it`s not a problem with the cores it self

    it sgotta be something that RetroArch is doing once a core is loaded and running. atleast within LibreElec. what Device model are you using? (1GB 2GB or 4GB?) if we can get a testing sample size and see if its locked to a particular Ram variant, we might find out whats causing these OutOf Memory/Deadlock Kernel panics

    MagicSeb retroarch is causing the issues doesnt look like it's the cores directly had Snes9x 2010 and Gambette (pokemon rando's) at the same time, 2 to 2nahalf hour crashes. my guess is RetroArch is slowly leaking. what Pi4 Models do you have? and/or can you get anyone to test w/ reducing system ram in config.txt if it solves it?
    (cause if this base OS image libreelec is using is the 64bit kernel, this might explain it.. the raspberry pi development team have stated the 64bit kernel is a WiP and breaks/becomes unstable on the 4GB model when more than 1GB Ram is enabled.

    well as the issue now branches out from just derping on the format of the templates, to package build Fail, now im completly stumped,

    unless it's because theres no development libs for SDL2, im not sure but, in the attempt to make Devilution build as a package, it gets so close then PFFT. fails on what seems to be a static linked lib that handles the networking. output.txt

    this *DOES* compile fine in Raspbian