I've been using ctrquake on o3ds as a testbed for qc/maps cause i don't have an old computer lying around. Just ran into this bug
Poorly optimized maps will trigger the ram warning badge (as expected) but the audio starts to lag behind if the strain is high enough. this appears to only happen in the case of extremely high ram usage. you can reproduce this by turning off mipmapping (d_mipscale 0) since it forces full resolution textures at distance.
A similar issue happens if you close the screen and open it, and if you leave it closed long enough it will just not start back up again. The latency doesn't go away, it seems to require a full restart.
Pretty minor considering it only appears if you're playing seriously unoptimized or huge maps but i've only run into it while testing beta stuff, it might appear in the mission packs though.
I need to rework the sound system to fix the timing issue. I was aware of the delay after closing the lid or pressing the home button, but not the other problem.
I've been using ctrquake on o3ds as a testbed for qc/maps cause i don't have an old computer lying around. Just ran into this bug
Poorly optimized maps will trigger the ram warning badge (as expected) but the audio starts to lag behind if the strain is high enough. this appears to only happen in the case of extremely high ram usage. you can reproduce this by turning off mipmapping (d_mipscale 0) since it forces full resolution textures at distance.
A similar issue happens if you close the screen and open it, and if you leave it closed long enough it will just not start back up again. The latency doesn't go away, it seems to require a full restart.
Pretty minor considering it only appears if you're playing seriously unoptimized or huge maps but i've only run into it while testing beta stuff, it might appear in the mission packs though.