View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006149 | The Dark Mod | Graphics | public | 04.11.2022 21:15 | 27.11.2022 13:46 |
Reporter | Daft Mugi | Assigned To | stgatilov | ||
Priority | normal | Severity | normal | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Product Version | TDM 2.10 | ||||
Target Version | TDM 2.11 | Fixed in Version | TDM 2.11 | ||
Summary | 0006149: Quick loading graphics glitch | ||||
Description | When quick loading, the screen usually flashes a little brighter and shows something odd for a brief moment before and after the loading screen. I had trouble seeing exactly what it was until I recorded it. Frame by frame there is a regular view, what looks like some sort of view where objects become translucent, the loading screen, a translucent view again, and finally the regular view. Forum Discussion (with screenshots and videos): https://forums.thedarkmod.com/index.php?/topic/21647-bug-quick-loading-graphics-glitch/ | ||||
Steps To Reproduce | Press the quick load key. | ||||
Tags | No tags attached. | ||||
Fixed in svn rev 10182. The greatest problem here was to catch the moment of the issue and find at least some location where things go wrong. In the end, I used apitrace: I captured full history of GL commands, then replayed up to various moment in something like binsearch, until I found where the issue is. I wonder if RenderDoc has the same capability... The problem was inside StartWipe + CompleteWipe, which is called during game load. The first function initializes wipe sequence, the second one renders frames of wipe sequence until it is over. StartWipe was filling backend command buffer, but did not render these commands, so they were continued by the first frame of CompleteWipe. It turns out such "double" frame does not work well: FBO state is wrong when rendering the second part (guiFBO attached for some reason). I simply added R_IssueRenderCommands + R_ToggleSmpFrame, so that StartWipe commands are executed immediately. This fixed the problem. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
04.11.2022 21:15 | Daft Mugi | New Issue | |
04.11.2022 21:17 | Daft Mugi | Product Version | => TDM 2.10 |
04.11.2022 21:31 | Daft Mugi | Description Updated | |
11.11.2022 18:54 | stgatilov | Relationship added | related to 0005314 |
27.11.2022 13:24 | stgatilov | Target Version | => TDM 2.11 |
27.11.2022 13:46 | stgatilov | Note Added: 0015483 | |
27.11.2022 13:46 | stgatilov | Assigned To | => stgatilov |
27.11.2022 13:46 | stgatilov | Status | new => resolved |
27.11.2022 13:46 | stgatilov | Resolution | open => fixed |
27.11.2022 13:46 | stgatilov | Fixed in Version | => TDM 2.11 |