For anyone interested, I restarted Chapter 7 and end up at the exact same point again. I found this thread, and apparently 36 other people have run into this as well.
For those that have finished Innocence, will playing Requiem make sense to someone who didn't?
I think in general, the main plot will make sense. You'll probably grasp the narrative. But it does kind of presume that you already know what's going on with the world and characters - there are lots of parallels and references to the events of the first game.
I dunno, it could go either way, because they also don't really spoil the first game much. It is both a direct continuation of the last one, and its own fully discrete storyline. There may be some things about character motivations in different scenes and dialog sequences that you'll miss. There's also some stuff about the Macula, and Amicia and Hugo's relationship that you'll kinda just be rolling with.
That really sucks that they have left that bug in there. Not my favorite section to begin with lol. I got stuck there once or twice just not following directions, missing a direction, or just straight up going wayyy the wrong way and having to go back.
More than once, I thought I was stuck with Melie not doing what she was supposed to, which I believe I solved by running around and messing with whatever I could. I think I even got stuck in that same spot, where Melie just wouldn't come across and up. But I think I just messed with the brazier above her. It was either that or there was some other one I hadn't moved quite right. It's hard to remember. Had to be over a year ago.
Yeah, that puzzle sucks. I won't defend it lmao. It marks a good point in the story but doing it is a drag.
Today I have learned that Plague Tale Requiem really doesn't like me running it at higher frame rates. Better to clock my monitor down to 60hz and let vsync lock it down. Much smoother, and no crashes in 3 chapters. Whereas before, it seemed like any random event (whether it be triggering a climbing animation, alerting/distracting a guard, grabbing an item, entering an area with placed dialog triggers, so on) had the potential to induce an instant crash. Doesn't happen with the frames locked down. Seems like maybe the physics and scripting systems don't always play nice, or it's down to memory management allowing conflicts between these events. *shrugs* Understand, vsync was on before. It's just that my monitor was running at 165hz. The only difference is that I have an effective 60fps cap now.
All well and good for me, tbh. I'm running most settings with ultra on the best quality DLSS setting. At 1080p, my poor FTW3 3060ti is SCREAMING. But all I get now are hard drive hitches when transitioning to a new loading cell and a couple small sections where my view of the rats gives me a steady, micro-grinding stutter.