c52158b733
* Add timestamp to 16-byte semaphore releases. BOTW was reading a ulong 8 bytes after a semaphore return. Turns out this is the timestamp it was trying to do performance calculation with, so I've made it write when necessary. This mode was also added to the DMA semaphore I added recently, as it is required by a few games. (i think quake?) The timestamp code has been moved to GPU context. Check other games with an unusually low framerate cap or dynamic resolution to see if they have improved. * Cast dma semaphore payload to ulong to fill the space * Write timestamp first Might be just worrying too much, but we don't want the applcation reading timestamp if it sees the payload before timestamp is written. |
||
|---|---|---|
| .. | ||
| CompressedMethod.cs | ||
| GPEntry.cs | ||
| GPFifoClass.cs | ||
| GPFifoClassState.cs | ||
| GPFifoDevice.cs | ||
| GPFifoProcessor.cs | ||