#Thug 2 pc cutscene fix pro#
You could also try running the game only on the Pro 560, no eGPU, at least long enough to get through a cutscene. So if you have a save from just before one of the cutscenes you know lagged, I'd love to borrow a copy and test that, just for comparsion. On the other hand, I only played up to where Shepard first lands on Eden Prime, and I won't have time to get much farther in-game. I have updated to the latest available AMD drivers.Īny assistance with a workaround or a bug fix would be very much I only had a little time to test tonight, but didn't see any issues with lag in cutscenes. FPS in game is consistently in the triple digits, its just the (seemingly prerecorded) cutscenes that are buggy. I'm playing this on a Macbook Pro 2017 15inch (Bootcamp/Windows) with a 5700XT eGPU. I booted up ME2 hoping the cutscene issue was limited to ME1 but the issue persists and I really don't want to play this entire trilogy with unwatchable cutscenes. I watched some youtube videos of the cutscenes to confirm that my cutscenes actually played in slow motion. I kept spamming spacebar to skip the cutscene in my final attempt but im not sure if that had anything to do with me making it back to the fight on time or not. On my 6th or 7th attempt the cutscene ended just before my shepard's health went to zero and I was able to recover and end the game. But after 6 or 7 attempts I realized that my Shepard was just dying while the cutscene continued to play. Its my first time playing the game so I thought maybe I was doing something wrong. Quite often I would be back in game before the cutscene has the opportunity to play till the end.įor example, in the final fight against Sovereign, the cutscene of the alliance ships attacking the Sovereign ship would play in slow motion, the cutscene would end abruptly, I would be dead, and have the option to load a save. I just finished ME1 and all of the pre recorded cutscenes played in slow motion (4-12 fps) while the audio plays at normal speed (audio and video are not in sync).
0 kommentar(er)
