GUI hangs when switching tv channel in fullscreen (1 Viewer)

[thesystemera]

Okay are we all using Vista and are we all using ATI Catalyst Drivers... And what versions... Oh and motherboard

Me.. ATI Catalyst 9.4 - MA-GA78GM Motherboard - Vista SP.1

 

[nikos1671]

ATI Catalyst 9.4 - MA-GA78GM Motherboard - Vista SP.2
now i have install catalyst 9.5 i will test and report back

 

[helsten2]

I installed Catalyst 9.5 this evening. Not seen the error yet. And I've been trying hard ....

 

[nikos1671]

here no luck with the new catalyst,i get again this error ,try to play with the info button and the back very fast on your remote a couple of times.....

 

[thesystemera]

I think we finally might have some attention on this issue... Just been talking to Simone, should be joining us soon

 

[nikos1671]

any news??any progress on this??

 

[verolano]

Same problem on my htpc with windows XP and NVidia 7600GS card.
video frezes on channel change, only audio is present and system is out of control. After forced reboot ,video drivers seems corrupted.

This happened after the upgrade to 1.0.2 version.


Ciao
pg

 

[nikos1671]

Guys have you solve this problem or you still suffer???i have make 3 times clean install and i get the same error.

 

[thesystemera]

I resolved by reverting back to 1.01... This is crazy that we have yet to see a developer address or even comment on this... Everyone PM the dev team, at least lets get a look at this, this needs to be bug tracked, we have all provided logs and written in the correct forum.

Lets go...

 

[tourettes]

To get this issue sorted out (no one in team is able to reproduce this, so we need really good information on the different aspects).

• On a quick look, there are multiple different issues in this thread (menu switching & channel switching at least). Please keep those separated, best would be to create two new threads and close this thread as it is pretty messy.
• Everyone should provide complete (and as clean as possible logs), not just the error
• Everyone should provide complete system information, not all have published such

There were zero rendering related changes between 1.0.1 and 1.0.2 so it seems pretty odd that this kind of error would have been introduced in 1.0.2. So take care and make sure that you cannot reproduce the error in anyway with the 1.0.1.