LibreELEC-RR 9.x [ Emulationstation | Retroarch | Pegasus | DolphinQT | Moonlight | Chrome | Spotify ]

  • Gosh thank you so much for this. Yesterday I spent hours for creating that damn map file with Knoppix and just failed. It was so frustrating.

    In PCSX2 my controller works. Its only about PPSSPP.

    Do you mean PS1 games by saying advanced emulated 3D games? I know that PCSX_Rearmed has lower requirements than beetle hw but since PCSX_Rearmed hat this stupid restart bug that makes it impossible to play my multidisk games I really hoped being able to use beetle with this new setup. However I atleast need internal resolution x4 or x8 in beetle to contest with graphics from PCSX_Rearmed. I'll ask reddit if someone has an idea why it is so slow.

    Ye I already read that. However I have no clue about cpus or hardware in general. I couldnt distinguish a toaster from a nasa pc.

    So the settings in pcsx2 in your build are already the lowest possible? I thought ps2 graphics are comparable with dolphins and dolphin runs fluent. I also looked for minimal settings but often they use other plugins or change options that are grayed out in my settings. Whatever I will try to find a solution.

    I highly doubt that you will need 4x to 8x times of the internal resolution to match PCSX reARMed which uses 320x240 as default.... Sony - PlayStation (PCSX ReARMed) - Libretro Docs so we're talking about 1280x960 up to 2560x1920 which is basically somewhat over HD and exceeds WHQD. If you want to run 25 year old games inalmost 4k on a NUC you have to get something like this NUC8I7HVK and spent roughly 900€ just for the barebone system.

    Same goes for PCSX2 if you can't run it fluent at the base resolution your CPU is to slow. It doesn't matter if you can run Gamecube/Wii games because that system used an entirely different architecture to run games. Unless you get a NUC with at least a very recent i3 or better i5 chances are low to proper emulate all games and systems.

    Btw. do you use Beetle-PSX or Beetle-PSX HW. At default the system runs Beetle-PSX and you have to change es_systems.cfg to run the hw accelerated core.

  • I highly doubt that you will need 4x to 8x times of the internal resolution to match PCSX reARMed which uses 320x240 as default.... Sony - PlayStation (PCSX ReARMed) - Libretro Docs so we're talking about 1280x960 up to 2560x1920 which is basically somewhat over HD and exceeds WHQD. If you want to run 25 year old games inalmost 4k on a NUC you have to get something like this NUC8I7HVK and spent roughly 900€ just for the barebone system.

    Same goes for PCSX2 if you can't run it fluent at the base resolution your CPU is to slow. It doesn't matter if you can run Gamecube/Wii games because that system used an entirely different architecture to run games. Unless you get a NUC with at least a very recent i3 or better i5 chances are low to proper emulate all games and systems.

    Btw. do you use Beetle-PSX or Beetle-PSX HW. At default the system runs Beetle-PSX and you have to change es_systems.cfg to run the hw accelerated core.

    I dont want to play them in 4k -_- I just want atleast the same video quality like before on my AML S905X box. I tested both Beetle PSX and Beetle PSX HW. I dont know why it looks so bad but you have seen the screenshot didnt you? It looks much better on my AML S905X box. And the only way I got the same result was by increasing the internal resolution.

    Its all weird. I just changed a few settings and couldnt start the core anymore (it stucked in blackscreen). So I restored my old config file and now I again cant start any cores. It brings me back to kodi main menu. Is it because fullscreen mode? First it was disabled and starting cores worked. Then I tried to enable it but no success I always ended up in kodi after changing it. After restoring my old config file fullscreen mode is enabled but I also end up in kodi after starting a core.

    And by the way I need 3 attempts to open Retroarch in 1080p because it changes to 2160p all the time. Also ES sometimes start in small size (same like ppsspp).

    And what is wrong with those logfiles? I activate debug logging start retroarch to reproduce my issue and all I get is what happened after closing retroarch.

    Thats so frustrating.. bought this NUC für 190 euros (incl. ssd and memory) and it cant even emulate my ps1 roms like my 40 euro S905X box did.

  • t want to play them in 4k -_- I just want atleast the same video quality like before on my AML S905X box. I tested both Beetle PSX and Beetle PSX HW. I dont know why it looks so bad but you have seen the screenshot didnt you? It looks much better on my AML S905X box. And the only way I got the same result was by increasing the internal resolution.

    You want to increase the resolution by 4 to 8 times so. I already did the math for you :rolleyes: I don't see how your S905X box has better graphics than mine because I'm not able to increase the resolution in my builds. I have no clue which build or image you used before on your S905X or what specifc version of PCSX reARMed that had superior graphics.

    Its all weird. I just changed a few settings and couldnt start the core anymore (it stucked in blackscreen). So I restored my old config file and now I again cant start any cores. It brings me back to kodi main menu. Is it because fullscreen mode? First it was disabled and starting cores worked. Then I tried to enable it but no success I always ended up in kodi after changing it. After restoring my old config file fullscreen mode is enabled but I also end up in kodi after starting a core.

    What settings? What old config?

    And by the way I need 3 attempts to open Retroarch in 1080p because it changes to 2160p all the time. Also ES sometimes start in small size (same like ppsspp).

    ES should always use the xrand resolution so 2160p or else. What is "in small size"? PPSSPP should start in fullscreen if it is set to fullscreen.

    And what is wrong with those logfiles? I activate debug logging start retroarch to reproduce my issue and all I get is what happened after closing retroarch.

    Are you kidding me? Have you read any of my posts at the beginning of this thread?!

    Does this link https://paste.ubuntu.com/p/qxfxds5nxn/ look like an zip file or any emulation related file to you or anyone else?! You've uploaded a Kodi logfile while Retroarch does not work? I really thought user are able to distinguish between "oh crap my Kodi is broken, lets get some Kodi logfiles" and "oh crap my Retroarch is broken, lets get some Retroarch logfiles"

    You think it's frustrating? Sorry but from my perspective you've just clicked the download link, installed an image and expect this to be a free out-of-the-box-tl:dr solution. I've spent ages to get things together and you're not in mood to read the FAQ or anything else of this stuff? And you still expect me to iron out your problems? Congratz!:thumbup:

  • You want to increase the resolution by 4 to 8 times so. I already did the math for you :rolleyes: I don't see how your S905X box has better graphics than mine because I'm not able to increase the resolution in my builds. I have no clue which build or image you used before on your S905X or what specifc version of PCSX reARMed that had superior graphics.

    You act like it was my aim to play on 4k. Its not! My aim is just to play with my old graphics and increasing the resolution was the only thing what came to my mind. However if you have an idea how to bring my old graphics back without increasing the resolution let me know. Thats actually the reason why Im here. On my S905X box I used the retroarch files from MXQProject.

    What settings? What old config?

    I just compared the settings in your retroarch version with the retroarch version of my old S905X box. I changed settings like fullscreen mode, refresh rate, width, height, video in seperate thread, GPU and CPU sync, graphics filter. I turned them on and off depending how it was on my old build. And no I have no clue what I did there I just tried it out. Because thats what noobs are doing. Anyway it didnt work and I stucked in blackscreen after starting a core. So I restored the config file with default settings from your build. However the cores didnt start aswell. But that already was the case when I installed your build. Then a bit later it worked but no clue why. Thats what I mean everything looks so random to me. Now it works then it didnt work anymore and I have no clue what has changed. Same with resolution. Sometimes its 1080p then its 2160p again and I dont know why. And I noticed that when Retroarch worked fullscreen mode was disabled. At the beginning and now where I've restored that config file its enabled again and Retroarch didnt work again. So my thought was that it is because of the fullscreen mode.

    ES should always use the xrand resolution so 2160p or else. What is "in small size"? PPSSPP should start in fullscreen if it is set to fullscreen.

    Yes it does. However as you know at the beginning it is not set to fullscreen mode and then PPSSPP is shrinked in that corner. And with ES its the same. It was just a description how ES sometimes looks like. However after restarting ES once or twice its fullscreen again. But again.. so random. I just tell you all those things because it doesnt seem normal to me and I hoped that there is a reason why all this happens and maybe there is a way to fix this.

    Are you kidding me? Have you read any of my posts at the beginning of this thread?!

    Dude. You already quoted it. Not that one what you've marked but the text below: enable debug logging, reboot, reproduce, upload. Thats exactly what I did. Why are you yelling at me.

    Does this link https://paste.ubuntu.com/p/qxfxds5nxn/ look like an zip file or any emulation related file to you or anyone else?! You've uploaded a Kodi logfile while Retroarch does not work? I really thought user are able to distinguish between "oh crap my Kodi is broken, lets get some Kodi logfiles" and "oh crap my Retroarch is broken, lets get some Retroarch logfiles"

    What shall I say on my old S905X box everything was in that kodi logfile. Also the retroarch part. And I never needed any other files. Just tell me the name of the file you need. Everything you mentioned in your FAQ is that its reachable via samba and that its placed in folder logfiles.

    You think it's frustrating? Sorry but from my perspective you've just clicked the download link, installed an image and expect this to be a free out-of-the-box-tl:dr solution. I've spent ages to get things together and you're not in mood to read the FAQ or anything else of this stuff? And you still expect me to iron out your problems? Congratz! :thumbup:

    Stop always telling me that I didnt read your FAQ thats just not true. Maybe I misunderstand much of it but I read it.

  • Hey just updated on my pc with radeon card and now m64plus is working great, exept one thing:

    The screen is stretched to 16/9 on my TV instead of correct 4/3.

    I checked the ini, the default is this:

    [Video-GLideN64]

    # Settings version. Don't touch it.

    configVersion = 24

    # Enable/Disable MultiSampling (0=off, 2,4,8,16=quality)

    MultiSampling = 0

    # Enable/Disable Fast Approximate Anti-Aliasing FXAA

    FXAA = False

    # Screen aspect ratio (0=stretch, 1=force 4:3, 2=force 16:9, 3=adjust)

    AspectRatio = 1

    What can I do?

  • 5schatten

    Quote

    Since you used MakeMKV in the past is it still functional? If so can you give us a brief summary what else you do to use it beside installing the addon & updating KEYDB.cfg? dainara tried to use it & ran into some problems so maybe you both have some advice for us.

    I tested the makemkv addon again on libreelec rr and it still works, all though the disk menu doesn't seem to work.

    the keydb.cfg is not needed when you use makemkv.

    I didn't test it on your latest release though.

    And i still think that the suggestions i mentioned should be implanted:

    1e when you install this addon you should know that it is necessary to start the add on through the add on menu to update/install the key!

    This should IMHO be included in the installation method.

    2e updating the makemkv key should be automatic when you start libreelec, Key must be updated once a month so it would be nice to take care of that automatically so the average user does not have to think about it anymore.

    You said make a cron job or start the addon with a startup script , while this is no problem for me, it will be for a average user

    So the installation routine would be like this:

    Start librelec rr

    Click on add ons in the left menu.

    In the upper left corner click on the box icon.

    Choose install from zipfile.

    Browse to where you put the makemkv zip file (this could be usb drive, harddisk or network drive)

    Wait for it to install.

    Start the add on at least once to update/install the key! (Click on Add ons in the left menu, and click on makemkv. popup will inform you)

    Reboot

    Insert a blu-ray disc and try through the disc menu.

    If that doesn't work (It won't work on kodi 17.6) click on video/files and select the line with your blu-ray and click play if you have a remote, otherwise right click on that item and choose play. Do not use enter or ok on your remote, it won't work.

    After this, if it works, there will be a list of found titles on the disc, usually only one but it can be multiple ones. if multiple choose the title with 800 in the title, if not try the other ones

    I hope this will help:)

  • im blanking hard, was WHDLoading in Amiberry ever solved some time back or?i decided to give up on my A500 till i can afford to repair the thing (it needs so much work i imho think im better off selling it and getting something like an A1200) and setup my older Pi3B (not the +) w/ RR, for Amiberry and WHDloading when possible over Floppy ADF Loading,

  • If I would rework the MakeMKV Addons this way you would lose the ability to use your own key you've paid for or I had to create an Addon setting management something just for this purpose and honestly this has no high priority for me. You either can update the key once in a while or buy one and enter it to the config file :/

    im blanking hard, was WHDLoading in Amiberry ever solved some time back or?i decided to give up on my A500 till i can afford to repair the thing (it needs so much work i imho think im better off selling it and getting something like an A1200) and setup my older Pi3B (not the +) w/ RR, for Amiberry and WHDloading when possible over Floppy ADF Loading,

    Well I wasn't aware that WHDLoad was broken in Amiberry in any build for me. If you have valid Kickstarts and roms in proper WHDLoad format it works in all builds /shrug

    I've set all of my tv's to a PC input mode and let my HTPC handle the screen format. My N64 games are displayed in 4:3 or 16:9 depending on what I set in mupen64plus.cfg so if you've set it to forced 4:3 and it's still 16:9 your tv probably changed the aspect ratio :/

  • Well from my pov you ask a lot of question that would have been answered in FAQs or Wikis of the emulator in question. So I have the impression you don't read them... also you don't follow basic steps like providing full sets of log files & if you think you did not understand something then ask first. I mean there is a complete how to available Provide Log File [LibreELEC.wiki] and still you deny to upload it. Personally I don't care if you have some fancy porn addons or anything else installed which might leave some notes in the log too as long as you don't expect support for them /shrug:D

    Anyway you have to deal with the psx situation for now until beetle-psx get's a Dynarec Dynamic recompiler [$895] [BOUNTY] · Issue #214 · libretro/beetle-psx-libretro · GitHub which is already included in PCSX reARMed since a while.

    If you restore old config files of an ancient Retroarch ARM build on a recent Generic build you should not expect it to run. I guess it should be obvious that quite a lot of settings are not updated or just invalid.

    About the resolution hazzle... well I use no 4k screens so I can't test this. But since Generic builds come with xserver it should not matter since the underlaying window system works for lower resolutions too. PPSSPP failed to switch to fullscreen in the past because it wasn't enabled at default but was fixed a while ago.

  • Well from my pov you ask a lot of question that would have been answered in FAQs or Wikis of the emulator in question. So I have the impression you don't read them... also you don't follow basic steps like providing full sets of log files & if you think you did not understand something then ask first. I mean there is a complete how to available Provide Log File [LibreELEC.wiki] and still you deny to upload it. Personally I don't care if you have some fancy porn addons or anything else installed which might leave some notes in the log too as long as you don't expect support for them /shrug:D

    No I dont use those addons. Here is the full zip file from 4 days ago. It actually should show how Im starting Retroarch and resolution changes automatically between 1080p and 2160p. Maybe it also shows that ES is shrinked to the corner and gets normal after some further tries. And it should also show that Retroarch on 2160p crashs if I start a game. However its already a few days ago and I dont know exactly what I tried to record. You dont have to look at it you can also wait until Im able to create a new logfile (I gave my NUC back for a few days).

    Anyway you have to deal with the psx situation for now until beetle-psx get's a Dynarec Dynamic recompiler [$895] [BOUNTY] · Issue #214 · libretro/beetle-psx-libretro · GitHub which is already included in PCSX reARMed since a while.

    Thank you, looks interesting.

    If you restore old config files of an ancient Retroarch ARM build on a recent Generic build you should not expect it to run. I guess it should be obvious that quite a lot of settings are not updated or just invalid.

    No, I didnt use the config file of my AML box for the NUC. I just wrote down what video options on my AML box were turned on/off and tested them for my NUC. However I stucked in black screen when I started a game and wasnt able to reverse the settings. So I restored the config file of your build that I've saved straight after installation. However with the default settings Retroarch always closed if I started a game. And I noticed that the enabled fullscreen mode could be the reason for that. Because when I started Retroarch on your build for the first time it already didnt work. After some time it suddenly worked. I had no clue why. When I compared the settings from my AML box and the NUC I noticed that fullscreen mode on my NUC is disabled. I couldnt enable it in Retroarch for some reason so I changed it in the config file and then Retroarch didnt work anymore. By disabling it Retroarch started working again.

    About the resolution hazzle... well I use no 4k screens so I can't test this. But since Generic builds come with xserver it should not matter since the underlaying window system works for lower resolutions too. PPSSPP failed to switch to fullscreen in the past because it wasn't enabled at default but was fixed a while ago.

    Maybe the log files above can explain something.


    Another question: I was thinking about giving my NUC back and spend 50 euros more for a small upgrade (NUC7PJYH with an Intel Pentium J5005 chip). However that probably wouldnt change much, would it? Because - I dont know if its up to date - I have read that pcsx2 and ppsspp dont support quad cores.

    And a request: Yesterday I tried to backup my savegame from a wii game. However I noticed that it is a bit complicated since savegames and other user files like screenshots get stored in /var/share/dolphin-emu ... or was it /storage/.local/share/dolphin.. something like that, sorry cant check anymore. Anyways since its only accessable by using ssh I wondered if you could change that path somehow maybe to the config file folder or something like that. It was even better if I could change the savegame path to my sd card. I tried this command:

    Code
    /path/to/dolphin/build/dolphin-emu -u /path/to/user/directory

    shown here but it didnt work. Putty said something like permission denied..

    Ah and I have 4gb memory. Is that to little? Because when I enabled debug logging a few days ago it showed my something like 320487/350948

    Edited once, last by Kupo91 (January 28, 2019 at 4:21 PM).

  • Quote

    If I would rework the MakeMKV Addons this way you would lose the ability to use your own key you've paid for or I had to create an Addon setting management something just for this purpose and honestly this has no high priority for me. You either can update the key once in a while or buy one and enter it to the config file :/

    I understand that, but for the average jane/john doe it is necessary to know how it works, so at least add this info to the download section or howto.

    That way it is clear how it works.

    Point is that if you install the addon it simply won't work right away, witch could lead to frustration.. (i found out how it works by reading the code)

    I agree that "Addon setting management" would be necessary to for full all possible needs and i do understand that it is no priority for you, but it may have priority to your users. It is just a thought.