(01-25-2018, 12:09 AM)MayImilae Wrote: [ -> ]What file is it? That's a critical detail toward finding out what's causing it!
I have no clue. That comment was more of a thinking out loud moment. Lol. I would have to record the file size of every file just after unzip and check them when the slowdown appears.
(01-24-2018, 09:07 PM)mstreurman Wrote: [ -> ]Have you tried making sure all applications you are not using (e.g. everything but Dolphin) are closed?
Did you check if maybe a Virus Scan, Defrag or other intensive application starts after 2 hours?
Did you turn off Virtual Memory/Pagefile or set it to anything different than "let windows decide"?
Do you have at least 20GB of free space on your C:\-drive and do you have enough free space (2-4GB) on the drive where your Dolphin Emulator settings folder is located (if you do not use a portable.txt it is on your c-drive so it comes on top of the 20GB free space)?
Why C:\-drive 20GB? 8GB Windows Hibernate file + 8GB Windows Pagefile + nVidia Shadercache folder + Dolphin Emulator folder (where also the dolphin shadercache is).
I have about 40GB of space, plus 8GB of virtual ram on BOTH of my hdd, plus a 32GB mSata SSD for page filing as well. And as far as a ruining program goes, I've checked task manager many times and see nothing using anymore resources than they did when I started.
(01-25-2018, 04:37 AM)buzzkillbob Wrote: [ -> ]I have no clue. That comment was more of a thinking out loud moment. Lol. I would have to record the file size of every file just after unzip and check them when the slowdown appears.
I played again today until the slowdown and checked ALL files within the main folder I extracted dolphin to and the dolphin folder in My Documents and i couldnt find and overly sized files. The biggest one was the .exe for dolphin itself. so im not sure exactly what file it could be.
(01-26-2018, 01:25 PM)buzzkillbob Wrote: [ -> ]I played again today until the slowdown and checked ALL files within the main folder I extracted dolphin to and the dolphin folder in My Documents and i couldnt find and overly sized files. The biggest one was the .exe for dolphin itself. so im not sure exactly what file it could be.
Does the issue also return when you just delete the User settings folder (%userprofile%\Dolphin Emulator) and put a portable.txt next to the dolphin.exe file?
(01-26-2018, 07:49 PM)mstreurman Wrote: [ -> ]Does the issue also return when you just delete the User settings folder (%userprofile%\Dolphin Emulator) and put a portable.txt next to the dolphin.exe file?
I'm not sure. I'll give that a try tonight.
(01-26-2018, 07:49 PM)mstreurman Wrote: [ -> ]Does the issue also return when you just delete the User settings folder (%userprofile%\Dolphin Emulator) and put a portable.txt next to the dolphin.exe file?
Exactly which file/folder is the one i should try deleting? Im in the middle of a slow down and would like to try your suggestion to see if it makes an immediate difference.
(01-27-2018, 11:17 AM)buzzkillbob Wrote: [ -> ]Exactly which file/folder is the one i should try deleting? Im in the middle of a slow down and would like to try your suggestion to see if it makes an immediate difference.
The whole top folder (or just rename it to anything else if you don't want to lose any savegames.) So "Dolphin Emulator"
Also, have you tried waiting a day to play the game again and see if the slowdown is still there?
(01-29-2018, 06:11 PM)mstreurman Wrote: [ -> ]The whole top folder (or just rename it to anything else if you don't want to lose any savegames.) So "Dolphin Emulator"
Also, have you tried waiting a day to play the game again and see if the slowdown is still there?
It has currently been 48 hours since i have had the time to boot it to see how it runs. I will pause this reply to see how it runs...
The slowdown still exists after the 48 hours. Just played for about 15 minutes moving from the phazon mines to overworld via the water path. However,the slowdown only existed in a few places of the water path itself. Music slowed down,frames dropped,and the save station door took about 6 seconds to open with choppy audio and low fps during that time. I saved the game,then closed to add to this.(I am saving this message as a draft and closing my browser each time so firefox isnt taking up ANY resources.) Im about to try your suggestion of renaming/moving the file.
Yes,the slowdown still exists even after renaming the folder from my documents and creating a portable.txt file in the same location as my dolphin.exe file. the ONLY thing i changed was i made a copy of my mem card so i could load from the same location and revisit the area that game me prior trouble and it played the same as before. Im going to do another quick wipe/reinstall and see if it helps once more...
Reinstalled and working just fine. Every fresh start after install causes a few hiccups during the first few minutes of gameplay as if its building a texture cache,but then it goes away after a bit with only common micro-stutters throughout the game until it seems like it hit a wall and cant load anymore. A strange band-aid i found is to LOWER the emulated cpu clock. that makes it run a bit smoother for a bit but eventually even that ends up not helping.
If there are any files i can send you,i have backed up my last two installs to my ext hdd in case the missing puzzle piece is in them. I backed up both my install directory and the folder from my documents.
The only thing i can speculate is its a texture cache issue. I have had it happen with early CEMU emulator builds when running Breath of the Wild. Beyond that,I am a self taught computer nerd so my knowledge isnt college worthy at this time. Im all ears to any other suggestions you might have.
(01-29-2018, 08:29 PM)buzzkillbob Wrote: [ -> ]It has currently been 48 hours since i have had the time to boot it to see how it runs. I will pause this reply to see how it runs...
The slowdown still exists after the 48 hours. Just played for about 15 minutes moving from the phazon mines to overworld via the water path. However,the slowdown only existed in a few places of the water path itself. Music slowed down,frames dropped,and the save station door took about 6 seconds to open with choppy audio and low fps during that time. I saved the game,then closed to add to this.(I am saving this message as a draft and closing my browser each time so firefox isnt taking up ANY resources.) Im about to try your suggestion of renaming/moving the file.
Yes,the slowdown still exists even after renaming the folder from my documents and creating a portable.txt file in the same location as my dolphin.exe file. the ONLY thing i changed was i made a copy of my mem card so i could load from the same location and revisit the area that game me prior trouble and it played the same as before. Im going to do another quick wipe/reinstall and see if it helps once more...
Reinstalled and working just fine. Every fresh start after install causes a few hiccups during the first few minutes of gameplay as if its building a texture cache,but then it goes away after a bit with only common micro-stutters throughout the game until it seems like it hit a wall and cant load anymore. A strange band-aid i found is to LOWER the emulated cpu clock. that makes it run a bit smoother for a bit but eventually even that ends up not helping.
If there are any files i can send you,i have backed up my last two installs to my ext hdd in case the missing puzzle piece is in them. I backed up both my install directory and the folder from my documents.
The only thing i can speculate is its a texture cache issue. I have had it happen with early CEMU emulator builds when running Breath of the Wild. Beyond that,I am a self taught computer nerd so my knowledge isnt college worthy at this time. Im all ears to any other suggestions you might have.
Shadercache stutter can be avoided by using Ubershaders (Hybrid or Exclusive) just keep in mind that it is much more taxing on your GPU than without Ubershaders so start out at low IR and build up until it starts slowing down again.
If you use Ubershaders on an nVidia GPU, keep in mind to set your backend to DX11 otherwise you will experience stutters because of the way OpenGL and Vulkan works in the nVidia drivers.
Hybrid Ubershaders create the whole NGC/WII GPU in shaders first and then start compiling specific shaders for your setup and use those (faster) shaders when they are called for
Exclusive Ubershaders does the same without compiling setup specific shaders and just always running the "real NGC/WII GPU" keep in mind that this is "slow"
(Any dev can correct me if I'm wrong)
On another note: If you are using CEMU as well, are you sure you didn't make your nVidia shader cache read only which might cause shader compilation issues for Dolphin? (I have seen that as a fix for slower systems in the CEMU forums)
(01-29-2018, 09:37 PM)mstreurman Wrote: [ -> ]Shadercache stutter can be avoided by using Ubershaders (Hybrid or Exclusive) just keep in mind that it is much more taxing on your GPU than without Ubershaders so start out at low IR and build up until it starts slowing down again. If you use Ubershaders on an nVidia GPU, keep in mind to set your backend to DX11 otherwise you will experience stutters because of the way OpenGL and Vulkan works in the nVidia drivers.
Hybrid Ubershaders create the whole NGC/WII GPU in shaders first and then start compiling specific shaders for your setup and use those (faster) shaders when they are called for
Exclusive Ubershaders does the same without compiling setup specific shaders and just always running the "real NGC/WII GPU" keep in mind that this is "slow"
(Any dev can correct me if I'm wrong)
On another note: If you are using CEMU as well, are you sure you didn't make your nVidia shader cache read only which might cause shader compilation issues for Dolphin? (I have seen that as a fix for slower systems in the CEMU forums)
As far as ubershaders go,keep in mind im running dolphin 4.0 which i dont believe has an ubershader option. And in the recent few updates regarding CEMU,the shader cache issue has been fixed on my end and i have returned everything changed from earlier releases to normal prior to messing with dolphin again. But even if it is a shader cache issue with dolphin,wouldnt there be a file within one of the dolphin folders that would continue to grow as i played so that i could "watch" the cache build to the point of causing a slowdown?