Emulator Issues #6572
closedEFB access cache needs to be moved to VideoCommon
0%
Description
Currently it's only in GL because I didn't knew what I was doing when I implemented it.
Updated by delroth about 11 years ago
Issue 6571 has been merged into this issue.
Updated by delroth about 11 years ago
Issue 6553 has been merged into this issue.
Updated by delroth about 11 years ago
Issue 6553 has been merged into this issue.
Updated by rodolfoosvaldobogado about 11 years ago
Your idea of the peek cache is excellent, when it is moved to common code what do you think about doing the cache check in the cpu thread, in VideoBackendHardware::Video_AccessEFB, that way we can save some wait time?
Updated by delroth about 11 years ago
I already have a patch that does this, actually :) Couldn't measure any performance impact, but in theory it should help. That's definitely a good thing to have when we will have a common peek cache.
Updated by delroth about 11 years ago
- Milestone changed from Next to Current
4.0 was released, moving Milestone-Next to Milestone-Current.
Updated by delroth over 10 years ago
- Milestone changed from Current to Next
Moving to next milestone since these issues are not critical to a new release.
If you feel strongly about this issue and want it to block the next Dolphin release, please assign yourself as owner and re-add Milestone-Current.
Updated by JMC4789 about 10 years ago
Issue 6275 has been merged into this issue.
Updated by JMC4789 almost 10 years ago
Issue 8252 has been merged into this issue.
Updated by degasus over 9 years ago
Renaming to relect that this cache should also be updated on EFB pokes.
Moving it to the CPU thread will be important as eg Monster Hunter Tri uses peeks & pokes for image manipulation. So all of this will stay on the CPU.
Updated by JMC4789 almost 9 years ago
This isn't fixing this issue, but, it can be implemented in all the hardware backends in https://github.com/dolphin-emu/dolphin/pull/3652
It's actually even better in the new one implemented, providing superior performance.
Updated by JosJuice over 8 years ago
- Milestone changed from Next to Current
5.0 was released, moving Milestone-Next to Milestone-Current.
Updated by JosJuice over 5 years ago
- Status changed from Accepted to Fixed
- Fixed in set to 5.0-9638