Posts by 5schatten

escalade

I guess this commit is also important then since cat /run/libreelec/xorg-settings.conf fails to find i915 on Atom/Celeron systems?

retroarch: default to kms if xorg uses modesetting driver · escalade/LibreELEC.tv@54fc379 · GitHub

So test for i915 (i3 and above) and run in KMS mode if no nokms file is found

Test Xorg.log for kms (Atom/Celeron) and run in KMS mode if no nokms file is found

-> is that what it shoudl actually do? Because the latter didn't work for me.

i3-6100

Xorg.0.log

[ 7.423] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20180308

retroarch.log

[INFO] [GL]: Found GL context: kms

j3455

Xorg.0.log

[ 15.006] (II) modesetting: Driver for Modesetting Kernel Drivers: kms

retroarch.log

[INFO] [GL]: Found GL context: x

The i3 KMS detection works fine and the j3455 uses the modesetting driver as intented but still starts RA with x context.

If I change -o to | | it works. I guess it's intended to be an or. Isn't it?

if grep -q i915 /run/libreelec/xorg-settings.conf || grep -q kms /var/log/Xorg.0.log && [ ! -f /storage/.config/retroarch/nokms ]; then

I compiled the HW variant and it got distorted video output right out of the box so I guess it starts with opengl/vulkan context if it's available & not disabled at least thats what the RA log stated.

Some work some don't but you're right it's not a reliable way to determine if something is messed up.

Yes I've read something about that, also he tried my RA binary before you've updated to the latest version.

Anyway thx for your help -> much appreciated!

psrkallez06

What kind of CPU is installed in your notebook?

Well I did some testing. RA runs at "full speed" so 59,99 -> ~60Hz on my i3 system but reaches only 56,xxHz as long as KMS is enabled. Also my RPi runs at about 60Hz so I guess there is a link between KMS and some Intel driver stuff at the low-end Intel systems. Once KMS is disabled the j3455 runs at full speed too.

It's not really a core related problem, once RA runs at full speed the core will too. Well as long as the system can handle the core.

Well this did indeed the trick:

xorg-server: use modesetting for atom/celeron grade gpu's · escalade/LibreELEC.tv@d9c63e8 · GitHub

Quote from psrkallez06

Oh nice! Btw i used PSX Rearmed when i tried it on LE8, that worked the smoothest, but Beetle worked to, except HW since it just crashes Retroarch.

Sure about that? AFAIK pcsx_rearmed is used for arm systems like the RPi and I use it for them too. But maybe lakka builds it for generic too. Anyway watch this video to understand why you can't just exchange some programs

Right now I'm buidling the same core lakka / gamestarter uses to ensure it's not a core problem.

package.mk

Update you RA cores and try to grab "mednafen_psx_hw_libretro.so" because my build ships with "mednafen_psx_libretro.so"

I guess LE8+Gamestarter runs faster because it uses another core / build option. Same goes for escalades build both build the mednafen_psx_hw_libretro core.

https://github.com/bite-your-idols/gamestarter/tree/master/packages/libretro-cores-gen

LibreELEC.tv/package.mk at le82 · escalade/LibreELEC.tv · GitHub

I rebuild the package with these flags

make_target() {
make HAVE_OPENGL=1
}

I suspect your system is to slow to run the core fast enough with software rendering enabled.

Quote from psrkallez06

I see, well I've tried every video setting i could find.. Turned of Vsync, enabled threaded video, tried to force a resolution, tried difference delays/changed latencys etc. It still runs very slow on LE9 "/

Also tried every PSX core.. on LE 8 i used PSX Rearmed which worked perfectly.

You used LE8 Remix or did you use LE8 vanilla + Gamestarter Addon? Basically you could use escalades build since his kernel, emulators, frontends and stuff are quite up-to-date. I only "forked" because I need Kodi 18 and the underlaying build system has some new features.

Well do you get a blank screen with enabled KMS and manually set display? Do you have "threaded video" enabled? Because this option made my psx emulator stuttering too.

I only see 52.5 "Vertical Refresh Rate" which basically means your panel runs at 52Hz as stated in Xorg.log . IMHO "estimated screen framerate" means RA runs/renders about 32fps so basically it just runs pretty slow. Anyway I guess you have to run games at ~50Hz or disable vsync. When I run Dolphin PAL60 Games at 50Hz they stutter too.

escalade

I know you added xorg-server: use modesetting for atom/celeron grade gpu's since KMS runs fine at my Celeron J3455 & i3-6100 so I did not. Otherwise it's just vanilla LE9 -> is there anything I have to consider?

