Hookshot Linux performance diagnosis: NVIDIA GeForce RTX 3060 / v2.1.0 #2535

Closed
opened 2026-11-11 22:34:33 +00:00 by naxacid-ai · 4 comments
naxacid-ai commented 2026-11-11 22:34:33 +00:00 (Migrated from github.com)

Hookshot hardware and performance diagnosis
Generated: 2026-11-11T23:33:52+01:00
Backend: nvidia
GPU: NVIDIA GeForce RTX 3060
GPU driver: 595.112.07
Dedicated VRAM (GiB): 12.0
System RAM (GiB): 31.1
Kernel: 7.3.1-202.nobara.fc44.x86_64
CPU model: 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz
CPU AVX2: yes
Vulkan API: 1.4.329 (4211017)
Vulkan mesh shader extension: yes
/dev/udmabuf: available and accessible
Installed Hookshot version: v2.1.0
Manager-managed Hookshot overrides: none
Profile signature: 1d8521e67f241a70906e8e5ca454fa978f03f9f76bd77ec2888a4857e88af67c
Game process exit status: 0
Log size exceeded the analysis limit; findings and selected evidence use only the latest 16 MiB of the session log.
Community recommendation match: no validated profile is installed for this exact NVIDIA GPU, driver, and Hookshot build. Reports from other GPUs/builds are not applied automatically.
Recent Hookshot FPS samples: 8; average 58.6, minimum 56.3, maximum 60.0.
Latest sampled present interval summaries report 244 frames longer than 22 ms across 8 samples.
Hookshot renderer submit time: latest 7.34 ms/frame; recent maximum 7.34 ms.
Hookshot renderer draw time: latest 0.23 ms/frame; recent maximum 0.23 ms.
Hookshot renderer programs time: latest 0.02 ms/frame; recent maximum 0.02 ms.
Hookshot renderer pipelines time: latest 0.01 ms/frame; recent maximum 0.01 ms.
Hookshot renderer memory sync time: latest 6.63 ms/frame; recent maximum 6.63 ms.
Latest GPU-bound wait sample: 0.00 ms/frame.
Largest logged queue-submit time: 54.5 ms; largest GPU time: 38.5 ms.
Finding: Hookshot logged 0 slow-frame records and 3 slow-upload records.
Vulkan API: 1.4.329
Mesa Vulkan package: package mesa-vulkan-drivers is not installed

Detector coverage
Detector FPS samples: evidence found
Detector Queue/GPU timings: evidence found
Detector Program translation timings: evidence found
Detector Slow frame/upload markers: evidence found
Detector Pipeline build markers: no matching evidence in available data
Detector Shader translation failures: no matching evidence in available data
Detector GPU/driver error markers: no matching evidence in available data
Detector Vulkan details: evidence found
Detector Hookshot log available: evidence found

