@mitu I just saw the other answer in there, I'll try changing those flags and see what happens, thanks!

@pieterken without being familiar with the software we can't really say but retropie sits on top of raspbian, so anything that runs as a background process/daemon (which is what i assume 'domoticz' is) should still be running.

what do you use the browse the internet on TV? normal raspbian? you can launch into the pixel desktop via retropie: https://retropie.org.uk/docs/FAQ/#where-did-the-desktop-go

My suggestion would be to use the RetroPie image directly and not through BerryBoot.

@mitu ok, i will do just that. i will have my old image restored, update the OS and retropie, then follow the instructions in the previous thread.

@thd79 said in tvservice not able to change resolution on the fly:

This has definitely worked in the past for me, has support for it been removed recently? The same settings work fine when specified at boot time.

The tvservice and support for video mode switching are not part of RetroPie, but a Raspbian/Kernel+firmware feature - it was certainly not removed in RetroPie. What does 'in the past' mean ? 1 year, 1 week, etc. , before doing any kernel/firmware updates, using a certain RetroPie version maybe ?

What version of RetroPie are you running (specifically) and how it was installed ? Can you post your config.txt configuration file ?

It's a temporary issue with the upstream repository - watch this topic for updates.

Hey,

it's me again.
I guess I am a bit closer. I was wondering why my custom gamepad driver which generates a uinput device is not working. By incident I started the game directly without the start script, so I could see the information output. One of the very first lines was "couldn't find keyboard event file". I recognized that my custom driver creates a eventX in /dev/input but not in the subdirectories by-id or by-path.
So I tried to create a symbolic link in by-id, pointing at my event.

Now the keyboard-emulating gamepad worked in the game!

Playing that a bit further I went back to my gamepad driver which behaves like a gamepad without keyboard emulation. Running on top xboxdrv with mouse and keyboard emulation. again with a symlink in by-id.

Now the regular gamepad-driver with xboxdrv on top worked in the game!

Only point is, that no regular keyboard is allow to be connected (maybe be game only uses the first keyboard?).

BR
Florian

Wait, I got it. There was a boot to desktop option which I missed. Oops.