• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Support v
« Previous 1 ... 645 646 647 648 649 ... 1197 Next »

Texture Cache, EFB, how it works?
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Texture Cache, EFB, how it works?
04-28-2013, 02:39 PM
#1
Qaazavaca Qaanic
Unregistered
 
Does texture cache accuracy matter when efb -> ram, or when it's to texture, or both? Or does it only matter when it's cached?
And will setting EFB to Tex affect anything negatively? As in: are there any bugs that require setting it to ram, but it's not specified in the game INI?
Reply
04-28-2013, 03:04 PM (This post was last modified: 04-28-2013, 03:07 PM by Shonumi.)
#2
Shonumi Offline
Linux User/Tester
**********
Administrators
Posts: 6,513
Threads: 55
Joined: Dec 2011
neobrain gave me this post of his a while ago, it's about the Texture Cache: http://forums.dolphin-emu.org/Thread-safe-texture-cache-is-not-in-newer-revs?pid=164693#pid164693

From what I can tell, Dolphin does not use texture caching with EFB -> RAM unless Enable Cache is checked. Texture caching should improve performance over having to decode a texture from the emulated RAM every single time the game wants to use a texture, so naturally enabling caching boosts the speed with EFB -> RAM. However, you can introduce texture inaccuracies if the hash used by the texture cache doesn't indicate to Dolphin that a texture has recently changed (when in fact it has changed), so it affects both EFB -> Texture and EFB -> RAM with Cache enabled.

A note to any passing dev (yo neobrain) please correct me if I'm wrong. This topic specifically and recently came up in discussions about the Dolphin manual, and we need that to be as accurate as possible.

There are some games where EFB -> RAM might not be the default, simply because the graphical issues are minor (not gamebreaking) and the fact that EFB -> RAM is demanding for some systems. One example, iirc, would be NSMB (see the wiki for info about the Blue Coins). You can play the game just fine with EFB -> Texture, but because of the performance cost of EFB -> RAM and the fact that Texture does a fine enough job, it's not the default in the .ini. I haven't updated my .inis in a while though, so it may have changed.

At any rate, look at the wiki for each game if you want a complete idea of what needs RAM and what can be left alone on Texture. Generally, most games are fine with Texture, but you should look up those that aren't.
Website Find
Reply
04-28-2013, 06:33 PM
#3
neobrain Offline
"Wow, I made my code 1000x faster! That means I can make it 2048x slower now!"
**********
Developers (Some Administrators and Super Moderators)
Posts: 3,208
Threads: 50
Joined: Jun 2009
Of course texture caching is used when efb to ram is enabled. It doesn't apply to EFB copies (unless caching is enabled), but it does apply to regular textures.
My blog
Me on Twitter
My wishlist on Amazon.de
Find
Reply
04-29-2013, 02:02 AM
#4
Qaazavaca Qaanic
Unregistered
 
OK got it.
And why has my system slowed down over the last thousand revisions to the point where my 4.0 ghz i5 and nvidia 660 can't play Mario Kart at full speed with EFB to RAM on any vid backend? Is that opt more demanding on mem or CPU speed?
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode