Yet again you argue with unscientific behavior like "boy", "capisci", etc. and make up claims that you can not substantiate and are false (especially those about me, as well as the topic at hand).
Like I wrote (and you have proven)... You will endlessly argue and resort to nonsense tactics to discredit someone who simply tells you the facts.
Are you capable to stay to the facts?
Since your assumed cause is false to begin with, your "workarounds" are no guarantee to work either.
The tests the guy did are ALL related to lower bandwidth needed on EE-RAM to VRAM transfers and he has just provided more evidence for what we know since 2018.
The ART is NOT "transfered from a port to VRAM" either, but "transfered from a port to EE-RAM, CACHED THERE, transfered to VRAM 180 times per second on a 60Hz 3-pass rendering High resolution mode".
I did not commit any logical fallacy contrary to you, but shared the facts that you deny like predicted.
EE-RAM to VRAM transfer shortage due to overflowing VRAM is the cause and I bet that some like @Maximus32, @Tupakaveli, @Krah, @El_isra and others which comprehend and know the software backend (because they used, improved or coded parts of it) and how the hardware works, would confirm that.
Even those who have a problem with me - like you apparently have - would not disagree with these FACTS. @HWNJ for example...
Mind looking at some tests which can absolutely prove that, like a UHD-Texturing-test with a 64x64 multimapped texture, where the device would be fast enough?
I agree with you.you have bad reading comprehension boy.
I do not agree with that thing you call facts.Even those who have a problem with me - like you apparently have - would not disagree with these FACTS. @HWNJ for example...
Oh, by the way, this is abuse of power. I'm reporting you on that.You are spamming again! Warning!![]()
Nah, you did exactly what any developer would appreciate - you reported bugs!I feel kind of sorry that a minor inconvenience on my end caused such a heated discussion among you guys. As an end-user with no clues about coding and no deep understanding of the PS2 hardware architecture, I can´t add anything substantial to the discussion or even decide whose approach to finding a solution might be correct. But judging the choice of words within this discussion is well in scope of what I can do and I gotta say some people come along as more reasonable, sympathetic and trustworthy than others...
What version of OPL are you using?Hi. Is there a fix to Power Off via OPL? After pressing OK to confirm powering off via START menu using this theme, it froze the screen and is not powering off.
What version of OPL are you using?
What resolution are you set to?
Is your ART JPG, PNG, or both?
Does it occur on other themes?
Does it occur with no themes?
I will try to resolve this issue if I can, based on the answers to these questions![]()
Yes, that's it. Tested here and with BGM off, the Power Off works normally with your theme.I would try with BGM off to see if it makes any difference.
Beyond that, I'll have to wait for some input on what I could change to lighten the load - assuming thats the issue