Selected sanitized log evidence (up to 40 matching lines)
[hos Presentation Thread] vk: a frame's replay time (ms): submit 20.81, present 0.10, draw 10.26, descriptors 3.75, texture lookups 0.11, uploads 0.00, pipelines 0.44, programs 1.91, commands 3.61, dispatch 1.29, memory sync 5.84, queue submit 0.27, slot wait 0.04
[hos Presentation Thread] vk: 49200 presents, 41.1 fps; a frame: 2058 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2321 textures (4292 MB)
[hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.1 ms); 0.0 textures made a frame
[hos Presentation Thread] vk: a frame's replay time (ms): submit 20.76, present 0.10, draw 10.42, descriptors 3.79, texture lookups 0.12, uploads 0.00, pipelines 0.44, programs 1.94, commands 3.69, dispatch 1.28, memory sync 5.69, queue submit 0.28, slot wait 0.03
[hos Presentation Thread] vk: 49320 presents, 41.2 fps; a frame: 2060 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2319 textures (4310 MB)
[hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.0 ms); 0.1 textures made a frame
[hos Presentation Thread] vi: 49389 frames presented (41.1 fps over the last 5.0 s, interval 1)
[hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 1, 22-30 205, 30-40 0, over 40 0
[hos Presentation Thread] vk: a frame's replay time (ms): submit 20.86, present 0.08, draw 10.52, descriptors 3.89, texture lookups 0.12, uploads 0.00, pipelines 0.44, programs 1.96, commands 3.67, dispatch 1.29, memory sync 5.77, queue submit 0.29, slot wait 0.03
[hos Presentation Thread] vk: 49440 presents, 41.0 fps; a frame: 2059 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2321 textures (4292 MB)
[hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 4.8 ms); 0.3 textures made a frame
[hos Presentation Thread] vk: a frame's replay time (ms): submit 20.80, present 0.08, draw 10.43, descriptors 3.83, texture lookups 0.12, uploads 0.00, pipelines 0.44, programs 1.93, commands 3.68, dispatch 1.29, memory sync 5.74, queue submit 0.30, slot wait 0.03
[hos Presentation Thread] vk: 49560 presents, 41.0 fps; a frame: 2061 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2318 textures (4280 MB)
[hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.1 ms); 0.1 textures made a frame
[hos Presentation Thread] vi: 49595 frames presented (41.1 fps over the last 5.0 s, interval 1)
[hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 4, 22-30 202, 30-40 0, over 40 0
[hos Presentation Thread] vk: a frame's replay time (ms): submit 20.83, present 0.08, draw 10.34, descriptors 3.76, texture lookups 0.11, uploads 0.00, pipelines 0.44, programs 1.93, commands 3.65, dispatch 1.28, memory sync 5.74, queue submit 0.27, slot wait 0.03
[hos Presentation Thread] vk: 49680 presents, 41.1 fps; a frame: 2061 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2318 textures (4287 MB)
[hos Presentation Thread] vk: GPU time 16.4 ms a frame (the longest submission 5.1 ms); 0.0 textures made a frame
[hos Presentation Thread] vk: a frame's replay time (ms): submit 20.79, present 0.09, draw 10.51, descriptors 3.85, texture lookups 0.15, uploads 0.00, pipelines 0.44, programs 1.96, commands 3.70, dispatch 1.29, memory sync 5.61, queue submit 0.30, slot wait 0.03
[hos Presentation Thread] vk: 49800 presents, 41.1 fps; a frame: 2065 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2323 textures (4302 MB)
[hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.1 ms); 0.5 textures made a frame
[hos Presentation Thread] vi: 49801 frames presented (41.1 fps over the last 5.0 s, interval 1)
[hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 4, 22-30 202, 30-40 0, over 40 0
[hos Presentation Thread] vk: a frame's replay time (ms): submit 20.70, present 0.11, draw 10.30, descriptors 3.74, texture lookups 0.11, uploads 0.00, pipelines 0.43, programs 1.92, commands 3.63, dispatch 1.27, memory sync 5.65, queue submit 0.28, slot wait 0.03
[hos Presentation Thread] vk: 49920 presents, 41.1 fps; a frame: 2064 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2322 textures (4315 MB)
[hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.0 ms); 0.1 textures made a frame
[hos Presentation Thread] vi: 50003 frames presented (40.4 fps over the last 5.0 s, interval 1)
[hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 6, 22-30 193, 30-40 3, over 40 0
[hos Presentation Thread] vk: a frame's replay time (ms): submit 21.38, present 0.09, draw 10.92, descriptors 3.96, texture lookups 0.17, uploads 0.00, pipelines 0.46, programs 2.04, commands 3.87, dispatch 1.33, memory sync 5.36, queue submit 0.31, slot wait 0.04
[hos Presentation Thread] vk: 50040 presents, 39.9 fps; a frame: 2069 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2325 textures (4312 MB)
[hos Presentation Thread] vk: GPU time 16.6 ms a frame (the longest submission 5.3 ms); 0.3 textures made a frame
[hos Presentation Thread] vk: a frame's replay time (ms): submit 20.61, present 0.09, draw 10.62, descriptors 3.83, texture lookups 0.11, uploads 0.00, pipelines 0.44, programs 1.97, commands 3.76, dispatch 1.26, memory sync 5.62, queue submit 0.26, slot wait 0.03
[hos Presentation Thread] vk: 50160 presents, 41.3 fps; a frame: 2069 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2332 textures (4337 MB)
[hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.0 ms); 0.2 textures made a frame
[hos Presentation Thread] vi: 50210 frames presented (41.3 fps over the last 5.0 s, interval 1)
[hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 7, 22-30 200, 30-40 0, over 40 0
[hos Presentation Thread] vk: a frame's replay time (ms): submit 20.43, present 0.10, draw 10.33, descriptors 3.80, texture lookups 0.23, uploads 0.01, pipelines 0.43, programs 1.94, commands 3.61, dispatch 1.24, memory sync 5.39, queue submit 0.27, slot wait 0.04
[hos Presentation Thread] vk: 50280 presents, 41.7 fps; a frame: 2045 draws (0 skipped), 131 dispatches, 166 passes, 146 barriers, 6 submits, 0.1 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2316 textures (4344 MB)
[hos Presentation Thread] vk: GPU time 16.1 ms a frame (the longest submission 5.1 ms); 1.2 textures made a frame

Community evidence
The Manager records measured hardware/build/settings results locally and distinguishes them from unverified suggestions. A profile should only be promoted when its source, supported build range, matching hardware, before/after measurement, and rollback are documented. This report does not turn a single user suggestion into a global default.
Developer handoff
Related upstream Linux tracker: #1000
Official Hookshot Linux guide: https://git.magicbean.dev/MagicBeanDev/Hookshot/src/branch/main/readme.md#install-and-play
Analysis runs locally. Every session and detector result is stored in the local troubleshooting database. A sanitized summary and selected redacted evidence are sent only after consent.
The report excludes full raw logs, saves, game files, generated code, shader caches, user name, and home paths. Review it before posting; GitHub issues are public.

Hookshot hardware and performance diagnosis Generated: 2026-11-11T23:33:52+01:00 Backend: nvidia GPU: NVIDIA GeForce RTX 3060 GPU driver: 595.112.07 Dedicated VRAM (GiB): 12.0 System RAM (GiB): 31.1 Kernel: 7.3.1-202.nobara.fc44.x86_64 CPU model: 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz CPU AVX2: yes Vulkan API: 1.4.329 (4211017) Vulkan mesh shader extension: yes /dev/udmabuf: available and accessible Installed Hookshot version: v2.1.0 Manager-managed Hookshot overrides: none Profile signature: 1d8521e67f241a70906e8e5ca454fa978f03f9f76bd77ec2888a4857e88af67c Game process exit status: 0 Log size exceeded the analysis limit; findings and selected evidence use only the latest 16 MiB of the session log. Community recommendation match: no validated profile is installed for this exact NVIDIA GPU, driver, and Hookshot build. Reports from other GPUs/builds are not applied automatically. Recent Hookshot FPS samples: 8; average 58.6, minimum 56.3, maximum 60.0. Latest sampled present interval summaries report 244 frames longer than 22 ms across 8 samples. Hookshot renderer submit time: latest 7.34 ms/frame; recent maximum 7.34 ms. Hookshot renderer draw time: latest 0.23 ms/frame; recent maximum 0.23 ms. Hookshot renderer programs time: latest 0.02 ms/frame; recent maximum 0.02 ms. Hookshot renderer pipelines time: latest 0.01 ms/frame; recent maximum 0.01 ms. Hookshot renderer memory sync time: latest 6.63 ms/frame; recent maximum 6.63 ms. Latest GPU-bound wait sample: 0.00 ms/frame. Largest logged queue-submit time: 54.5 ms; largest GPU time: 38.5 ms. Finding: Hookshot logged 0 slow-frame records and 3 slow-upload records. Vulkan API: 1.4.329 Mesa Vulkan package: package mesa-vulkan-drivers is not installed Detector coverage Detector FPS samples: evidence found Detector Queue/GPU timings: evidence found Detector Program translation timings: evidence found Detector Slow frame/upload markers: evidence found Detector Pipeline build markers: no matching evidence in available data Detector Shader translation failures: no matching evidence in available data Detector GPU/driver error markers: no matching evidence in available data Detector Vulkan details: evidence found Detector Hookshot log available: evidence found Selected sanitized log evidence (up to 40 matching lines) [hos Presentation Thread] vk: a frame's replay time (ms): submit 20.81, present 0.10, draw 10.26, descriptors 3.75, texture lookups 0.11, uploads 0.00, pipelines 0.44, programs 1.91, commands 3.61, dispatch 1.29, memory sync 5.84, queue submit 0.27, slot wait 0.04 [hos Presentation Thread] vk: 49200 presents, 41.1 fps; a frame: 2058 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2321 textures (4292 MB) [hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.1 ms); 0.0 textures made a frame [hos Presentation Thread] vk: a frame's replay time (ms): submit 20.76, present 0.10, draw 10.42, descriptors 3.79, texture lookups 0.12, uploads 0.00, pipelines 0.44, programs 1.94, commands 3.69, dispatch 1.28, memory sync 5.69, queue submit 0.28, slot wait 0.03 [hos Presentation Thread] vk: 49320 presents, 41.2 fps; a frame: 2060 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2319 textures (4310 MB) [hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.0 ms); 0.1 textures made a frame [hos Presentation Thread] vi: 49389 frames presented (41.1 fps over the last 5.0 s, interval 1) [hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 1, 22-30 205, 30-40 0, over 40 0 [hos Presentation Thread] vk: a frame's replay time (ms): submit 20.86, present 0.08, draw 10.52, descriptors 3.89, texture lookups 0.12, uploads 0.00, pipelines 0.44, programs 1.96, commands 3.67, dispatch 1.29, memory sync 5.77, queue submit 0.29, slot wait 0.03 [hos Presentation Thread] vk: 49440 presents, 41.0 fps; a frame: 2059 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2321 textures (4292 MB) [hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 4.8 ms); 0.3 textures made a frame [hos Presentation Thread] vk: a frame's replay time (ms): submit 20.80, present 0.08, draw 10.43, descriptors 3.83, texture lookups 0.12, uploads 0.00, pipelines 0.44, programs 1.93, commands 3.68, dispatch 1.29, memory sync 5.74, queue submit 0.30, slot wait 0.03 [hos Presentation Thread] vk: 49560 presents, 41.0 fps; a frame: 2061 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2318 textures (4280 MB) [hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.1 ms); 0.1 textures made a frame [hos Presentation Thread] vi: 49595 frames presented (41.1 fps over the last 5.0 s, interval 1) [hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 4, 22-30 202, 30-40 0, over 40 0 [hos Presentation Thread] vk: a frame's replay time (ms): submit 20.83, present 0.08, draw 10.34, descriptors 3.76, texture lookups 0.11, uploads 0.00, pipelines 0.44, programs 1.93, commands 3.65, dispatch 1.28, memory sync 5.74, queue submit 0.27, slot wait 0.03 [hos Presentation Thread] vk: 49680 presents, 41.1 fps; a frame: 2061 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2318 textures (4287 MB) [hos Presentation Thread] vk: GPU time 16.4 ms a frame (the longest submission 5.1 ms); 0.0 textures made a frame [hos Presentation Thread] vk: a frame's replay time (ms): submit 20.79, present 0.09, draw 10.51, descriptors 3.85, texture lookups 0.15, uploads 0.00, pipelines 0.44, programs 1.96, commands 3.70, dispatch 1.29, memory sync 5.61, queue submit 0.30, slot wait 0.03 [hos Presentation Thread] vk: 49800 presents, 41.1 fps; a frame: 2065 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2323 textures (4302 MB) [hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.1 ms); 0.5 textures made a frame [hos Presentation Thread] vi: 49801 frames presented (41.1 fps over the last 5.0 s, interval 1) [hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 4, 22-30 202, 30-40 0, over 40 0 [hos Presentation Thread] vk: a frame's replay time (ms): submit 20.70, present 0.11, draw 10.30, descriptors 3.74, texture lookups 0.11, uploads 0.00, pipelines 0.43, programs 1.92, commands 3.63, dispatch 1.27, memory sync 5.65, queue submit 0.28, slot wait 0.03 [hos Presentation Thread] vk: 49920 presents, 41.1 fps; a frame: 2064 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2322 textures (4315 MB) [hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.0 ms); 0.1 textures made a frame [hos Presentation Thread] vi: 50003 frames presented (40.4 fps over the last 5.0 s, interval 1) [hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 6, 22-30 193, 30-40 3, over 40 0 [hos Presentation Thread] vk: a frame's replay time (ms): submit 21.38, present 0.09, draw 10.92, descriptors 3.96, texture lookups 0.17, uploads 0.00, pipelines 0.46, programs 2.04, commands 3.87, dispatch 1.33, memory sync 5.36, queue submit 0.31, slot wait 0.04 [hos Presentation Thread] vk: 50040 presents, 39.9 fps; a frame: 2069 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2325 textures (4312 MB) [hos Presentation Thread] vk: GPU time 16.6 ms a frame (the longest submission 5.3 ms); 0.3 textures made a frame [hos Presentation Thread] vk: a frame's replay time (ms): submit 20.61, present 0.09, draw 10.62, descriptors 3.83, texture lookups 0.11, uploads 0.00, pipelines 0.44, programs 1.97, commands 3.76, dispatch 1.26, memory sync 5.62, queue submit 0.26, slot wait 0.03 [hos Presentation Thread] vk: 50160 presents, 41.3 fps; a frame: 2069 draws (0 skipped), 138 dispatches, 167 passes, 146 barriers, 6 submits, 0.0 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2332 textures (4337 MB) [hos Presentation Thread] vk: GPU time 16.3 ms a frame (the longest submission 5.0 ms); 0.2 textures made a frame [hos Presentation Thread] vi: 50210 frames presented (41.3 fps over the last 5.0 s, interval 1) [hos Presentation Thread] vi: present intervals: <15.5 ms 0, 15.5-17.8 0, 17.8-22 7, 22-30 200, 30-40 0, over 40 0 [hos Presentation Thread] vk: a frame's replay time (ms): submit 20.43, present 0.10, draw 10.33, descriptors 3.80, texture lookups 0.23, uploads 0.01, pipelines 0.43, programs 1.94, commands 3.61, dispatch 1.24, memory sync 5.39, queue submit 0.27, slot wait 0.04 [hos Presentation Thread] vk: 50280 presents, 41.7 fps; a frame: 2045 draws (0 skipped), 131 dispatches, 166 passes, 146 barriers, 6 submits, 0.1 uploads (0.0 MB), 83 ub updates (58 overlays), GPU-bound wait 0.0 ms; 10967 pipelines (135951 ms), 0 programs (0 failed), 2316 textures (4344 MB) [hos Presentation Thread] vk: GPU time 16.1 ms a frame (the longest submission 5.1 ms); 1.2 textures made a frame Community evidence The Manager records measured hardware/build/settings results locally and distinguishes them from unverified suggestions. A profile should only be promoted when its source, supported build range, matching hardware, before/after measurement, and rollback are documented. This report does not turn a single user suggestion into a global default. Developer handoff Related upstream Linux tracker: https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/1000 Official Hookshot Linux guide: https://git.magicbean.dev/MagicBeanDev/Hookshot/src/branch/main/readme.md#install-and-play Analysis runs locally. Every session and detector result is stored in the local troubleshooting database. A sanitized summary and selected redacted evidence are sent only after consent. The report excludes full raw logs, saves, game files, generated code, shader caches, user name, and home paths. Review it before posting; GitHub issues are public.
NotRexed commented 2026-11-12 03:07:44 +00:00 (Migrated from github.com)

Thanks for the report. Reports of the same kind are collected in #1000, which lists this one with your details and links back here, so one fix closes them together. Follow #1000 for the fix and add new details there (or here). If this turns out to be separate it will be reopened.

Thanks for the report. Reports of the same kind are collected in #1000, which lists this one with your details and links back here, so one fix closes them together. Follow #1000 for the fix and add new details there (or here). If this turns out to be separate it will be reopened.
Owner

@mooki000 commented on GitHub · 2026-11-12 12:45 UTC · original

Thanks for the detailed summary. One important version boundary: v2.1.0 contains neither #2125 nor #2419, so the later readback regression discussed on #2602 cannot explain this report as written.

The headline and the pasted gameplay excerpt show different frame rates; they may cover different parts of the session. Could you attach the full log and say which area and time were slow, with output/render resolution, upscaler, frame generation, cap/V-Sync and any other heavy work running? That would give the report collected under #1000 a usable comparison without predicting a gain from another GPU's results.

> [@mooki000](https://github.com/mooki000) commented on GitHub · 2026-11-12 12:45 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2535#issuecomment-6823983356) Thanks for the detailed summary. One important version boundary: v2.1.0 contains neither #2125 nor #2419, so the later readback regression discussed on #2602 cannot explain this report as written. The headline and the pasted gameplay excerpt show different frame rates; they may cover different parts of the session. Could you attach the full log and say which area and time were slow, with output/render resolution, upscaler, frame generation, cap/V-Sync and any other heavy work running? That would give the report collected under #1000 a usable comparison without predicting a gain from another GPU's results. <!-- github-sync:c:6823983356 -->
Owner

@naxacid-ai commented on GitHub · 2026-11-12 15:56 UTC · original

Hello! Nice to hear from you! Yes I will do a better report, i tested send it away automated by AI but its not complete log sorry haha. Next time it will be better for you!

But got alot of fucking problems from the beginning to run my game, and many have.. But thats when I tested shitty emulators.. first of all black screen, and thats because of wayland I use on Linux I THINK..

PERFECT FROM THE BEGINNING OF GAME ALL THE TIME. BUT AFTER THE FUCKING SCHENE WHEN THE THREE DIES, THEN FPS DROPS ONLY A LITLE, AND WHEN I CAME TO THE BIG WORLD AFTER THAT, MY FOS DROPS TOO 20-35 FPS.. its a hugh diffrent, it can not be really hard to find out why the fuck it do that. And if you do not or anyone else.. then I will find it out because this makes my so angry and happy to find out at the same time! xD

I fucking love the work you all do, and software are magic. And this will give me more energy to find out what the fuck everyone have problems with the game. When im working on something, then in stuck for ever to its solved. Thats how I working.. No one should have problems to run a baby based games with mid-high end pcs! It must be very logic why it has stutters and fps drop, can not be hard.. why have nobody solved it yet?

Sent from Proton Mail for Android.

-------- Original Message --------
On Thursday, 11/12/26 at 13:46 Mooki @.***> wrote:

mooki000 left a comment (NotRexed/Hookshot#2535)

Thanks for the detailed summary. One important version boundary: v2.1.0 contains neither #2125 nor #2419, so the later readback regression discussed on #2602 cannot explain this report as written.

The headline and the pasted gameplay excerpt show different frame rates; they may cover different parts of the session. Could you attach the full log and say which area and time were slow, with output/render resolution, upscaler, frame generation, cap/V-Sync and any other heavy work running? That would give the report collected under #1000 a usable comparison without predicting a gain from another GPU's results.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you authored the thread.Message ID: @.***>

> [@naxacid-ai](https://github.com/naxacid-ai) commented on GitHub · 2026-11-12 15:56 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2535#issuecomment-6828597834) Hello! Nice to hear from you! Yes I will do a better report, i tested send it away automated by AI but its not complete log sorry haha. Next time it will be better for you! But got alot of fucking problems from the beginning to run my game, and many have.. But thats when I tested shitty emulators.. first of all black screen, and thats because of wayland I use on Linux I THINK.. PERFECT FROM THE BEGINNING OF GAME ALL THE TIME. BUT AFTER THE FUCKING SCHENE WHEN THE THREE DIES, THEN FPS DROPS ONLY A LITLE, AND WHEN I CAME TO THE BIG WORLD AFTER THAT, MY FOS DROPS TOO 20-35 FPS.. its a hugh diffrent, it can not be really hard to find out why the fuck it do that. And if you do not or anyone else.. then I will find it out because this makes my so angry and happy to find out at the same time! xD I fucking love the work you all do, and software are magic. And this will give me more energy to find out what the fuck everyone have problems with the game. When im working on something, then in stuck for ever to its solved. Thats how I working.. No one should have problems to run a baby based games with mid-high end pcs! It must be very logic why it has stutters and fps drop, can not be hard.. why have nobody solved it yet? Sent from [Proton Mail](https://proton.me/mail/home) for Android. -------- Original Message -------- On Thursday, 11/12/26 at 13:46 Mooki ***@***.***> wrote: > mooki000 left a comment [(NotRexed/Hookshot#2535)](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/2535) > > Thanks for the detailed summary. One important version boundary: v2.1.0 contains neither [#2125](https://git.magicbean.dev/MagicBeanDev/Hookshot/pulls/2125) nor [#2419](https://git.magicbean.dev/MagicBeanDev/Hookshot/pulls/2419), so the later readback regression discussed on [#2602](https://git.magicbean.dev/MagicBeanDev/Hookshot/pulls/2602) cannot explain this report as written. > > The headline and the pasted gameplay excerpt show different frame rates; they may cover different parts of the session. Could you attach the full log and say which area and time were slow, with output/render resolution, upscaler, frame generation, cap/V-Sync and any other heavy work running? That would give the report collected under [#1000](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/1000) a usable comparison without predicting a gain from another GPU's results. > > — > Reply to this email directly, [view it on GitHub](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/2535?email_source=notifications&email_token=CUVJTTIRSHLLRZVWUXESP2D5YWWJNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMOBSGM4TQMZTGU3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-6823983356), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/CUVJTTM7TPTQIPIP2BQMLGL5YWWJNAVCNFSNUABGKJSXA33TNF2G64TZHMYTINBWHE3DENJSGA5US43TOVSTWNRTGM4DGOBYHE2DLILWAI). > Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for [iOS](https://github.com/notifications/mobile/ios/CUVJTTJG7QUREOEGSKUHQVT5YWWJNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMOBSGM4TQMZTGU3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG) and [Android](https://github.com/notifications/mobile/android/CUVJTTO7GJUJL5PGBSRX7J35YWWJNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMOBSGM4TQMZTGU3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA). Download it today! > You are receiving this because you authored the thread.Message ID: ***@***.***> <!-- github-sync:c:6828597834 -->
Owner

@naxacid-ai commented on GitHub · 2026-11-12 16:00 UTC · original

I will check it out thanks!!

Sent from Proton Mail for Android.

-------- Original Message --------
On Thursday, 11/12/26 at 04:08 NotRexed @.***> wrote:

NotRexed left a comment (NotRexed/Hookshot#2535)

Thanks for the report. Reports of the same kind are collected in #1000, which lists this one with your details and links back here, so one fix closes them together. Follow #1000 for the fix and add new details there (or here). If this turns out to be separate it will be reopened.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you authored the thread.Message ID: @.***>

> [@naxacid-ai](https://github.com/naxacid-ai) commented on GitHub · 2026-11-12 16:00 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2535#issuecomment-6828700476) I will check it out thanks!! Sent from [Proton Mail](https://proton.me/mail/home) for Android. -------- Original Message -------- On Thursday, 11/12/26 at 04:08 NotRexed ***@***.***> wrote: > NotRexed left a comment [(NotRexed/Hookshot#2535)](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/2535) > > Thanks for the report. Reports of the same kind are collected in [#1000](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/1000), which lists this one with your details and links back here, so one fix closes them together. Follow [#1000](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/1000) for the fix and add new details there (or here). If this turns out to be separate it will be reopened. > > — > Reply to this email directly, [view it on GitHub](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/2535?email_source=notifications&email_token=CUVJTTJX4HFLPZ2YUWF42WT5YUSRLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMOBRGMYTQOBTGE22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-6813188315), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/CUVJTTMYUIN3E547QKQIE7L5YUSRLAVCNFSNUABGKJSXA33TNF2G64TZHMYTINBWHE3DENJSGA5US43TOVSTWNRTGM4DGOBYHE2DLILWAI). > Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for [iOS](https://github.com/notifications/mobile/ios/CUVJTTNH6DKRYWFIXISJTF35YUSRLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMOBRGMYTQOBTGE22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG) and [Android](https://github.com/notifications/mobile/android/CUVJTTLBN6K4WDVI2IGPXVD5YUSRLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMOBRGMYTQOBTGE22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA). Download it today! > You are receiving this because you authored the thread.Message ID: ***@***.***> <!-- github-sync:c:6828700476 -->
Commenting is not possible because the repository is archived.
No milestone
No assignees
2 participants
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Hookshot#2535
No description provided.