Quote from psrkallez06

Found another issue.. I highly doubt that it is your build, rather i think it's the Kodi Leia since it is an Alpha.. PSX emulator is lagging a LOT. i can't get full speed, audio crackling etc. I was able to get full speed easily with Official Libreelec + Retroarch. When i launch retroarch with "nokms". It lags a lot. when i launch it without "nokms" and set my monitor index, it does launch BUT the TV is locked at 30 hz.. i can't change it to 59/60 hz like it should be so it still lags a lot.. do you have similar problems?

(refresh rate is grayed out in kodi settings also so I can't change it)

Can you tell me how to actually did install the latest moonlight into emulation station? I'm gonna try and do it myself for the LE8 remix. I'm not sure if i need to compile and (and if so how) or just drag in the files etc. i mean, first i download the latest release from:

Releases · irtimmer/moonlight-embedded · GitHub

after that I'm stuck.. do you know any good tutorial about it?

Well which resoluions are listed in Kodi config (expert mode)? RA isn't tied to Kodi settings afaik and estimates the refresh rate itself.

I tried to reproduce your stuttering but failed. Only if KMS is disabled & "threaded video" is enabled medanafen psx starts to stutter on my system but that is more likely a RA or core bug. I changed the refresh rate to 30hz in Kodi but still no stuttering. I guess your games are stuttering because they run asynchronous.

https://emulation.miraheze.org/wiki/using_retroarch#stuttering_due_to_inaccurate_refresh_rate_estimation

NTSC games need 60hz to run properly but your screen runs at 52Hz:

[INFO] [DRM]: Mode 0: (1366x768) 1366 x 768, 52 Hz

So I guess you have to disable vsync or try some play PAL games.

If you want to compile it yourself... well "good luck". I wasn't able to build escalades builds on my system without fixes or modifications because he uses Arch as build system and thats mostly bleeding edge. To update the moonlight package for old LE you need to modify this package GitHub - dead/script.moonlight: Moonlight-embedded Addon for Libreelec and you have to recompile the whole distribution to make sure moonlight is linked properly.

Btw.:

The script is pretty broken and I guess that's the reason they basically removed it moonlight service file not installed on Libreelec 9 with Kodi 18 Alpha · Issue #58 · dead/script.moonlight · GitHub so I'm pretty sure you won't be able to run it. I was able to create a "working" addon but only after several hacks and with a broken interface. So basically it's as good (or bad) as mine right now since the UI doesn't change the settings anymore.

FalconX

What kind of artifacts? I've experienced this in Kodi 17.x & 18 on my x86 systems when I used timeshift but not while watching regular TV. My RPis run fine tough even after pausing & unpausing so I guess it's some kind of Kodi/Intel driver bug.

Well I encountered these problems too. I have to rework the scripts especially because games like "Sid Meyer's..." won't launch because the single quote.

Anyway the basics work for now

If you have problems with streaming try h264 or h265 as codec instead of auto. I already patched the video decoder buffer size so h264 works fine but auto still falls after a short time.

When I have some more time to spare I'll try to optimize it.

psrkallez06

No problem but it should work now. At least in my tests I had no problems. Also press "Play+Back+LeftShoulder+RightShoulder" the same time & you can quit moonlight without any keyboard input.

Once the new build is online -> install it and pass something like this to your "Game".ml file or look in the moonlight config directory because there should be a Template.ml file.

GAMESTREAM_OPTIONS="-verbose -unsupported -width 1366 -height 768"
GAMESTREAM_ID="Steam"

psrkallez06

new build is online

Quote from psrkallez06

Damn it.. just noticed another issue for me. I can't get Retroarch to launch. I just get a black screen with a "Frozen" cursor in the corner.

here is the log:

External Content pastebin.com

Content embedded from external sources will not be displayed without your consent.

Display all external content

Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

I have updated the moonlight start script & you should now be able to pass custom options within the Game.ml files. I also added a Template.ml file. I'm uploading an updated x86 build right now.

Have you tried to disable KMS? touch /storage/.config/retroarch/nokms

Maybe this helps. Also do you have several outputs? Maybe RA just uses a wrong output to display it?

[INFO] [DRM]: Found 6 connectors.
[INFO] [DRM]: Connector 0 connected: yes
[INFO] [DRM]: Connector 0 has 1 modes.
[INFO] [DRM]: Connector 0 assigned to monitor index: #1.
[INFO] [DRM]: Connector 1 connected: no
[INFO] [DRM]: Connector 1 has 0 modes.
[INFO] [DRM]: Connector 2 connected: yes
[INFO] [DRM]: Connector 2 has 24 modes.
[INFO] [DRM]: Connector 2 assigned to monitor index: #2.
[INFO] [DRM]: Connector 3 connected: no
[INFO] [DRM]: Connector 3 has 0 modes.
[INFO] [DRM]: Connector 4 connected: no
[INFO] [DRM]: Connector 4 has 0 modes.
[INFO] [DRM]: Connector 5 connected: no
[INFO] [DRM]: Connector 5 has 4 modes.
[INFO] [DRM]: Mode 0: (1366x768) 1366 x 768, 52 Hz

Maybe this could help -> force the monitor index.

RetroArch/retroarch.cfg at master · libretro/RetroArch · GitHub

For example I have only 2 connectors & my it reports there is just one connection

[INFO] [DRM]: Connector 0 connected: yes
[INFO] [DRM]: Connector 0 has 43 modes.
[INFO] [DRM]: Connector 0 assigned to monitor index: #1.
[INFO] [DRM]: Connector 1 connected: no
[INFO] [DRM]: Connector 1 has 0 modes.

Are you able to start some games in Emulationstation? Try to start either MrBoom or 2048 as they rely on Retroarch too.

I don't see anything wrong in your log file beside the 6 connectors. Does RA run in escalades builds?

My script LibreELEC.tv/moonlight.start at libreelec-9.0-rr · 5schatten/LibreELEC.tv · GitHub starts moonlight this way:

export SDL_AUDIODRIVER=alsa

GAMESTREAM_ID=$(cat "$@")

moonlight stream -app "$GAMESTREAM_ID" -verbose > /var/log/moonlight.log 2>&1

It tells SDL to use the ALSA backend, reads the external variable ($@) passed by ES which is basically the path to the game.ml file, then it reads the content which should match a streamable game. So I have to rework this line to read additional commands like this:

moonlight stream "$OPTIONS" -app "$GAMESTREAM_ID" -verbose > /var/log/moonlight.log 2>&1

Maybe you can adjust the resolution according to your needs in \\your_system\Configfiles\moonlight\moonlight.conf too?

I closed moonlight by hitting ALT+ESC but I have to see if there is a better way to quit it.

How did the moonlight add-on ended the stream?

About the resolution you could add -unsopported xyz after the game name within the Game.ml file. Then this will be added to the command line.

psrkallez06

You shouldn't worry about 4.14.x build those are pretty outdated and I'll stick to upstream (kernel)patches.

I used the latest commit of moonlight GitHub - irtimmer/moonlight-embedded: Gamestream client for embedded systems and it should work with GFE 3.14.x well at least I've tested it with this version. Maybe recent versions broke the Kodi addon since it wasn't some bleeding edge software as my build.

I had more "problems" to get my controller up & running or some sound output because moonlight-embedded lacks compile switches to disable pulse. Or I didn't found them.

Anyway I tested these builds on my x86 HTPC & Steam, Witcher 3 and Skyrim worked. The rpi version started Steam so I guess it will work fine too. But I focused on setting up the program & and the scripts so maybe not everything is optimized right now.

Update:

Builds with moonlight are uploaded.

Uploading new generic & rpi builds with moonlight included. Once the builds are available have a look at the FAQ how to set it up properly.

psrkallez06

About moonlight... the easy part is done -> I was able to compile it for generic & rpi builds but now I have to figure out how to configure it properly.

Update:

Well at least the basics work fine -> have to test it later with my main HTPC build.

raspi3:~ # moonlight list x99
Connect to x99...
1. Steam
2. Heroes of the Storm
3. XCOM 2
4. Alien: Isolation
5. Sid Meier's Civilization: Beyond Earth
6. Fallout 4
7. Portal 2
8. PlayerUnknown's Battle Grounds
9. Half-Life 2: Episode One
10. Half-Life 2
11. Half-Life 2: Episode Two
12. DOTA 2
13. Diablo III
14. The Elder Scrolls Online
15. The Witcher 3: Wild Hunt
16. Middle-earth: Shadow of Mordor
17. Sid Meier's Civilization V (DX 11)
18. The Elder Scrolls V: Skyrim
19. StarCraft II
20. Overwatch
21. Sid Meier's Civilization VI

Update 2:

Rebuilding & uploading afterwards some builds with moonlight & Steam start option within ES.

MakeMKV

-improved the settings.conf handling while updating the key. [ thx vpeter ]

https://goo.gl/eu2uu9