Hi, not sure if there was something breaking in 1.0.0 as part of rewrite, specifically for new installs?
I’ve just installed 1.0.0 on a fresh install of Matrix RC3 and couldn’t get to work, if would say pairing failed, but I could see games in “quick lunch”. When pairing via SSH I would get correct message. When I would launch from UI it wouldn’t open games and just black screen. Also It wasn’t producing any logs, sorry so I can’t send anything (e.g. in here ~/.kodi/addons/script.luna/bin/). I installed and uninstalled, rebooted and keep all default, even tried some other settings (video format etc) but nothing.
As soon as I downgraded to 0.9.0 everything worked perfectly.
Let me know if there is anything I can do to help debug.
Both wouldn’t load a game list, it would only show games in the “quick launch” section. It would show this even after I unpaired and did a reinstall, so I’m thinking something was keeping old pairing or settings.
Dont think it’s surround sound issue as I left both 1.0.0 settings and 0.9.0 audio settings exactly same?
Don’t think its’ incompatible device, using odroid n2+?
I’m thinking it’s a pairing issues as it was doing some weird things noted below:
When I ssh’d into device and would do moonlight stream from home directly, I would get a “no mapping defined” error. But if I cd’d into ~/.kodi/addons/script.luna/bin/ and did exact same, it would try and launch but would give different errors. So it was like launch moonlight was using different configs depending on where it was launched.
Again I think it was keeping old pairing for some reason as even before I paired I could run moonlight list and it would list my games.
I unpaired and paired in SSH but would consistently get pairing already done. I did clear paring multiple times on my PC, (Nvidia settings → forget shields) and that would force a repair. But that didn’t help in terms fixing anything.
No matter what I did I couldn’t get pairing working in UI (in terms of it getting my PC to launch Nvidia popup to enter pin), only when i did it via SSH or used 0.9.0 UI.
Also not sure if this was meant to be but 0.9.0 UI menu is really different to 1.0.0 UI menu? Just wanted to make sure it wasn’t something with my setup and maybe causing issue.
1.0.0 is a complete rewrite and effectively a downgrade compared to 0.9.0. The game list UI is dropped because I don’t want to maintain it.
If I ever do decide to upgrade back to the game list UI, I have to make it a full-time project for a month or two, in order to get experience with Kodi’s plugin system and making moonlight and Kodi work together. moonlight unpair doesn’t work
It seems that people at Nvidia have figured out unpairing is a useless feature, as pairing keys get deleted whenever you uninstall their app on Shield. Forget shields will force repair, so that’s all good.
In order to force repair from the moonlight client, you have to delete /storage/.cache/moonlight, but this will get fixed at some point in Luna. You cannot use moonlight stream if gamecontrollerdb.txt is not in your current working directory
Moonlight binary will check for gamecontrollerdb.txt for typical Linux installations. But since CoreELEC uses a read-only file system, this file isn’t located at the typical locations, so moonlight won’t work if the file isn’t in your cwd. Running moonlight stream from ~/.kodi/addons/script.luna/bin
This is what Luna does in the backend. It will save a moonlight.conf file based on your configuration in the settings. When you upgrade from 0.9.0 to 1.0.0, it is possible some settings won’t get auto-converted, hence you might have an invalid configuration.
If there’s errors running moonlight stream, delete your moonlight.conf and try again.
Running from SSH will output useful information, if you get any errors there, post them here, I can help you with fixing issues from logs.
Thanks that’s awesome in terms of helping me debug.
I’ll clear the keys/unpair as I feel that might have not been working properly even with force repair. Also might clear the .conf and let it generate again and see if that results in improvement.
I’ll upgrade from 0.9.0 and see if that works straight way but if not, then I’ll try steps above.
@smg04, have tested your latest build after updating from the script.luna-1.0.1-matrix.126 version. Left all my settings the same as had been set previously and unfortunately my surround channels are all messed up now the old version worked very well after all that testing we did before.
Can you send your logfile after you’ve run moonlight?
There’s a trick now: as soon as moonlight establishes connection, close it via shortcut. If moonlight closes in less than 10 seconds, Luna will trigger a crash message and will ask you if you want to make a bug report. Then you can send the link here for me to check out.
In case that doesn’t work, just send logfile from ~/storage/.kodi/addons/script.luna/bin/logfile.
hi @smg04
I have tried the last version: script.luna-1.1.0-matrix.127, and I was able to pair to pc.
Clicking on a game or desktop raises LUNA’s opening and then an error message pops up:
it seems that moonlight embedded might have crashed. create an automatic bug report.
when I clicking yes it said to check the logs for more information.
I tried to pull the logs and send it but there is no such folder ‘logfile’ in the location you specified:
/storage/.kodi/addons/script.luna/bin/logfile
Try going to settings and in extras find option “Select launchscripts” then choose the coreelec one. Scripts dont have the execute permission so it cannot launch.
@Adam86 could you send the logfile again, with the latest version?
I recommend rolling back to the old version for now if surround is required, it seems that CoreELEC audio drivers doesn’t use the same channel map, so a remap function is required. For now, use versions prior to 127 until I build a patch for 129 (friday or saturday) and a better solution will come in the future.
@smg04, no problem, will downgrade to 126 for now.
What additional changes had you made for the surround sound with these newer builds? As I know you spent a lot of time with me and @Kaan getting it work previously. So didn’t think anything else needed sorting on the surround front!
Welp, the proposed fix is basically a compromise. The current solution is to change the order of inputs so it goes to the correct channels, but that order only works on CoreELEC. So if u were to use the binaries on another OS, the channels would have the wrong order again. Also, the order from CoreELEC is not the same as one proposed by ALSA, which should be standardized.
A better solution would be to specify a parameter where you would remap the channels if the layout is not a standard one. I added one commit that was supposed to force ALSA to use channel map given by moonlight, but it doesn’t work…
the old version worked very well after all that testing we did before.