(2013-08-24, 12:20)popcornmix Wrote:

(2013-08-24, 11:58)SSC_Jarod Wrote: 3D Problem, that TV doesnt automatic switch to 3D (preferred mode = none) still there.

I think that got broken by:
https://github.com/xbmc/xbmc/pull/3099

I did patch the 3D audo switching code after that went in, but didn't have a 3D tv to test it on. I'll try to investigate more this weekend.

Note: XBMC doesn't support automatically switching to 3D mode on any platform, so until this happens, it's going to be an unofficial hack, and is subject to breaking with other xbmc commits.

I did submit a PR to try to get 3D auto switching support into main XBMC, but the result is that it's complicated and there's no scheme that fits well with the current architecture.
https://github.com/xbmc/xbmc/pull/3072

(2013-08-23, 17:59)evanspae Wrote:

(2013-08-23, 16:52)doveman2 Wrote: xbmc.log is an hour out (it's 15:49 here now but the log shows 14:49). I think the problem started at 14:27 in the log.

---

I confirm this has been broken for at least last two Gotham builds

(2013-08-24, 19:04)misa Wrote: Try to remove <guires>1080 or 720</guires> from advancedsettings.xml

(2013-08-25, 02:42)Squall13 Wrote:

(2013-08-24, 19:04)misa Wrote: Try to remove <guires>1080 or 720</guires> from advancedsettings.xml

Hi there.

I tried that and it still reverts back to it's default settings (deformed) when I restart the thing.

Does guisettings.xml have anything to do with this? I came to an advice on the previous thread that I should delete it. I deleted it, and it looked fine. Made some adjustments on the overscan then when I restarted it it was messed up again.

How about config.txt? I remember one time that I should be changing gpu_mem in there somewhere depending on if its a 256 or 512 Pi.

(2013-08-25, 00:38)doveman2 Wrote: Ah, I see it affects XBMC completely and shows the wrong time on Home and in the EPG (i.e. it shows the current programme as the one that was on an hour ago) and not just the log

(2013-08-25, 12:28)popcornmix Wrote:

(2013-08-25, 00:38)doveman2 Wrote: Ah, I see it affects XBMC completely and shows the wrong time on Home and in the EPG (i.e. it shows the current programme as the one that was on an hour ago) and not just the log

Just edit advancedsettings.xml and add the correct timezone information. E.g. I use:

Code:

<locale>
        <country>UK (24h)</country>
        <language>English</language>
        <timezone>Europe/London</timezone>
        <timezonecountry>Britain (UK)</timezonecountry>
    </locale>

That will fix the time. Not sure why setting this in the gui is broken in gotham builds.

(2013-08-25, 13:18)evanspae Wrote: I included advanced settings above in earlier 21-08 build and it did work, but it does not fix time as used by log etc.
Because of guisettings issues above I have reverted back to a more stable Frodo build, however during latest Gotham 24-08 tests I have feeling even with above locale entry XBMC displayed clock was still wrong?? Could this be also overwritten in guisettings?

(2013-08-25, 13:30)popcornmix Wrote: advancedsettings should trump guisettings. My clock is correct with those settings in advancedsettings.
However I don't understand setting the timezone from the gui does not work.
It would be useul to determine where the problem lies. I'd like to know if:
raspmbc nightly (gotham) build has the same timezone bug
xbmc nightly gothman build on windows has the same timezone bug
xbmc nightly gotham build on openelec on PI has the same timezone bug

If it affects all platforms, then a trac ticket should be submitted. If it only affects openelec or Pi, then we need to investigate why that is.

(2013-08-25, 13:56)rbej Wrote: Updated Gotham Branch
- added some Xbmc patches from internet