The cache will only get so big. An ever increasing cache is the size of a memory leak. Plus, more cache means it can load faster in Dolphin, so it's not a slowdown but a speedup
4.0 runs better than 5.xxx????
|
01-30-2018, 03:38 PM
(01-30-2018, 01:01 PM)KHg8m3r Wrote: The cache will only get so big. An ever increasing cache is the size of a memory leak. Plus, more cache means it can load faster in Dolphin, so it's not a slowdown but a speedup If there is no limit to the size of it,then for a computer thats not the latest,fastest,most gb and mhz possible,it IS a slowdown because of hardware limitations. But even with that said,a texture cache should be dumped into ram of some sort,be it system memory or gpu memory,therefore it should also be able to be monitored through task manager (system memory) and Nvidia Inspector (GPU memory) which is not the case for this issue. In between the fresh dolphin install and the slowdown after 2-ish hours of gameplay,there is no noticable difference in resource usage across the board that would help to pinpoint the cause of whatever is making my game lag out of nowhere. 01-30-2018, 04:14 PM
I explained it in a confusing way, but the cache is limited in how big it can get, which is based on the number of unique ways a game can do something with graphics (read the blog post on ubershaders for a more detailed explanation of that).
And it doesn't really get "loaded" anywhere, it just exists and is used in real time. Here's the super short explanation: Dolphin runs a game for the first time and the game requests graphic option X. Dolphin generates X from scratch and saves it to the cache and loads it to the screen (this is slow). The next time the game requests X, Dolphin just loads the cached version (very fast). Even reading data from a hard disk is faster than generating it on the fly. Since it's not really loaded until it's used inside Dolphin, outside inspector tools can't differentiate generated X from cached X. Now, you state this slowdown happens when playing version 4.0 for a certain amount of time, but that playing 5.0 and dev builds is just bad. However, what wasn't clear from your posts is if you cleared the Dolphin Emulator global files but saved the memory card to test the 5.0 and dev builds in a totally clean environment. 01-30-2018, 04:19 PM
Please don't keep deleting your shader cache. We cache because it's faster by order of magnitude.
01-30-2018, 06:06 PM
(01-30-2018, 12:27 PM)buzzkillbob Wrote: As far as ubershaders go,keep in mind im running dolphin 4.0 which i dont believe has an ubershader option. If you're not at least kepp running Dolphin 5.0 stable then... good luck with support because only 5.0 and the latest devbuilds are supported, so it's better to keep using the latest devbuild and try to use the Ubershaders on Hybrid with DX11.
Check my profile for up to date specs.
01-30-2018, 06:35 PM
(01-30-2018, 06:06 PM)mstreurman Wrote: If you're not at least kepp running Dolphin 5.0 stable then... good luck with support because only 5.0 and the latest devbuilds are supported, so it's better to keep using the latest devbuild and try to use the Ubershaders on Hybrid with DX11. Anything beyond 4.0 runs like dirt with metroid prime. That's why I'm still on 4.0. I've tried 5, and a few of the other builds and I get a max of 45 fps and it's too sluggish to play. 01-30-2018, 07:10 PM
(This post was last modified: 01-30-2018, 07:11 PM by mstreurman.)
(01-30-2018, 06:35 PM)buzzkillbob Wrote: Anything beyond 4.0 runs like dirt with metroid prime. That's why I'm still on 4.0. I've tried 5, and a few of the other builds and I get a max of 45 fps and it's too sluggish to play. Then I guess your laptop is not fast enough to run Metroid without any issues. You must get used to the shaderstutters because Metroid is one of those games that has them very noticably, they will go away in time though because it will build up a working shadercache. The max of 45FPS: I guess that is at 1x IR... make sure VSYNC is off though.
Check my profile for up to date specs.
02-02-2018, 06:41 PM
(01-30-2018, 07:10 PM)mstreurman Wrote: Then I guess your laptop is not fast enough to run Metroid without any issues. You must get used to the shaderstutters because Metroid is one of those games that has them very noticably, they will go away in time though because it will build up a working shadercache. The game runs like a charm at 1.5x ir, 60 fps on 4.0 the issue is after 2 hours or so, it starts lagging beyond playability. The micro microstutters don't bother me that bad as long as I'm at a solid 60 fps. But the slowdown is what keeps me from a straight playthrough 02-02-2018, 09:37 PM
If you have no interest in using newer builds due to performance concerns, that's fine. But we're not going to bother with giving support for an ancient build either.
|
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)