FPS tanks after a re-entering an area during long gameplay, requires restart. #2432
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#2432
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hookshot version
2.1.0
What kind of problem
Low fps or stutter
What happened
After a while of gameplay and entering new areas my fps drops substantially. I first noticed this after leaving kokiri forest and re-entering after obtaining the ocarina. When I restarted the game it started running a lot smoother after that. Similarly upon first entering castle town the fps was horrible, obviously I know shaders need time to compile but I was in there for over 5 minutes and when I restarted it worked just fine. I'm thinking running out of vram was the issue.
Where in the game
Kokiri Forest, Castle Town, Lost woods
How often
Every time
Graphics card and driver version
3070ti 617.42
CPU, RAM and operating system
Ryzen 5 5600x, 32GB 3600mhz cl18, Windows 11
Changes from the defaults
hookshot_options.ini:
quality_preset=0
fullscreen=1
gpu_device=1
frame_generation=0
frame_pacing=1
hdr=0
hdr_paper_white=200
hdr_peak_brightness=1000
frame_rate_cap=0
nvidia_reflex=1
amd_anti-lag_2=0
output_res=2560x1440
dlss=0
dlss_model=0
resolution=1
upscaling=0
sharpness=80
anisotropic_filtering=4
handheld_profile=0
ultrawide=0
ultrawide_menus=1
robust_buffers=0
mesh_shaders=0
volume=100
mute_in_background=0
audio_output=0
fps_counter=1
menu_size=1
game_speed=1
text_speed=0
text_size=0
microphone=4
discord_status=1
controller_in_background=0
mouse_camera=0
disable_camera_centering=0
mouse_sensitivity=100
invert_mouse_vertical=0
invert_camera_x=0
invert_camera_y=0
stick_dead_zone=0
rumble_strength=100
motion_controls=1
motion_sensitivity_x=100
motion_sensitivity_y=100
invert_motion_x=0
invert_motion_y=0
motion_deadzone=1
layout_preset=0
button_prompts=5
menu_shortcut=0
debug_tools=0
descriptor_reuse=1
sampler_cache=0
microphone_device=Microphone (Blue Snowball )
options_version=4
pad_a=1
key_a=69,0
pad_b=0
key_b=16,0
pad_x=3
key_x=32,0
pad_y=2
key_y=1,0
pad_ls=7
key_ls=17,0
pad_rs=8
key_rs=67,0
pad_l=9
key_l=81,0
pad_r=10
key_r=82,0
pad_zl=15
key_zl=90,2
pad_zr=16
key_zr=88,70
pad_plus=6
key_plus=9,13
pad_minus=4
key_minus=77,0
pad_left=13
key_left=49,0
pad_up=11
key_up=50,0
pad_right=14
key_right=51,0
pad_down=12
key_down=52,0
key_move_up=87,0
key_move_down=83,0
key_move_left=65,0
key_move_right=68,0
key_cam_up=38,73
key_cam_down=40,75
key_cam_left=37,74
key_cam_right=39,76
Other software hooked into the game
No, nothing hooked in
hookshot_log.txt
hookshot_log.3.txt
hookshot_log.4.txt
hookshot_log.txt
hookshot_log.1.txt
hookshot_log.2.txt
Screenshots or video
No response
Before you send it
I'm having the same issue. The longer I play, the more the FPS drops, but restarting the game makes it run smoothly again. Feels like VRAM is getting maxed out.
I have this exact same issue; I have to restart the game to fix my FPS.
Same issue here. It also happens while roaming around Hyrule Field.
Same issue here, noticed when I returned to the kokiri forest and instead of having the 50+fps that I normally have it went down to 15-20fps, restarting the game works tho
Same issue here, 6700XT 5600x 32gb RAM. I believe this issue is related to the VRAM usage, I have noticed the game launches utilizing around 7gb of my VRAM, after playing for 15-20 minutes it maxes out at 12gb (the max my card has) and either crashed the driver entirely or game needs restarted to fix. FPS jumps back to 58-60 after reboot.
if you have more than one screen if you mouse click on a non playable monitor the drops stop happening.
Thanks for the report. Reports of the same problem are now collected in #993, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #993 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.