Nothing is displayed on the screen in plugin "Commodore - Amiga (P-UAE)"
Opened this issue · 11 comments
Bug report
Describe the bug
Here is a clear and concise description of what the problem is:
I can't see the emulated image.
I use the "Commodore - Amiga (P-UAE)" plugin from the LibreELECT repository (versions 11 and 12). Tested on different versions of the plugin and on the latest one.
Kodi works fine, but when using this plugin "Commodore - Amiga (P-UAE)" no image appears on the screen. The emulator works, e.g. the music from the game can be heard. When saving a position (snapshot) the image of the saved position shows the game image. But the emulator image itself is not displayed. Even the control and notification messages from the emulator work, but the image of e.g. the emulated game does not.
I use LibreELECT in a virtualized (ProxMox) environment with redirection to a physical graphics card. (Everything else is not a problem), but the emulator image is.
RetroArch Behavior
Here is a clear and concise description of what happens in RetroArch with the same core/game:
The problem is everywhere and always.
To Reproduce
Steps to reproduce the behavior:
Just play anything.
Debuglog
The debuglog can be found here:
Please help me what to look for in the log to insert the correct text here.
Screenshots
Here are some links or screenshots to help explain the problem:
There's nothing to photograph on a black screen.
Your Environment
Used Operating system:
- Android
- iOS
- Linux
- OSX
- Raspberri-Pi
- Windows
- Windows UWP
LibreELECT 11 and 12 verison.
Operating system version/name:
Linux
Kodi version:
12 and 11.
note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.
Can you try my latest LE 12 build at https://github.com/garbear/xbmc/releases? It contains an unmerged fix for black screens.
Also add-on versions are helpful, as I maintain the versions in the LE repo.
Thanks for the response, yes, if I use the build "LibreELEC-Generic.x86_64-12.0-retroplayer-20240528-d68f9e7a.img.gz" screens works, so should I just wait for the patch to get to the main branch?
Annoyingly, in the emulator not working keyboard or mouse (mouse doesn't work in Kodi, the keyboard does). The virtual keyboard works.
The keyboard might be a problem on my side, I might just have something wrong, because one key (space) works.
One more addendum, in the linked bug report, it mentions the theory that the bug happens on old graphics cards, but I have an AMD Radeon RX6400.
I don't know if it's due to a temporary fix, but the image contains occasional graphic errors.
Thanks for the response, yes, if I use the build "LibreELEC-Generic.x86_64-12.0-retroplayer-20240528-d68f9e7a.img.gz" screens works, so should I just wait for the patch to get to the main branch?
The release notes link to the "temporary fix": garbear/xbmc@6f75325
As you can see, there's two tasks to fixing this bug:
- Register buffer objects in a different order
- Add a buffer import check for input stream
I'm short on time but I encourage you to look into these two or start an effort for the community to do so.
Annoyingly, in the emulator not working keyboard or mouse (mouse doesn't work in Kodi, the keyboard does). The virtual keyboard works.
Because I designed the input system, if there's broken input I can usually quickly fix it. Can you upload a debug log of input not working?
I don't know if it's due to a temporary fix, but the image contains occasional graphic errors.
Unlikely due to the fix. You can narrow it down to core/frontend by trying the same core and game in RetroArch.
Wouldn't it be better to close this task and mark it as solved, even if it is just a "hotfix", and create a new task for the input device problem?
I guess it would help people, who come here via the search engine link when they are looking for a solution to the same problem I had.
It's just an idea...
A new issue for input would be good. I think this issue should stay open, because it's only "fixed" (hacked) in my personal fork, and the issue still exists in upstream LE.
I solved the control problem, only I didn't know that I had to map the physical controller to the virtual one... (in my case the gamepad (PS4) to the Amiga gamepad...
Thank you so much for the effort and I'll just wait for the final fix screen...
Have a nice day...
Hm, I thought I shipped buttonmaps for Amiga so that controllers would work out of the box. I'll look into that when I get a chance.
As for the black screen fix, I'll hit up the dev who pointed me to the current hack, but he's pretty busy so we may not get this fixed in upstream for a while. Until then, you can use my test builds with the fix: https://github.com/garbear/xbmc/releases. If you want any customizations let me know.
Also, interesting observation, my boomer dad (love him) uses ellipses. Gen Z sees these as hesitant or unsure. Just so us aging programmers are aware.
I'm very busy, so I know. This is a community project, so that's how I approach it.
The keyboard works fine, the gamepad doesn't by default, but it's up for consideration whether that's a good thing or a bad thing. You just need to remap the controller, it's more of a shame that the system doesn't point that out...