05 Jun 11, 04:26PM
this is insane - any screen-capture tool does exactly what it says on the tin - it captures the content of the screen; it can't distinguish between worldrender() and hudrender().
Either the tool is seriously broken - reading in-between GL-buffer-swapping - or you have a user expecting results that aren't right.
Like |BC|Wolf says : it depends on whether you're recording 1st-person, spectator/ghost or one of the chasing-cameramodes.
If there really is a frame where you should be seeing the HUD and you're not then I'm mostly interested in the pixels showing in the areas where the HUD should be.
I really don't get the "black ghosts" reference either .. is that some form of trying to describe the LAG-transparency-animation !?!? .. come to think of it .. all this might be pointing at faulty hardware (72.4% probable cause: gfx-card)
Either the tool is seriously broken - reading in-between GL-buffer-swapping - or you have a user expecting results that aren't right.
Like |BC|Wolf says : it depends on whether you're recording 1st-person, spectator/ghost or one of the chasing-cameramodes.
If there really is a frame where you should be seeing the HUD and you're not then I'm mostly interested in the pixels showing in the areas where the HUD should be.
I really don't get the "black ghosts" reference either .. is that some form of trying to describe the LAG-transparency-animation !?!? .. come to think of it .. all this might be pointing at faulty hardware (72.4% probable cause: gfx-card)