I've had dump textures turned on for a while. For the most part I haven't had problems with it in the past, but today, when I went to look at what I have, I realized my directory has hundreds of thousands of files.
There are two problems right now with dump textures, one of which is new:
What I'd really/also like is the ability to provide a list of sizes to exclude from being dumped. This would at least allow working around #1 by blacklisting the relevant sizes, and could also be used to help out with #2 by avoiding dumping of video frames (which tend to also be unusual sizes). Plus I'm not interested in the video frames, anyway...
Also, is there a way to avoid dumping mip levels?
There are two problems right now with dump textures, one of which is new:
- EFB's are being dumped even though I didn't ask for them.
- This is why I have oodles of textures. Moreover, I know that they're from the EFB because they're obviously from doing bloom effects (i.e. they look like game screens and not "real" textures), and I don't get said effects in EFB to RAM (which is a separate bug, although a potentially useful one). Also because games run MUCH faster (I can generally get 60 VPS, vs. 20-40 VPS) with EFB to RAM, probably because dolphin isn't trying to write out textures to disk every frame.
- This is why I have oodles of textures. Moreover, I know that they're from the EFB because they're obviously from doing bloom effects (i.e. they look like game screens and not "real" textures), and I don't get said effects in EFB to RAM (which is a separate bug, although a potentially useful one). Also because games run MUCH faster (I can generally get 60 VPS, vs. 20-40 VPS) with EFB to RAM, probably because dolphin isn't trying to write out textures to disk every frame.
- Videos are really slow and frequently "corrupted".
- By "corrupted", I mean they are full of the sorts of artifacts you'd see from a really low bitrate video. Both issues happen only with dump textures turned on (if not perfect, at least they are much faster and with fewer/no artifacts). The artifacting might be because the emulated code "sees" that it is running really slowly and takes shortcuts in the decoding, i.e. I suspect it is not a bug as such but a result in some manner of the poor performance.
- By "corrupted", I mean they are full of the sorts of artifacts you'd see from a really low bitrate video. Both issues happen only with dump textures turned on (if not perfect, at least they are much faster and with fewer/no artifacts). The artifacting might be because the emulated code "sees" that it is running really slowly and takes shortcuts in the decoding, i.e. I suspect it is not a bug as such but a result in some manner of the poor performance.
What I'd really/also like is the ability to provide a list of sizes to exclude from being dumped. This would at least allow working around #1 by blacklisting the relevant sizes, and could also be used to help out with #2 by avoiding dumping of video frames (which tend to also be unusual sizes). Plus I'm not interested in the video frames, anyway...
Also, is there a way to avoid dumping mip levels?