View Issue Details

IDProjectCategoryView StatusLast Update
0004843The Dark ModCodingpublic29.01.2021 04:23
ReporterAluminumHaste Assigned Tonbohr1more  
Status resolvedResolutionfixed 
PlatformX64OSWindows 7OS VersionUltimate
Product VersionSVN 
Target VersionTDM 2.07Fixed in VersionTDM 2.07 
Summary0004843: Game isn't frozen during screenshot command with jitter
DescriptionUsing the jitter built into the screenshot command:

screenshot 1920 1080 32

Doesn't cause the game to freeze during all the jittering, so you get blurry parts of the image.
For example, look at the beastie in this screenshot, he's moved during the 32 jitter steps and is now blurred.
Steps To ReproduceBind the command "screenshot 1920 1080 32" to a key, and press it while in game.
Set your res to your monitor res.
TagsNo tags attached.


related to 0005494 resolvednbohr1more g_stopTime causes portal_sky to turn black 




22.06.2018 04:00

developer   ~0010550

This should probably be fixed but as a workaround you could set a hot-key to "g_stopTime 1"


24.06.2018 13:43

developer   ~0010578

using this works:

bind F12 "g_stoptime 1;screenshot;g_stoptime 0"



02.07.2018 05:58

developer   ~0010637

I tried to trace down g_stopTime in the code to find out how it works
and I seem to have hit one of those strange paradoxes where it is referencing itself in a pause routine?

Anyway, I know a hacky way to do this.
1) create a temp bool variable
2) determine if g_stopTime is already active
3) assign a value to the temp variable
4) g_stopTime.SetBool(true)
5) capture sceenshot
6) use the value from step 3 to determine whether to start time again

I already have an ugly hack in RenderSystem_Init for screenshots with FBO so I'm reluctant to touch this until the "FBO management cleanup" project here is completed:


10.07.2018 04:26

developer   ~0010665

Old FBO screenshot lightgem fix (hack) removed in rev 7559
New g_stopTime jitter fix (hack) in rev 7560

I suspect we could fix the case where you specify a different resolution than your current screen with r_fboResolution but that is outside the scope of this fix.

Issue History

Date Modified Username Field Change
22.06.2018 03:52 AluminumHaste New Issue
22.06.2018 03:52 AluminumHaste Description Updated
22.06.2018 04:00 nbohr1more Note Added: 0010550
24.06.2018 13:43 AluminumHaste Note Added: 0010578
02.07.2018 05:58 nbohr1more Note Added: 0010637
10.07.2018 04:26 nbohr1more Note Added: 0010665
10.07.2018 04:26 nbohr1more Assigned To => nbohr1more
10.07.2018 04:26 nbohr1more Status new => assigned
10.07.2018 04:26 nbohr1more Fixed in Version => TDM 2.07
10.07.2018 04:26 nbohr1more Status assigned => resolved
10.07.2018 04:26 nbohr1more Resolution open => fixed
29.01.2021 04:23 nbohr1more Relationship added related to 0005494