Posts by Kupo91

Hello there, I have some trouble with my remote and hoped to find some help.

This is my remote:

The orange buttons are for IR programming and I use them to turn on my TV. The white buttons interact with an usb dongle which I have to plug into my NUC. And everything works fine except for the power button (the white one). I wish to shutdown my Nuc with this button but instead it puts my NUC into sleep mode.

In my keyboard.xml file I have <power>ActivateWindow(ShutdownMenu)</power>

and I also tried it to map with keymap addon in kodi. So I also have a gen.xml file with

<keymap><global><keyboard><key id="61663">shutdown</key></keyboard></global></keymap>

but it still puts my NUC into sleep mode if I press the power button

Does anyone have an idea how to solve my issue?

Quote from Alucard

Regarding the J5005 I have one and I can confirm it allows you to run Beetle-PSX perfectly fine (tested with multiple games: Broken Sword 2, FF9, Symphony of the Night, Crash Team Racing, Suikoden...) and is light miles ahead of PCSX-ReARMed in terms of accuracy.

On what internal resolution do you play?

Quote from 5schatten

Well what does the Dolphin logfile say if it doesn't come up?

My dolphin logfile is empty. I have looked for an logging option that I have to enable but couldnt find anything. Did I miss something? However since rcb doesnt start it, shouldnt it be in the kodi logfiles? I just attached them. log-2019-03-04-13.07.38.zip

Quote from 5schatten

Beside RCB I guess that won't be possible since you're still starting a third party program. Also Kodi is only muted and runs in the background, so it probably still reacts on inputs. As I said there's reason why Retroplayer was invented or Kodi is shutdown otherwise. How should RCB run programs normally? What does it's documentation say about starting prgrams while Kodi is active?

Do you mean this by saying documentation? There is something about solo modes and using popen. Maybe this is an option? However since coming back to rcb after playing works fine with the "retroarch" file I thought its maybe just a command that I have to add in your *.start scripts

Quote from 5schatten

Bash

#!/bin/sh
# SPDX-License-Identifier: GPL-2.0-or-later
# Copyright (C) 2018-present 5schatten (https://github.com/5schatten)

. /etc/profile

# Freeze Kodi / stop audio
kodifreeze.sh freeze muteonly

# Change refresh rate to 60Hz
set_refresh_rate_60

# Set audio backend to ALSA
export SDL_AUDIODRIVER=alsa

# clean logfile
rm -f /var/log/PPSSPP.log

/usr/share/PPSSPP/PPSSPPSDL "$@" > /var/log/PPSSPP.log 2>&1

# Switch back to Kodi & start audio
kodifreeze.sh unfreeze muteonly

Display More

Thank you very much! It works for ppsspp and pcsx2! Awesome!

Only dolphin shows no reaction, can you take a look if everything is correct?

Bash

#!/bin/sh
# SPDX-License-Identifier: GPL-2.0-or-later
# Copyright (C) 0riginally created by Escalade (https://github.com/escalade)
# Copyright (C) 2018-present 5schatten (https://github.com/5schatten)

. /etc/profile

# Set common paths
DOLPHIN_HOME_CONFIG=/storage/.config/dolphin-emu/share
DOLPHIN_HOME_LOCAL=/storage/.local/share/dolphin-emu

