+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Windows (https://forum.kodi.tv/forumdisplay.php?fid=59)
+---- Thread: [WINDOWS] Unofficial third-party nightly builds for the community (Notification only) (/showthread.php?tid=35452)
- nugentgl - 2009-11-24
Why not continue the post in the sticky? It was very convenient up there.
- ikons - 2009-11-24
http://forum.xbmc.org/showpost.php?p=431008&postcount=1145
- ikons - 2009-11-25
Upped new build
- ikons - 2009-11-26
Upped a new build
Odd Behavior with SVN:25049 - ijourneaux - 2009-11-26
This could be an issue with the Launcher plug-in but I thought I would report it anyway.
Somtime and only sometimes when lauching BeyondTV with the Launcher plugin, XBMC seems to hang before it minimizes. When this happens, XBMC is totally unresponsive. Althouhg it seems as if I can kick-off taskmanager using control-alt-delete, what is left of XBMC is always in the foreround. The only way to get out of this is to power cycle the computer.
This problem never seems to occur the first time I used Launcher in an XBMC session.
ALthough I am using the SVN, if this looks important, I will reinstall the latest beta and duplicate the problem. I have seen this issue in the recent official alphas and beta.
Here is the log
http://pastebin.com/m76cdd64
- ikons - 2009-11-27
Upped a new build
- johnny2 - 2009-11-27
nugentgl Wrote:Why not continue the post in the sticky? It was very convenient up there.
Because the overzealous devs locked the thread. Thanks to ikons for fighting the good fight and continuing to do the builds after his thread got abruptly shut down.
- AzzX - 2009-11-27
http://forum.xbmc.org/showpost.php?p=431008&postcount=1145
- xexe - 2009-11-27
The download in the OP is linked to the wrong EXE
- WiSo - 2009-11-27
johnny2 Wrote:Because the overzealous devs locked the thread. Thanks to ikons for fighting the good fight and continuing to do the builds after his thread got abruptly shut down.
If we would see this as a fight we would lock the thread too and ban ikons.
We just asked for understanding but unfortunately many users (as you?) just wanna take it for free instead of giving us something back.
- TiN-MAN - 2009-11-27
WiSo: Its not because we don't want to give something back. But I actually use XBMC on a (allmost) daily basis, and if there is an annoying error preventing smooth operation I dont want to sit around waiting for a new beta, when there is a good chance the error already have been fixed in the svn.
I understand that there is a lot of (L)users out-there whos got itching bug-reporting triggerfingers, not careing about versions and thats why you locked the sticky thread.
So thank you for allowing the continued thread about svn releases.
I think most users of the svn version would do like ijourneaux and try to replicate the error in the latest beta, if its a serious error.
Hope this makes any sense :-)
- ashlar - 2009-11-27
johnny2 Wrote:Because the overzealous devs locked the thread. Thanks to ikons for fighting the good fight and continuing to do the builds after his thread got abruptly shut down.I'll stop at this message and won't reply further but, really, are you serious about this? Overzealous devs? Fighting the good fight? You probably don't have the slightest idea about debugging stuff, using a controlled environment, being grateful to people that give you stuff for free out of their hard work.
You should present your excuses to the devs and leave it at that.
Since I don't have time, currently, for proper debugging, I'm still at SVN 21930 and guess what? It works great. If somebody has uncontrollable upgraditis it would do well not to take it on devs.
Cheers.
- watzen - 2009-11-27
TiN-MAN Wrote:WiSo: Its not because we don't want to give something back. But I actually use XBMC on a (allmost) daily basis, and if there is an annoying error preventing smooth operation I dont want to sit around waiting for a new beta, when there is a good chance the error already have been fixed in the svn.
I understand that there is a lot of (L)users out-there whos got itching bug-reporting triggerfingers, not careing about versions and thats why you locked the sticky thread.
So thank you for allowing the continued thread about svn releases.
I think most users of the svn version would do like ijourneaux and try to replicate the error in the latest beta, if its a serious error.
Hope this makes any sense :-)
If you're that serious why don't you build it yourself. it's dead simple... If you can't even do that, then you should use the builds sanctioned by the team.
- ikons - 2009-11-27
Link is fixed
- ikons - 2009-11-28
Update