[evanspae]

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.

There is obviously still a bug here (I think it looks as if its an XBMC Gotham one with menu restructures) and we will have to wait for developers to sort. Config.txt will not sort this as guisettings are being overwritten on each reboot.. its becoming a real showstopper preventing latest Gotham from daily usage. We will have to be patient. Most of the earlier issues of buffering and DTS, Dolby HD etc are looking good.

Thanks to all for progress todate keep up the good work. The eternal problem here is the better the solution being offered... the more we want from it!

I understand sir if it is a bug or some sort and I appreciate all these people have done for the project. but it looks like I'm the only one with the problem so it must have been something I've done lol. The last people that had the same problem that I have googled was back in 2012 so I think it's safe to assume that no one here currently is having said issue.

This is a bug both I and doveman2 and others have posted on this see posts #438, #449 and #450.
According to XBMC wiki it should be possible to cut and paste desired guisettings into advancedsettings which should then take precedence. This works for the locale time settings but I have tried this approach with resolution and pixel ratio and other settings with no joy. If the Pi is rebooted I am back to square one (or should I say 0.5 pixel ratio!) with the same problem as you and others.