@ApexAuroraGames curious what didn't work for you, precache misses or the bundled cache? if it's pcvr: i made a free plugin that flags which hitches are likely pso compiles in packaged builds and where on the map. could help check your fix. windows only for now https://t.co/BjyORVmz58
@warslavegame since you want next fest feedback: i just put out a free unreal plugin that logs every hitch on players' machines, with likely cause, map spot and hardware, and makes one report. i built it, still beta, so tell me if it breaks anything https://t.co/BjyORVn6UG
@warslavegame Makes sense, Next Fest is basically a free hardware lab. One tip: add a tiny perf log to the demo (GPU name, avg + 1% low FPS) so player feedback comes with specs attached. How have you been checking perf so far, mostly your own rigs?
@mabussoftware Nice month of groundwork. One tip for the optimization pass: capture a frame-time graph, not just avg fps, on your slowest machine. 1% lows are what players feel as stutter. What hardware have you been testing on so far?
@Sector13OnSteam Forest scenes are where low-end PCs suffer most: foliage overdraw and shadow cascades usually cost more than poly count. Cutting shadow distance on Low often buys more fps than LOD tweaks. Were the forest perf issues from player reports or your own test PCs?
@StevenMoss_M@gamelawless For the lower-end passes: ray-marched scattering usually scales best rendered at half or quarter res and upsampled, with fewer march steps on Low, so the boss fight keeps its frame budget. Which lower-end configs are you testing on: your own older machines or testers'?