solvise/Ryujinx

Fork 0

forked from Mirror/Ryujinx

Commit graph

Author	SHA1	Message	Date
riperiperi	10e17ab423	Only use persistent buffers to flush on NVIDIA and Windows+AMD (#2489 ) It seems like this method of flushing data is much slower on Mesa drivers, and slightly slower on Intel Windows. Have not tested Intel Mesa, but I'm assuming it is the same as AMD. This also adds vendor detection for AMD on Unix, which counted as "Unknown" before.	2021-07-18 11:45:50 -03:00
riperiperi	ca5ac37cd6	Flush buffers and texture data through a persistent mapped buffer. (#2481 ) * Use persistent buffers to flush texture data * Flush buffers via copy to persistent buffers. * Log error when timing out, small refactoring.	2021-07-16 18:10:20 -03:00

Author

SHA1

Message

Date

riperiperi

10e17ab423

Only use persistent buffers to flush on NVIDIA and Windows+AMD (#2489 )

It seems like this method of flushing data is much slower on Mesa drivers, and slightly slower on Intel Windows. Have not tested Intel Mesa, but I'm assuming it is the same as AMD.

This also adds vendor detection for AMD on Unix, which counted as "Unknown" before.

2021-07-18 11:45:50 -03:00

riperiperi

ca5ac37cd6

Flush buffers and texture data through a persistent mapped buffer. (#2481 )

* Use persistent buffers to flush texture data

* Flush buffers via copy to persistent buffers.

* Log error when timing out, small refactoring.

2021-07-16 18:10:20 -03:00

2 commits