Bug is unfortunately not Vulkan specific. We've had members in the discord get it on OpenGL too, although people using OpenGL and also experiencing the bug is uncommon so it makes it seem like it never occurs for that renderer. Also, an updated of Cemu should have fixed some of the performance regressions that occurred on .5, so I don't think that should be mentioned?
One of the fixes you should maybe mention is that it's a random thing, and that saving and reloading that save file usually fixes that problem, or reloading the game. For most people coming across the bug it'll be a perfectly fine fix since it's so rare. Thanks for making the post though, does seem like a lot of people come across this so it might be nice to link to.
>Also, an updated of Cemu should have fixed some of the performance regressions that occurred on .5, so I don't think that should be mentioned?
On 1.24, I get 120fps at Dueling Peaks and 80 in Hateno Village. On 25.4, 25.5 and 25.6, I get 100 and 70 respectively. I've tested this several times over the last few weeks just to make up for any run-to-run variance. Maybe it's just a quirk of my specific system, would love to hear what numbers other people get.
Also, I don't know who is in charge of the guide, but if the bug does happen on OpenGL, then that part in the Troubleshoot section needs to be changed.
Also also, I know I probably should be at least lurking a bit on the discord just to stay in touch with things. I just really really *really* don't like that program...
Ah, that info is from the [cemu.cfw.guide](https://cemu.cfw.guide)? It's not updated that regularly unfortunately since I just don't have time to check or to tell the maintainer what exactly to update.
I've retested it and it does seem to be still there and have raised the issue again. Basically told me that it has to do with Vulkan pipeline barriers, and that an "optimization" meant to add to performance actually caused that regression. Drivers internally do a lot of magic behind the scenes, so I guess this update didn't really improve things.
Reason why I thought it was fixed was due to having helped with a beta version after raising it initially where a certain part of this optimization was reverted, which did fix it for the most part. No clue what happened after that unfortunately, but the fix was kinda buggy when I tested it, so I guess it wasn't ready.
Just want to share my experience in case it helps anyone. Been playing for a month and this bug is anything but infrequent. Every time I enter a new village or area, it comes back. It's my biggest problem with this game. Saving and reloading does not fix the problem. What does work is saving, closing the program, and then reloading. The problem will then be "fixed" for the local area. Once an area is "fixed," it remains that way. Since I've explored most of the map, the problem has become less frequent, but it was definitely frustrating spending the last month periodically quitting and reloading. Nevertheless thanks to developers for allowing us to play this game at high resolution and frame rate.
That might sound strange but manually setting you max fps to 60 in Nvidia control panel helps. At least it did for me. I tried everything to recreate the bug but i couldn't.
I tried it because my fps was spiking up to 65 while loading. Even with vsync.
This could be just a coincidence tho
Yes. Never happened to me again.
1) make sure your graphic packs are updated. (Latest version fixes a lot of inconsistent fps problems)
2) update your cemu to 1.26.1
3) limit your fps to 59 in Nvidia CP. 60 didn't work after latest graphic pack update.
I know this is late but one thing that seemed to have worked for me was capping the FPS at 55 rather than 60. I haven't been able to play much with it yet but so far I haven't run into any physics issues since switching.
i've played at 55fps for about 40 hours and have only run into the problem one time in the Goron general store but rebooting the game fixed the bug. Compared to my hour or so at 60 fps where I ran into the issue multiple times. It seems to have nearly dissolved the issue for me. Of course there are still certain physics based missions where capping the fps at 30 is needed, but i've only had to do that twice.
I actually found a better solution:
\- set FPS++ higher than your display's refresh rate
\- set Vsync to match emulated display
\- get Afterburner + RTSS, and use RTSS to limit the framerate
That way you don't have to deal with the increased input lag of Triple Buffering, while also getting much smoother frametimes than you would with the FPS++ framelimiter.
Good to know! I’ll give that a shot! I haven’t noticed any input lag but I may be chalking that up to the fact I’m rubbish at the game haha.
It was almost unplayable before I put in the first fix. I was getting stuck in invisible water towers every few dozen meters. I would run around with Cryosis permanently so I could try and predict it.
Bug is unfortunately not Vulkan specific. We've had members in the discord get it on OpenGL too, although people using OpenGL and also experiencing the bug is uncommon so it makes it seem like it never occurs for that renderer. Also, an updated of Cemu should have fixed some of the performance regressions that occurred on .5, so I don't think that should be mentioned? One of the fixes you should maybe mention is that it's a random thing, and that saving and reloading that save file usually fixes that problem, or reloading the game. For most people coming across the bug it'll be a perfectly fine fix since it's so rare. Thanks for making the post though, does seem like a lot of people come across this so it might be nice to link to.
>Also, an updated of Cemu should have fixed some of the performance regressions that occurred on .5, so I don't think that should be mentioned? On 1.24, I get 120fps at Dueling Peaks and 80 in Hateno Village. On 25.4, 25.5 and 25.6, I get 100 and 70 respectively. I've tested this several times over the last few weeks just to make up for any run-to-run variance. Maybe it's just a quirk of my specific system, would love to hear what numbers other people get. Also, I don't know who is in charge of the guide, but if the bug does happen on OpenGL, then that part in the Troubleshoot section needs to be changed. Also also, I know I probably should be at least lurking a bit on the discord just to stay in touch with things. I just really really *really* don't like that program...
Ah, that info is from the [cemu.cfw.guide](https://cemu.cfw.guide)? It's not updated that regularly unfortunately since I just don't have time to check or to tell the maintainer what exactly to update. I've retested it and it does seem to be still there and have raised the issue again. Basically told me that it has to do with Vulkan pipeline barriers, and that an "optimization" meant to add to performance actually caused that regression. Drivers internally do a lot of magic behind the scenes, so I guess this update didn't really improve things. Reason why I thought it was fixed was due to having helped with a beta version after raising it initially where a certain part of this optimization was reverted, which did fix it for the most part. No clue what happened after that unfortunately, but the fix was kinda buggy when I tested it, so I guess it wasn't ready.
Just want to share my experience in case it helps anyone. Been playing for a month and this bug is anything but infrequent. Every time I enter a new village or area, it comes back. It's my biggest problem with this game. Saving and reloading does not fix the problem. What does work is saving, closing the program, and then reloading. The problem will then be "fixed" for the local area. Once an area is "fixed," it remains that way. Since I've explored most of the map, the problem has become less frequent, but it was definitely frustrating spending the last month periodically quitting and reloading. Nevertheless thanks to developers for allowing us to play this game at high resolution and frame rate.
I have exactly the same experience with this glitch. I noted that it does only happen near water.
I finally finished the game but still hope one day the bug will be fixed
Are you getting the invisble lava glitch as well?
yup. but i completed the game in november maybe it's been fixed since then
[удалено]
the invisible lava and water are the same glitch. but like I said, there is no "fix", using 1.24 hopefully makes it less likely to happen.
[удалено]
Did the 1.24 make it really less frequent ? I have the same problem but idk if I should go on 1.24 or 1.18 to play the game without it
That might sound strange but manually setting you max fps to 60 in Nvidia control panel helps. At least it did for me. I tried everything to recreate the bug but i couldn't. I tried it because my fps was spiking up to 65 while loading. Even with vsync. This could be just a coincidence tho
Was this a permanant fix? Have you experienced the probleme again,?
Yes. Never happened to me again. 1) make sure your graphic packs are updated. (Latest version fixes a lot of inconsistent fps problems) 2) update your cemu to 1.26.1 3) limit your fps to 59 in Nvidia CP. 60 didn't work after latest graphic pack update.
Thank for the answer, you cant go back to the old graphiic pack for 60fps? And how many hours did you put in the game so far?
You can find previous versions [here](https://github.com/ActualMandM/cemu_graphic_packs/releases). About 500 hours.
I know this is late but one thing that seemed to have worked for me was capping the FPS at 55 rather than 60. I haven't been able to play much with it yet but so far I haven't run into any physics issues since switching.
How its working so far, did you get the bug again ?
i've played at 55fps for about 40 hours and have only run into the problem one time in the Goron general store but rebooting the game fixed the bug. Compared to my hour or so at 60 fps where I ran into the issue multiple times. It seems to have nearly dissolved the issue for me. Of course there are still certain physics based missions where capping the fps at 30 is needed, but i've only had to do that twice.
For me ReShade seems to have been the primary culprit.
I tried this and I can confirm! I was having this bug too, saw this post and disabled ReShade, and the bug seems to have completely vanished.
Late to the party I was having a huge problem with the above but switching to Triple buffering Vsync as the edit stated solved it for me!
I actually found a better solution: \- set FPS++ higher than your display's refresh rate \- set Vsync to match emulated display \- get Afterburner + RTSS, and use RTSS to limit the framerate That way you don't have to deal with the increased input lag of Triple Buffering, while also getting much smoother frametimes than you would with the FPS++ framelimiter.
Good to know! I’ll give that a shot! I haven’t noticed any input lag but I may be chalking that up to the fact I’m rubbish at the game haha. It was almost unplayable before I put in the first fix. I was getting stuck in invisible water towers every few dozen meters. I would run around with Cryosis permanently so I could try and predict it.