[RELEASE] Steam Launcher - Start Steam Big Picture Mode from within Kodi - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27) +---- Forum: Program Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=151) +---- Thread: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within Kodi (/showthread.php?tid=157499) |
RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - munificent - 2014-03-06 Yup, the rollback worked. Very nice. Sadly, Steam's streaming doesn't seem to work so well from Big Picture, but I'm glad I'm vaguely ready for it when it does. RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - teeedubb - 2014-03-08 New version in OP: Quote:0.9.10 @people having to use v0.5.2, can you try this version, if it doesnt work please post a debug log (wiki). If its still not working try to use the 'Batch file' option - more info above and on first page. RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - wolfodeiwolfy - 2014-03-08 (2014-02-17, 07:31)teeedubb Wrote:(2014-02-15, 11:28)wolfodeiwolfy Wrote: Hi, I've just updated from 0.5.2 to 0.9.8 and it doesn't work. Steam bpm doesn't launch (add-on settings are correct).Do you get any errors in xbmc or autohotkey? Youre using windows right? Which exact version and edition, eg x64/x86, home premium/ultimate etc? Anything else that could affect the addon (as it uses external scripts)?Someone else reported the same problem but I'm unable to reproduce it on 2x win7 + 1x win8 x64 home premium installs. If I cant work out the problem is, when I have some time I'll look at adding a option to use a batch file as was the case in v0.5.2. Hi, sorry I didn't play a game for a long time. I've just tried v0.9.15. It works perfectly. I'm running windws 8.1 x64 home edition on i5 3570k with gtx 660, xbmc 12.2, artic skin RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - GCMX - 2014-03-11 Hi teeedub, I've set up xbmc and ubuntu minimal following this guide: http://forum.xbmc.org/showthread.php?tid=174854 I've installed openbox and wmctrl and made steam-launch.sh executable from within the addon-setings. I then followed your instructions here: http://forum.xbmc.org/showthread.php?tid=157499&pid=1584693#pid1584693 When I run the addon I get a "working" popup for a bit, then it disappears and nothing further happens. XBMC isn't even getting killed (the add-on setting says always kill XBMC). I can start steam by ssh from within XBMC using: Code: DISPLAY=:0 steam -bigpicture Although it gets stuck on selecting a network (I think this is simply because I haven't yet installed a network manager, wireless is working from the initial installation setup). Has anything changed in the addon-on to make your suggested scripts not work? The other possible cause of the issue is that I can't for the life of me work out how to start openbox. Because of that openbox has never run and I'm guessing there might be some initialisation that needs to take place before your scripts can work. I assume I have to kill XBMC and then start openbox but everything I've tried fails. Most guides are to start openbox at startup (which I don't really want, although will resort to if all else fails). Any ideas? Cheers RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - teeedubb - 2014-03-12 From a quick look at the minimal guide you need to omit one step, the /etc/xinit/xbmc.conf step, so disable the upstart script. I've updated my post you linked to with clearer instructions + wiki links. I think the script not working is from copy/pasting whole code blocks from that post, delete the user scripts via the addon settings and try with the updated instructions. If xbmc isnt killed with the new script please post a debug log (wiki). RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - rassilon - 2014-03-13 (2014-03-12, 07:07)teeedubb Wrote: From a quick look at the minimal guide you need to omit one step, the /etc/xinit/xbmc.conf step, so disable the upstart script. I've updated my post you linked to with clearer instructions + wiki links. I think the script not working is from copy/pasting whole code blocks from that post, delete the user scripts via the addon settings and try with the updated instructions. If xbmc isnt killed with the new script please post a debug log (wiki). I followed your setup there and changed some of the paths to match my system, but XBMC takes forever to startup and instead of a black background, its a black background with 13.10, then a couple of flickers and it opens XBMC. Steam launches fine when everything boots up. Sometimes when I reboot, it just hangs on the ubuntu 13.10 loading screen and never launches XBMC. Any advice? RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - teeedubb - 2014-03-14 Not sure why it would be taking long to boot, pressing escape will show you whats going on at boot time, you can also have a look in the log files in /var/log/ RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - rassilon - 2014-03-17 Weird. For some reason that bash_profile script is causing my system to not start X for around 3 minutes. I disabled it and had X start on boot and it works fine. I can't find anything in /var/log/boot.log or /var/log/Xorg.0.log that explains it. Also, the irxevent script isn't launching irxevent when XBMC is closed. RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - teeedubb - 2014-03-18 Youre not trying that method over xbmcbuntu/etc, how does X start if you remove .bash_profile? Unless your system disagrees with the command to launch X in the .bash_profile, I cant see why it would hang for minutes. Run the irexevent script, or individually, via ssh to see what going on/whether irxevent works. RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - rassilon - 2014-03-18 It looks like I put the fstrim in my rc.local and that was causing the delay.. So when I removed that line its back toba few seconds, yay. When I run the irxevent script I get: Code: ./.irxevent.sh: 6: ./.irxevent.sh: [[: not found Edit: Fixed it, #!/bin/bash was missing at the top of the script RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - teeedubb - 2014-03-19 SteamOS + Ubuntu Installing the packages from this PPA will give you a Steam Os session in Ubuntu, with the steam compositor, so you can log into it via lightdm, xinit etc or via the addon using my method here.. Steam OS BPM is slightly different to non SteamOS BPM. Note that running steam os has reset my steam install, games and all, on several occasions so do so at your own risk, although it is possible to run non steamos bpm with the valve compositor which has been trouble free and Ive found the steam compositor best for playing games. Only downside is that the "Retun to desktop" option does not work in this mode. If you want to use the steamos session, it is started via /usr/bin/steamos-session. If you want to run a steam bpm session copy the file /usr/bin/steamos-session elsewhere, as it will be overwritten with updates, and change the last line to something like the following: Code: steam -bigpicture #-tenfoot -steamos -enableremotecontrol You can also add other programs to load suchs as unclutter or pulseaudio, a copy of mine as a example: ~/.scripts/steamos-session-xbmc Code: #!/bin/sh Also the steamos-xpad driver from that PPA is worth installing if you use a 360 controller, it stops the flashing ring of light. RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - GCMX - 2014-03-20 (2014-03-12, 07:07)teeedubb Wrote: From a quick look at the minimal guide you need to omit one step, the /etc/xinit/xbmc.conf step, so disable the upstart script. I've updated my post you linked to with clearer instructions + wiki links. I think the script not working is from copy/pasting whole code blocks from that post, delete the user scripts via the addon settings and try with the updated instructions. If xbmc isnt killed with the new script please post a debug log (wiki). Thanks for all your effort teeedubb. I haven't had a chance to try this yet, but I'll report back when I do. RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - teeedubb - 2014-03-21 To people using my repo: Due to a change in the way that github handles links a manual update to v1.0.1 is required. This solves xbmc on linux crashing when checking for updates. Link in first post updated and it can also be downloaded from https://github.com/teeedubb/teeedubb-xbmc-repo/blob/master/repository.teeedubb/ RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - LSU Jonno - 2014-03-25 teeedub, Thanks for the great plugin! I'm having some trouble getting it working. I'm a linux newb running XBMCbuntu. I understand your first post about running Steam Launcher from an XBMC session. However, if I log into my desktop and launch XBMC from the desktop I can't get Steam Launcher to work. I've installed wmctrl and Quote: Linux only: Make steam-launch.sh executable on next run - This changes the executable bit on the file 'steam-launch.sh' which is necessary for this addon to run, Linux users need to do this on the first run and after deleting the profile://addon_data scripts. This setting defaults to off after being run once. ...but I keep getting an error that steam-launch.sh could not run. I'm using XBMCbuntu 13: http://forum.xbmc.org/showthread.php?tid=189553 Also, anyone know how to make XBMC autostart in XBMCbuntu from the desktop? I think I'd rather launch this way rather than through the XBMC session so that plugins like this one and Chrome launcher work without going through too much configuration. RE: [RELEASE] Steam Launcher - Start Steam Big Picture Mode from within XBMC - teeedubb - 2014-03-25 Hmmmm... I haven't upgraded to xbmcbuntu 13 yet so I haven't tested it with 13. Can you please post a log file of the error occurring. |