 |
r_cinematic_legacyRoq 1 is the workaround |
 |
I have played the mission "in one go" and managed to reproduce it. In my case the debriefing played fully to the very end. After the second "blessed day, ..." the camera centered on the artifact. Then it simply stopped there without the mission ending. The engine still worked normally: lighting of the scene was constantly changing because of the torches. Exiting to main menu did not work. However, when I load my savegames and finish mission, the issue does NOT happen: the mission finishes after the camera centers on the artifact and "mission complete" screen is shown. Anyway, there is no cinematic playing during the debriefing: no ROQ/FFmpeg is involved. There are no ROQ files in mission pk4. The whole debriefing is scripted gameplay. And the cvar "helped" only because the issues does not reproduce so easily. |
|
|
I tried to reproduce it with fresh game and did not succeed. |
|
|
Resigning myself: this problem is not related to cinematics/ffmpeg. |
 |
I just played this mission with both endings, and had no problems. We should get some 2.07 testers to run this to see if the problem exists for them. I'll attach my Darkmod.cfg file. |
|
|
Need someone to confirm this problem during 2.07 beta, if it still exists. |
|
|
Still happens for "The Rat's Triumphant". The affected Roq appears to be the mission complete animation? Somehow the timing at that phase is thrown off by FFMPEG decoding vs legacy decoding? |
|
|
Hmm... Maybe this is a little fragile: Objective.h idStr m_CompletionTarget; I seem to recall a number of discussions about idStr not properly retaining data... |
|
|
I won’t be looking at this. Someone else needs to handle it. |
|
|
Unable to reproduce on 2.07 beta package. |
|
|
Closed as a duplicate of 4919 |
|
|
I am not sure that it is duplicate: it does not crash at least. I changed resolution to "Unable to reproduce", since that's how the things actually are (for a rather long time). |
|
|
Added 0005538 as related, the same dangling thread issue (leading to heap corruption) happens during the final sequence. It is quite likely that the hanging is caused by heap corruption too. |
- Anonymous
