Repository navigation
Xendroid+: Gears of War 3 options, 21 to 30 fps at the fountain (#99) - #139
Conversation
Software round-toward-zero in vertex shaders pushed Gears of War 3's first playable checkpoint (~2520 draws, 65 passes, 6298 tiles a frame) from its 30 fps cap down to 21.3-22.0 fps (44.6-45.2 ms of GPU a frame with pass timestamps on a POCO F7, Adreno 825, Turnip V38). Enable alu_round_toward_zero=false (-13.6 ms), spirv_vs_relaxed_math=1 (-4.1 ms), spirv_texture_implicit_lod=true (-1.4 ms) and vulkan_texture_load_to_image=true (-0.68 ms interleaved) for 0x4D5308AB: together 28.24 ms of GPU a frame (-37.1%, 29.3-30 fps even with pass timestamps enabled) with matching sky, horizon, cobblestone ground, fountain and HUD. Record the full A/B breakdown and rejected candidates in performance-tests/gears-of-war-3-results.md.
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0f0d9d25c9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| // 1.01 ms), 29.3-30 fps even with pass timestamps on, the same sky, | ||
| // horizon, cobblestone ground and fountain. Memexport barriers by range, | ||
| // structured forward jumps and coarse 4x-as-1x were neutral here. | ||
| {0x4D5308AB, "alu_round_toward_zero", false, |
There was a problem hiding this comment.
Preserve native RTZ on capable Vulkan devices
When the host advertises shaderRoundingModeRTZFloat32, this setting disables native RTZ as well as the software emulation: RoundsTowardZero() checks this cvar before the hardware capability, so affected vertex operations use round-to-nearest instead of Xenos rounding and can produce different geometry. The report only measured the software-emulation cost on a POCO F7; avoid disabling the exact hardware path on capable devices.
Useful? React with 👍 / 👎.
| "no SM3 zero-multiply emulation in vertex shaders"}, | ||
| {0x4D5308AB, "spirv_texture_implicit_lod", true, | ||
| "2D texture fetches with the host's LOD"}, | ||
| {0x4D5308AB, "vulkan_texture_load_to_image", true, |
There was a problem hiding this comment.
Leave texture-load aliases to the device gate
This per-game true bypasses the startup auto-detection, which enables storage aliases only on Turnip Adreno 750+; on older Adreno or other drivers, the texture-cache code will still create eligible textures with storage usage, which the cvar documentation warns can reduce compression and slow sampling. The measurements cover only a POCO F7, so avoid forcing this path on devices outside that tested range.
Useful? React with 👍 / 👎.
Gears of War 3 (
0x4D5308AB) volta ao seu teto de 30 fps no primeiro checkpoint jogável (fonte do prólogo, ~2520 draws/frame), caindo de 44,9 para 28,2 ms/frame de GPU (−37,1%) num POCO F7 (Adreno 825, Turnip V38,e4003ba66).Depois de
2026-10-05, o arredondamento para zero em software nos vertex shaders (#99) tinha somado ~13,6 ms/frame aos passes de cena e sombras projetadas da Unreal Engine 3, derrubando essa cena de 30 para ~21,3 fps. As quatro opções promovidas recuperam os 30 fps sem perda visual ou geométrica nas regiões medidas.0x4D5308AB, janelas de 40 s com timestamps por passe)1280x20481120x2352main(e4003ba66, início / fim da série)alu_round_toward_zero = false(isolada)spirv_vs_relaxed_math = 1(isolada)spirv_texture_implicit_lod = true(isolada)vulkan_texture_load_to_image = true(intercalada)O que muda
game_quirks.cc(0x4D5308AB— Gears of War 3): adicionaalu_round_toward_zero = false,spirv_vs_relaxed_math = 1,spirv_texture_implicit_lod = trueevulkan_texture_load_to_image = truejunto às duas quirks existentes do título (vulkan_depth_4x_as_1xevulkan_samples_as_pixels_simple_ps).performance-tests/gears-of-war-3-results.md: relatório completo da rodada A/B no aparelho, decomposição por passe (VkPassTime/VkMiscTime/VkMemexport), tabela de integridade visual por região (dLuma,MAE,RMSE, energia de borda) e justificativa técnica das opções rejeitadas.Opções testadas e mantidas fora das quirks
spirv_structured_forward_jumps = true:44,90 ms(+0,02 ms, neutra).vulkan_memexport_barriers_by_range = true:+0,54 ms,0,0barreiras elididas (read_after_export = 0,0).vulkan_samples_as_pixels_coarse+vulkan_fragment_shading_rate:−0,05 ms,6298tiles inalterados (as sombras 4x já são cobertas porvulkan_depth_4x_as_1x+vulkan_samples_as_pixels_simple_ps).vulkan_resolve_clear_in_guest_pass = true:46,04 ms(+0,80 ms).render_target_7e3_as_r11g11b10 = true(43,92 ms,−0,96 ms) eocclusion_query = 'fake'(43,15 ms,−1,73 ms): descartadas por serem com perda/inexatas (flare extra no topo do céu comfake) e desnecessárias, pois o conjunto seguro/verificado já alcança o limite de 30 fps (28,24 msmesmo com timestamps por passe ligados).Limites e não testado
alu_round_toward_zero = falseé a primeira quirk a suspeitar.e4003ba66antes do merge do PR [GPU/Vulkan] Guard Vulkan 1.0-1.2 extensions, port Edge rendering fixes, and optimize software RTZ #135.g3-b8-base-end.Gears of War 3 returns to its 30 fps cap in its opening checkpoint on a POCO F7 (Adreno 825), cutting GPU frame time by 37% (44.9 to 28.2 ms).
Gears of War 3 volta ao seu limite de 30 fps no primeiro checkpoint jogável num POCO F7 (Adreno 825), reduzindo o tempo de GPU em 37% (de 44,9 para 28,2 ms por frame).