(2013-11-21, 02:27)Selene Wrote: Has anyone managed to figure out why the power button no longer works when you press it? Mine only responses to my remote now. I'm not too worried but it is going to be rather annoying down the line if I need to start without a remote?

(2013-11-21, 02:28)Alchete Wrote:

(2013-11-21, 02:27)Selene Wrote: Has anyone managed to figure out why the power button no longer works when you press it? Mine only responses to my remote now. I'm not too worried but it is going to be rather annoying down the line if I need to start without a remote?

My Power button works fine. i3 Haswell NUC.

I haven't touched any Bios settings.

For shutdown, I do need to do it twice from XBMC, as others have reported.

(2013-11-21, 02:28)Alchete Wrote:

(2013-11-21, 02:27)Selene Wrote: Has anyone managed to figure out why the power button no longer works when you press it? Mine only responses to my remote now. I'm not too worried but it is going to be rather annoying down the line if I need to start without a remote?

My Power button works fine. i3 Haswell NUC.

I haven't touched any Bios settings.

For shutdown, I do need to do it twice from XBMC, as others have reported.

(2013-11-21, 02:16)Alchete Wrote:

(2013-11-21, 01:26)Ravetrancer Wrote: I did enable expert settings but there is no Frame Multi Threaded Decoding, exactly between which options is it located under Playback?

RT, you need to be running the latest daily build, also as linked at the top of the instructions.

The multithreading option is only available in this build.

- Use the Nov. 20 Generic build here (x64): http://sources.openelec.tv/tmp/image/OpenELEC-Generic.x86_64-devel-20131120110738-r16406.tar

(2013-11-19, 23:29)Selene Wrote:

(2013-11-19, 20:56)Crssi Wrote:

(2013-11-19, 20:54)Selene Wrote: I think my windows issue was related to an addon. It seems to be working now..

Great to hear you have sorted out.
It might that I am getting SSD tomorrow, and I can do a test with Win. Which versions of Win did you try, and which is best for the porpuose?

I ran Windows 7 SP1.. worked off the bat, but I think 8.1 is probably better, if you can get it. There's a weird green line in the minimized video overlay (4:3) mode but not present in fullscreen that happens in Win7 but not in 8.

Otherwise I imagine they're very similar. Note that I did use XBMCLauncher, and I edited a ton of stuff, for example, I made sleep shutdown by editing registry keys, and I also replaced the bootloader, and messages using ResHacker.

Good luck

(2013-11-21, 03:52)Ravetrancer Wrote: I dont know if i get what u mean.
I installed the 16406 and then copied the codes to autostart.sh just like u wrote in ur post.

(2013-11-21, 03:00)Dropbear67 Wrote: Is it fair to say that openelec on this new nuc is still 'broken' in so far as getting proper display with hardware acceleration is concerned?

(2013-11-21, 05:25)lmyllari Wrote:

(2013-11-21, 03:00)Dropbear67 Wrote: Is it fair to say that openelec on this new nuc is still 'broken' in so far as getting proper display with hardware acceleration is concerned?

As broken as all hardware with Intel GPUs. There is a driver issue preventing proper colors on HD material when hardware decoding is used.

Another way to look at it is that Haswell is the only thing with proper 23.976Hz output and it has enough power for software decoding (except the i3 for 3D, not sure about i5). There should be no quality issues when set up properly.

I'm pretty sure hardware decoding is going to be fixed soon too. The driver is open source..

(2013-11-21, 06:22)Dropbear67 Wrote: That's really disappointing..

if the driver is open sourced and should be fixed soon, why hasn't it been fixed with the previous gen nucs??

(2013-11-20, 19:56)Alchete Wrote: I assume you're trying to build the driver/shader assembly directly in OpenELEC? Can you give a link to the source code and the steps you've taken to build it?