# create link to config directory
if [ ! -L ${DOLPHIN_HOME_LOCAL} ]; then
  mkdir -p ${DOLPHIN_HOME_CONFIG}
  cp -r ${DOLPHIN_HOME_LOCAL}/* ${DOLPHIN_HOME_CONFIG}/
  rm -rf ${DOLPHIN_HOME_LOCAL}
  ln -s ${DOLPHIN_HOME_CONFIG} ${DOLPHIN_HOME_LOCAL}
fi

# Freeze Kodi / stop audio
kodifreeze.sh freeze muteonly

# Change refresh rate to 50Hz(PAL) or 60Hz(NTSC/PAL60)
set_refresh_rate_DOLPHIN

# Set audio backend to PulseAudio or ALSA
set_DOLPHIN_audiobackend

# Set Qt5 screen scale environment vars
set_QT_screen_scale_environment_vars

dolphin-emu "$@"> /var/log/dolphin.log 2>&1

# Switch back to Frontends or unfreeze Kodi & start audio
kodifreeze.sh unfreeze muteonly

Display More

I kept set_DOLPHIN_audiobackend because my dolphin audio settings is set to ALSA

And another question that I have is: After quitting a game I end up in kodi main menu and not in RCB. However when I first changed my libretro cores command from retroarch.start to retroarch it worked. Now I changed it back to retroarch.start and also end up in kodi main menu. Is there a solution for this?

Quote from 5schatten

Well this won't work as you might think. If RCB is Rom Collection Browser and a Kodi addon you can't use my scripts out of the box. You have to write start scripts that just mute Kodi instead of stopping it like it's done here LibreELEC.tv/google-chrome-stable at libreelec-9.x-rr · 5schatten/LibreELEC.tv · GitHub.
The you have to export the SDL audio driver LibreELEC.tv/910-audio-settings-common.conf at libreelec-9.x-rr · 5schatten/LibreELEC.tv · GitHub since PulseAudio won't work on the fly when Kodi is running. Basically you can use my scripts as template and replace the kodifreeze.sh calls appropriate to your needs.

Or you stick to Retroplayer, sacrifice all standalone emulators and use RCB

Bash: https://github.com/5schatten/LibreELEC.tv/blob/libreelec-9.x-rr/packages/5schatten/emulation-standalone/ppsspp/scripts/PPSSPP.start

#!/bin/sh
# SPDX-License-Identifier: GPL-2.0-or-later
# Copyright (C) 2018-present 5schatten (https://github.com/5schatten)

. /etc/profile

# Freeze Kodi / stop audio
kodifreeze.sh freeze muteonly

# Change refresh rate to 60Hz
set_refresh_rate_60

# Set audio backend to ALSA
export SDL_AUDIODRIVER=alsa

/usr/share/PPSSPP/PPSSPPSDL "$@" > /var/log/PPSSPP.log 2>&1

# Switch back to Kodi & start audio
kodifreeze.sh unfreeze muteonly

Display More

and then run this by /bin/sh -C /path/to/the/script

Thanks a lot to you

However it seems like something went wrong, it says it couldnt create line 16:

LibreELEC (5schatten): RR-20190221-753d629 (Generic.x86_64)
LibreELEC:~ # /bin/sh -C /storage/downloads/PPSSPP.start
Sending: {'content': 'RunScript(/usr/bin/audio-suspend.py)', 'type': 'action'}
/storage/downloads/PPSSPP.start: line 16: can't create /var/log/PPSSPP.log: File                                                                                                                                                              exists
Sending: {'content': 'RunScript(/usr/bin/audio-resume.py)', 'type': 'action'}
LibreELEC:~ # cp /var/log/PPSSPP.log /storage/downloads/

PPSSPP.log

5schatten I want to change my frontend from ES to RCB and I finally got it working for my libretro cores. In RCB the command has to be

 /usr/bin/retroarch and not /usr/bin/retroarch.start

However for ppsspp, dolphin and pcsx2 I only found the files with *.start

I tried to solve it by myself by opening the retroarch and retroarch.start file in notepad++ to check what is different but I dont really understand what is happening there.

In ppsspp I changed the command from

/usr/bin/ppsspp.start to /usr/share/PPSSPP/PPSSPPSDL 

and it atleast started the game. But it had no sound.

I also tested

/storage/.local/share/dolphin-emu instead of /usr/bin/dolphin.start

but it didnt start anything

and pcsx2 seems to be even more complicated with those docker commands.

Can you help me please?

Quote from 5schatten

What did you do? Install Docker & place the bios files and iso in the directories and run the game afterwards? ES has nothing to do with this since it just runs the PCSX2.start command and points to the game you want to run. Or do you try to load real game discs?

No real discs, just isos. And yes I installed Docker from the LE repo or from your google drive or both. Not sure. Its too long ago.

I just remember that I needed 2 attempts.

I placed the bios in bios folder and also selected it in the pcsx2 configuration wizard.

My isos are on a sd card. I changed the paths in a file called es_systems I guess.

Maybe I should reinstall everything. Do I have to connect my ssd with my computer to formate it or can I overwrite everything by flashing LE from sd card again?

Quote from 5schatten

Have you cleaned your PCSX2 config and tried again? I never had this issue on any of my systems so to me this sounds like a screwed up config.

No I had this issue from beginning on.. I just tried it after cleaning config but the issue persists. Its always the first attempt. I try to launch it via emulationstation and get this notification. I click ok or cancel, try it again this time via boot iso and it works.

Now I launched pcsx2 via putty to skip emulationstation. Then started the game via boot iso and it works at the first try.

..So its because of emulationstation?

Hey me again xD since I found some ps2 games which seem to run on my nuc I'm interested in running pcsx2 aswell. There is just a little detail in pcsx2 what annoys me a bit and I wondered if you maybe experienced that too. If I start a ps2 game via emulationstation I always get an error

"CDVD plugin failed to open. Your computer may have insufficient resources, or incompatible hardware/drivers. Press OK to go to the Plugin Configuration Panel."

I can just close this notification and start the game via System -> Boot ISO (fast). I cant explain this to myself because google says this error is caused when an iso is already in use. But how should this be the case in LibreElec? If I search for results in combination with LE I found this. Thats not about the CDVD plugin but about the GS plugin but maybe its similar?

Here are my logfiles

Quote from 5schatten

You use the wrong device. Your TV signals that you use HDMI1 so the first input of it's HDMI connections. I'm talking about your HDMI outputs and on Linux the numbering starts with 0. So set your output to hdmi:CARD=PCH,DEV=0 in my addon and reboot your device.

Thank you the reboot made it

Wow your answer came quickly. Yes I am. I mean in my kodi system audio settings my audio output device is set to

"ALSA: HDA Intel PCH, CTV UHD TV on HDMI #0"

But if I turn on my NUC my tv always show HDMI1 1080P@60Hz in the left corner. Thats why I set it to hdmi:CARD=PCH,DEV=1 and until yesterday evening this worked. Even with ALSA as backend audio.

PS: But to make sure I also tested DEV=0

Quote from 5schatten

Whatever you did you have not selected PulseAudio as backend. This is you log file:

Code

[INFO] ALSA: Using signed 16-bit format.
[INFO] ALSA: Period size: 384 frames
[INFO] ALSA: Buffer size: 1536 frames
[INFO] [Menu]: Found menu display driver: "gl".
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [LED]: LED driver = 'null' 0xa3b860
[INFO] [MIDI]: Initializing ...
[INFO] [MIDI]: Input disabled.
[INFO] [MIDI]: Output disabled.
[INFO] [MIDI]: Initialized "null" driver.

Display More

When I run Retroarch & PulseAudio it looks like this:

Code

[INFO] [PulseAudio]: Requested 24576 bytes buffer, got 18432.
[INFO] [Menu]: Found menu display driver: "gl".
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [LED]: LED driver = 'null' 0xa3b860
[INFO] [MIDI]: Initializing ...
[INFO] [MIDI]: Input disabled.
[INFO] [MIDI]: Output device "FluidSynth".
[INFO] [MIDI]: Initialized "alsa" driver.

If you haven't changed anything the sound "shouldn't be gone" at some point. Check you settings and make sure you've selected the right output.

So what you want me to do is going into RR config and selecting Pulse instead of ALSA, right? I did but that doesn't solve my problem. Still no audio.

Quote from 5schatten

Well you have to check your Retroarch core settings & increase the internal resolution of your PPSSPP core. That's all.

Same goes for PCSX_reARMed. If you run it on an ARM system you can enable the enhancements if it's not an ARM system there is no option for that. And again you could use Beetle PSX & increase the resolution but only if you have a decent CPU as lang as there is no working dynarec on x86-64 CPUs.

But this has nothing to do with this build in particular. I ship PPSSPP, PCSX_reARMED and everything else with default settings and you have to adjust them to your system

If you want to use custom skins ask the devs how to run custom commands and read the example how it works with Confluence. If you can't create menu entries that run commands in Addons you can't place them there. Also it makes no sense to place it in addons because they are not addons but software that is compiled for and with this image.

You were right. On my S905X box there are options like "Enhanced resolution" which I dont have on my NUC. Too bad. Then all I can do is hoping that they implement that dynamic recompiler. Although I dont understand that I can increase ppsspp's resolution to x5 without having lags while I cant increase beetles resolution to x2..

And I have a new issue <.< I have sound in kodi and no sound in es/while playing. It startet when I updated your build. Then I activated your new config addon and changed audio device from sysdefault to hdmi:CARD=PCH,DEV=1. Sound was back again. And also in ES for the first time. Even if I dont need it there because I have no videofiles. But nice to have. Anyways I cant remember to change anything. I just switched a few times between my S905X box and my NUC. At some point the audio in ES and while playing was gone.

Here are my log files... https://drive.google.com/open?id=1j_0sz4cfm7aztp7stymsu7zajrrqkl8i

5schatten I now was able to test some things. My controller and also accessing the profile folder of dolphin work very well now. Thanks a lot for your changes.

I also tested the pcsx_rearmed core in your build and it has the same pixel graphics as the beetle psx core. So my first thought was its no core issue but a retroarch issue. So I tested another retroarch core and indeed there are the same differents.

In the following picture you can see a screenshot of ppsspp libretro core in your build (top) and a screenshot of ppsspp libretro core on my S905X box (bot):

So as I said my thought was its not an core issue but a retroarch issue. However the ppsspp standalone emulator has the same pixel graphics.. so maybe the issue is anywhere else in my graphic settings?

Another question that I have is: I still try to integrate those apps like chrome, retroarch etc. in my skin. I showed the following quote of your faq to the skin author but he told me that he fist have to get an android box to test libreelec. Then I wondered if its possible to execute those scripts as addons? Because you can easily integrate addons in the main menu of aeon mq7. Furthermore I prefer to have those apps in the same place as my addons instead of having them in my main menu. However I have no clue of those things and its just a question if its possible and if yes how complicated it would be. Maybe you can answer this?

Quote from 5schatten

V. Kodi Themes & Custom Skins

If you prefer a custom skin and want to start the apps & emulator frontends you'll have to find a way to execute the following scripts. Confluence users can uses this to include the emulation frontends.

Display Spoiler

Chrome

# /usr/bin/app-google-chrome.py

Spotify

# /usr/bin/app-spotify.py

Emulationstation

# /usr/bin/frontend-emulationstation.py

Emulationstation

# /usr/bin/frontend-pegasus-fe.py

Retroarch

# /usr/bin/frontend-retroarch.py

Display More

Quote from 5schatten

Yeah it's somewhat a gap between those two. Anyway you'll should be able to play Saturn, Dreamcast, GameCube and Wii stuff on those NUCs so IMHO it's absolutely worth it.

Mh those are not my main platforms. I actually have just one game for Dreamcast and Wii. Most games which I play are for PS1 or Gameboy. So the bad Beetle graphics are an issue for me but I hope the dynamic recompiler will give me some better results when its implemented one day.

However I also remember that I've only compared Beetle PSX with PCSX_Rearmed on my AML box. Not with PCSX_Rearmed for generic in your build. Maybe it looks like the same. I'm gonna test it as far as I can. If PCSX_Rearmed is looking good I will keep it for all my single disk games and will take Beetle only for multidisk games. Multidisk games are actually the only reason why I want to use Beetle instead of PCSX_Rearmed. Otherwise I'm totally fine with PCSX_Rearmed

Quote from 5schatten

Well it was something I had in mind for quite some time since backing it up for testing purposes was a bit complicated for me too.

Unfortunately I cant test it yet. Same like the new controller mapping on SHL since the NUC that I've ordered is delaying more and more (ordered it in Dec 18th, now they told me its gonna be avril or later. I cancelled it and ordered it somewhere else). But I'm looking forward to test it

Quote from 5schatten

The J4005 was fine the J5005 has 4 cores 4 threads while the celeron has 2 cores / 4 threads. Both have a TDP of 10W so when they run hot I suspect the J5005 will throttle earlier. The thing is both are faster than any arm stuff but not as fast as an i3 or else. IMHO the J5005 is too expensive and won't let you run PCSX2 or Beetle-PSX too. If you really want to run all games then you've to buy a mini-itx system with a small i3 or AMD Ryzen 3 2200G, 4x 3.50GHz, boxed ab â¬Â 91,90 (2019) | Preisvergleich Geizhals Deutschland or Intel Pentium Gold G5400, 2x 3.70GHz, tray ab â¬Â 70,92 (2019) | Preisvergleich Geizhals Deutschland

Oh okay. Thats not worth it to me but thank you for explanation

Quote from 5schatten

About the Dolphin dir -> I've changed to path so you can access & backup your data by copying the dolphin-emu dir in configfiles.

Thank you

Quote from 5schatten

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

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).

Quote from 5schatten

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.

Quote from 5schatten

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.

Quote from 5schatten

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:

/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

Quote from 5schatten

You want to increase the resolution by 4 to 8 times so. I already did the math for you 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.

Quote from 5schatten

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.

Quote from 5schatten

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.

Quote from 5schatten

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.

Quote from 5schatten

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.

Quote from 5schatten

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!

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

Quote from 5schatten

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.