The following warnings occurred: | |||||||||||||||
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.2.28 (Linux)
|
![]() |
New AMD/ATI drivers bug identified: workaround in r2015 - Printable Version +- EmuNewz Network (https://www.emunewz.net/forum) +-- Forum: PSP Emulation (https://www.emunewz.net/forum/forumdisplay.php?fid=191) +--- Forum: JPCSP Official Forum (https://www.emunewz.net/forum/forumdisplay.php?fid=51) +---- Forum: svn trunk discussion (https://www.emunewz.net/forum/forumdisplay.php?fid=56) +---- Thread: New AMD/ATI drivers bug identified: workaround in r2015 (/showthread.php?tid=3894) |
New AMD/ATI drivers bug identified: workaround in r2015 - gid15 - 03-12-2011 I've identified a new AMD/ATI driver bug when enabling shaders. A workaround has been implemented in r2015: to activate the workaround, the option "Enable dynamic shader generation" has to be selected. The workaround has been tested on different Catalyst versions (thanks to Darth for alpha-testing!): - Catalyst 11.2: this version is bringing new bugs, even when shaders are not activated. Not recommended. - Catalyst 11.1: the workaround is bringing some improvements in this version, but it is far from being perfect. You might experience different results depending on the tested application. - Catalyst 10.9: not thoroughly tested, but the workaround seems to bring the most significant improvements in this version. You can provide feedback when testing r2015 with AMD/ATI shaders in this thread. Please always provide a log file and screenshots, this might help me improving the support for AMD graphic cards. AMD will probably soon release a Catalyst 11.3, let's see if this one brings new improvements... RE: New AMD/ATI drivers bug identified: workaround in r2015 - luckwii - 03-12-2011 Sorry, no time to post the logs right now. But shaders had started to halfway work with my Intel HD gpu due to changes in rev 2012. I could see the health, stats etc. but no image in games like Ghosts N' Goblins. Now with the 2015, that is broken again. Games won't load. RE: New AMD/ATI drivers bug identified: workaround in r2015 - Game - 03-12-2011 Tested F.F.Tactics with r2015. Using Catalyst 10.12. It looks like this with shaders enabled,it's the same with dynamic shader enabled.FPS are bigger since it's not rendering background,I mean textures are a mess. http://img855.imageshack.us/i/fftactics.png/ Log: Handler 0x0883C840(0x08BAF6DC) 81063 [xpLibSpu] DEBUG hle - Alarm returned value 4166 81078 [xpLibSpu] DEBUG hle.ThreadManForUser - New Schedule for Alarm uid=34: 109832558 81078 [xpLibSpu] DEBUG hle.ThreadManForUser - End of Interrupt 81078 [xpLibSpu] DEBUG hle - Calling Timer uid=34, now=109837557 81078 [xpLibSpu] DEBUG hle.ThreadManForUser - Triggering Interrupt SYSTIMER0(0xF) at 0x0883C840 81078 [xpLibSpu] DEBUG hle.ThreadManForUser - Calling InterruptHandler 0x0883C840(0x08BAF6DC) 81078 [xpLibSpu] DEBUG hle - Alarm returned value 4166 81078 [xpLibSpu] DEBUG hle.ThreadManForUser - New Schedule for Alarm uid=34: 109841723 81078 [xpLibSpu] DEBUG hle.ThreadManForUser - End of Interrupt 81078 [xpLibSpu] DEBUG hle - Calling Timer uid=34, now=109847584 81078 [xpLibSpu] DEBUG hle.ThreadManForUser - Triggering Interrupt SYSTIMER0(0xF) at 0x0883C840 81094 [xpLibSpu] DEBUG hle.ThreadManForUser - Calling InterruptHandler 0x0883C840(0x08BAF6DC) 81094 [xpLibSpu] DEBUG hle - Alarm returned value 4166 81094 [xpLibSpu] DEBUG hle.ThreadManForUser - New Schedule for Alarm uid=34: 109851750 81094 [xpLibSpu] DEBUG hle.ThreadManForUser - End of Interrupt 81094 [xpLibSpu] DEBUG hle - Calling Timer uid=34, now=109856976 81094 [xpLibSpu] DEBUG hle.ThreadManForUser - Triggering Interrupt SYSTIMER0(0xF) at 0x0883C840 81094 [xpLibSpu] DEBUG hle.ThreadManForUser - Calling InterruptHandler 0x0883C840(0x08BAF6DC) 81094 [xpLibSpu] DEBUG hle - Alarm returned value 4166 81094 [xpLibSpu] DEBUG hle.ThreadManForUser - New Schedule for Alarm uid=34: 109861142 81094 [xpLibSpu] DEBUG hle.ThreadManForUser - End of Interrupt 81110 [xpLibSpu] DEBUG hle - Calling Timer uid=34, now=109865484 81110 [xpLibSpu] DEBUG hle.ThreadManForUser - Triggering Interrupt SYSTIMER0(0xF) at 0x0883C840 81110 [xpLibSpu] DEBUG hle.ThreadManForUser - Calling InterruptHandler 0x0883C840(0x08BAF6DC) 81110 [xpLibSpu] DEBUG hle - Alarm returned value 4166 81110 [xpLibSpu] DEBUG hle.ThreadManForUser - New Schedule for Alarm uid=34: 109869650 81110 [xpLibSpu] DEBUG hle.ThreadManForUser - End of Interrupt 81110 [xpLibSpu] DEBUG hle - Calling Timer uid=34, now=109874807 81110 [xpLibSpu] DEBUG hle.ThreadManForUser - Triggering Interrupt SYSTIMER0(0xF) at 0x0883C840 81110 [xpLibSpu] DEBUG hle.ThreadManForUser - Calling InterruptHandler 0x0883C840(0x08BAF6DC) 81110 [xpLibSpu] DEBUG hle - Alarm returned value 4166 81125 [xpLibSpu] DEBUG hle.ThreadManForUser - New Schedule for Alarm uid=34: 109878973 81125 [xpLibSpu] DEBUG hle.ThreadManForUser - End of Interrupt 81125 [xpLibSpu] DEBUG hle - Calling Timer uid=34, now=109884823 81125 [xpLibSpu] DEBUG hle.ThreadManForUser - Triggering Interrupt SYSTIMER0(0xF) at 0x0883C840 81125 [xpLibSpu] DEBUG hle.ThreadManForUser - Calling InterruptHandler 0x0883C840(0x08BAF6DC) 81125 [xpLibSpu] DEBUG hle - Alarm returned value 4166 81125 [xpLibSpu] DEBUG hle.ThreadManForUser - New Schedule for Alarm uid=34: 109888989 81125 [xpLibSpu] DEBUG hle.ThreadManForUser - End of Interrupt 81125 [xpLibSpu] DEBUG hle - Calling Timer uid=34, now=109893857 81125 [xpLibSpu] DEBUG hle.ThreadManForUser - Triggering Interrupt SYSTIMER0(0xF) at 0x0883C840 81141 [xpLibSpu] DEBUG hle.ThreadManForUser - Calling InterruptHandler 0x0883C840(0x08BAF6DC) 81141 [xpLibSpu] DEBUG hle - Alarm returned value 4166 81141 [xpLibSpu] DEBUG hle.ThreadManForUser - New Schedule for Alarm uid=34: 109898023 81141 [xpLibSpu] DEBUG hle.ThreadManForUser - End of Interrupt 81141 [xpLibSpu] DEBUG hle - Calling Timer uid=34, now=109903064 81141 [xpLibSpu] DEBUG hle.ThreadManForUser - Triggering Interrupt SYSTIMER0(0xF) at 0x0883C840 81141 [xpLibSpu] DEBUG hle.ThreadManForUser - Calling InterruptHandler 0x0883C840(0x08BAF6DC) 81141 [xpLibSpu] DEBUG hle - Alarm returned value 4166 81141 [xpLibSpu] DEBUG hle.ThreadManForUser - New Schedule for Alarm uid=34: 109907230 81141 [xpLibSpu] DEBUG hle.ThreadManForUser - End of Interrupt 81157 [xpLibSpu] DEBUG hle - Calling Timer uid=34, now=109912588 81157 [xpLibSpu] DEBUG hle.ThreadManForUser - Triggering Interrupt SYSTIMER0(0xF) at 0x0883C840 RE: New AMD/ATI drivers bug identified: workaround in r2015 - f0ster - 03-12-2011 Now shaders work fine for crisis core. ![]() RE: New AMD/ATI drivers bug identified: workaround in r2015 - gid15 - 03-12-2011 (03-12-2011, 07:10 PM)f0ster Wrote: Now shaders work fine for crisis core.Which Catalyst version are you using? RE: New AMD/ATI drivers bug identified: workaround in r2015 - beanclr - 03-12-2011 ^ what he said. I hope your not using Nvidia. That would just break my hopes. RE: New AMD/ATI drivers bug identified: workaround in r2015 - f0ster - 03-12-2011 (03-12-2011, 07:34 PM)gid15 Wrote: Which Catalyst version are you using?I using AMD Catalyst 10.12 sorry for bad english) Tested God of War Chains of Olympus RE: New AMD/ATI drivers bug identified: workaround in r2015 - beanclr - 03-12-2011 K downloading it now. RE: New AMD/ATI drivers bug identified: workaround in r2015 - dista_bagus - 03-12-2011 gid15,which log file? INFO/DEBUGGER/ALL? i will try it later with Jpcsp r2015. my VGA ATI Radeon HD3850 512MB => Catalyst 11.2 RE: New AMD/ATI drivers bug identified: workaround in r2015 - beanclr - 03-12-2011 Tried it with 10.12. Still wont work for me. Can someone tell me how to make a log file. So i can upload it. |