mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-17 02:49:57 -04:00
Make an area's textures at once after a load instead of over the first seconds, which showed the ground and walls black.
The texture pool creates 16 entries a refresh and stops after 6 ms a frame, so that textures streaming in do not make long frames. An area load leaves thousands of slots at once (4,936 loading the test save), and at that rate they came in over the frames after the load screen: the scene's first frames showed a quarter of the picture as black stand-ins, for 22 presented frames on a free machine and for about three seconds with the CPU busy. While a refresh leaves pool_load_backlog slots or more (512; 0 never), the pool is loading: the count limit is off, a frame's refreshes may take pool_load_ms (50), and frame_hold leaves out the presents of frames drawn meanwhile (up to 2 s), so the picture before the load stays until fewer than 64 slots are left. Measured with the flight recorder's thumbnails of every present: the 4,847 textures are made in one frame of 345 ms, 30 frames before the scene fades in, and the black share of the picture goes from the fade straight to its final value. The streaming limits are as before below the backlog. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -625,6 +625,11 @@
|
||||
# keeps its budget): an area load then spreads over several frames with stand-ins instead of holding one frame for
|
||||
# 200-400 ms. 0: no limit.
|
||||
# pool_create_ms = 6
|
||||
# An area load is told from streaming by the number of textures still to make: at this many or more, the two limits
|
||||
# above give way (a frame may take pool_load_ms for them) and the picture before the load stays on screen until the
|
||||
# area's textures are there, instead of showing the ground and the walls black for the first seconds. 0: never.
|
||||
# pool_load_backlog = 512
|
||||
# pool_load_ms = 50
|
||||
# Written storage-buffer ranges up to this size in MiB (1 to 256) go back to game memory as a merge, in 4 MiB pieces:
|
||||
# copied within video memory and only the words that changed written over PCIe. Larger ones are copied back whole at
|
||||
# the end of every submission. Raising it from 4 to 16 took a 5.5 MiB range off the plain copies (about 46 MiB a frame
|
||||
|
||||
Reference in New Issue
Block a user