Ok be honest, which is most painful? :)
-
-
-
Right now CA is causing me a lot of grief due to CARenderer (yeah yeah I know, but we can’t ship Metal yet), but I think they’re all about equally problematic in different ways.
-
Do the other ones handle offscreen rendering differently? (truly don’t know)
-
I’m about to find out! :)
-
This is for integration testing, BTW, so I could in theory just give up, but I do want some kind of automated testing here…
-
Is rendering to a window and screenshot-ing impractical? I wouldn’t be surprised if CARenderer gives surprising results sometimes…
-
I tried that, but I had synchronization issues when trying to use Quartz Window Services for that. It didn’t flush in time and I would have had to add sleep(3) :(
-
Ah hm. I take it you’re doing stuff that doesn’t work with -[CALayer drawInContext:]?
- 1 more reply
New conversation -
-
-
"Qualcomm GPU drivers" is like several layers of horrifying. ... why does Qualcomm even *have* a GPU?!
-
Unfortunately, as you probably already know, phones
-
I thought it's Mali
-
Adreno is Qualcomm’s GPU. Adreno 200 was barely functional at all.
-
I thought that's the normal state of GPUs.
-
AMD sold them their mobile GPU division which is why Adreno is an anagram of Radeon. It used to have a lot of internal memory corruption bugs in the firmware spamming IOMMU tracebacks to the kernel log.
@ScottyBauer1 -
My favorite one was that in their Adreno 200 driver, glTexSubImage2D() just did “return glTexImage2D(…)” with the arguments it was given, ignoring x and y. Yes, this usually led to segfaults.
-
incredible
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.