Delayed chunk loading in renders & game crashing during renders - ReplayMod & Bobby incompatibility

[TrixyBlox]

Bug Description

I've been experiencing severely delayed chunk loading in rendered recordings (in 1.19 versions, all chunks would be force loaded from the first rendered frame) and crashing with this exit code error when using ReplayMod/Bobby/Iris/Sodium in 1.20.4 (we have tested Sodium 0.5.4-0.5.8).

Crashing only seems to happen when I attempt to render clips off using shaders with greater than 60 render distance. I'm able to render with higher render distance, only with shaders disabled. For context, on the same system with all the same variables previously, I was able to render at 120 render distance with shaders (no chunk loading at the start of the clip and no crashing).

I've been in contact with the ReplayMod/Bobby developer via their support channel and they told me to raise this with the Sodium team, as it seems to be a fundamental compatibility issue with 1.20 (see screenshot of response I received from the ReplayMod/Bobby developer).

For full context, we have done a lot of testing to eliminate other issues. This happens on all 4 of our PCs, no matter the graphics driver version, Java version, presence of other mods (i.e. we have tested with & without other mods in all possible configurations) etc. No crash reports were generated for the crashes we experienced, but I have included the log.

Reproduction Steps

Reproduction of the bug would entail running ReplayMod, Bobby, Iris & Sodium in 1.20.4. The presence of other mods like C2ME and Nvidium does not make any difference to these issues. Make sure your Bobby mod is activated - in the settings you will need to configure this differently if you are on a server vs singleplayer.

Next, record a clip and make sure you load in plenty of chunks so that they are stored in the Bobby cache and will be rendered through ReplayMod. Then, save the replay recording and open it in the viewer, making sure your render distance is set anywhere between 80-100 and shaders (I was using Complementary Unbound, for instance) are enabled before rendering the clip. The render should start, but it will crash part way through and the segment of the clip that was successfully rendered will start with a chunk loading "wave" moving away from the camera (rather than chunks all being force loaded from the first frame).

Log File

2024-04-26-3.log.gz

Crash Report

No crash report was generated for this issue (as discussed with JellySquid in the Caffeine MC Discord).