Kodi Community Forum

(2015-06-09, 09:21)Helioy Wrote: [ -> ]

(2015-06-09, 02:42)Woppie Wrote: [ -> ]I've hit a reproducible issue while testing this one. If you want a log I'll run it tomorrow.
After I put it into standby and wake the tv up over CEC kodi goes all mental and flashes the screen with black screens and the menu becomes sluggish.
This happens on a i3-3225 with HD4000 and the latest build.
Other than that before putting the htpc into standby no issues have been observed whatsoever.

Are you sure it is only this build? This also happened for me, but I found out that this was a broken intel graphics driver.... You havn't updated it since february? For more see http://forum.kodi.tv/showthread.php?tid=...pid1977432

It didn't happen with v14 or beta1, this is the first dx11 build I've tested. Actually I have updated since February and I'm on version .4176 now which isn't the .4180 that seems problematic in that topic. I'll update a bit and see if different version make a difference.

Now on 15.33.36.64.4226 (latest), will see how it goes.

(2015-06-09, 09:25)afedchin Wrote: [ -> ]

(2015-06-09, 02:42)Woppie Wrote: [ -> ]I've hit a reproducible issue while testing this one. If you want a log I'll run it tomorrow.
After I put it into standby and wake the tv up over CEC kodi goes all mental and flashes the screen with black screens and the menu becomes sluggish.
This happens on a i3-3225 with HD4000 and the latest build.
Other than that before putting the htpc into standby no issues have been observed whatsoever.

Do you have same issue with latest nightly? Please try to reproduce this with latest nightly http://mirrors.kodi.tv/nightlies/win32/

Let me try, if it persists with a combination of the drivers mentioned above I'll let you know and edit this post.
Also I'm already on the latest version from June the 4th already.

Edit: now it doesn't wake up over cec anymore so let me first research that.

Ok, just wanted to be sure it wasn't a similar issue to mine

As i mentioned a while back, in system info there's no "DirectX vendor" filled in.
http://pastebin.com/983HsThh

NVIDIA GTX275 driver 341.44

Actually my other system also doesn't report DirectX vendor
http://pastebin.com/3Qc5HgYW
Zotac EI730 on Windows 10

@Martijn
unfortunatly, this is "normal" behavior in current version. This is https://msdn.microsoft.com/en-us/library...s.85).aspx only what I can get about current adapter. dx9 adapter description (https://msdn.microsoft.com/ru-ru/library...s.85).aspx) has more descriptions about current adapter. I'll try to find a way to get all this info fro dx11 version.

For all I care you just remove the line
I think it's of little real use now days. If it would be important just put it in the log file

@afedchin I briefly played some files, excellent work! Everything is really smooth. I noticed one thing. When cycling through the deinterlace video setting in th video osd there's a green flicker, maybe one or two frames. I'm on the run the run, if you need a log file and can provide one tonight.

@Martijn
What do you think about this?


@Ace
Thanks. The Debug Log would be useful.

@afedching: Looks fine - if you could reduce the memory usage a bit :-) (just joking)

IMO remove both DirectX vendor and GPU temperature items for win32. Neither VendorId, nor DeviceId provide any valuable information to the average user and they are part of the debug logs anyhow. GPU temperature never worked on Windows AFAIK.

@a11599, just make sure those are logged somewhere as we have 100ts of workarounds for different deviceids, especially f*cked up AMD video cards.

iirc GPU temperature worked at some point.
Just log Vendor and device ID at start of the log and remove from system info

Hm. I have never seen anything else than ? on Windows with Intel/nVidia/AMD. But I use it on Windows since Dharma only.

@a11599 is right GPU temperature never works on Windows.

@fritsch
The dx11 version has no any workarounds - only generic code, only hardcore

new version


reduce used memory as fritsch wants