Taking screenshots on Windows messes up view angle

[motorsep]

When taking a screenshot on Windows with F12, the view turns left and centers.

Clean install of Doom 3, yesterday's git checkout, Windows XP 32bit.

[dhewg]

For the record, this also happens with SDL2.

[motorsep]

so, where is the issue and is it fixable ? :)

[motorsep]

Shall we close this issue or is there a solution? :)

[andre-d]

I keep forgetting to look into this, I will add it to my list.

[dhewg]

Yeah, don't just close it.
If anyone beat me, great. I just didn't had the motivation to hunt this win32 specific bug down :P

[motorsep]

cool stuff, thanks guys :)

[andre-d]

Oh, windows specific? Ehhhhh, I will have a look at the code but cant test for that.

[motorsep]

yeah, it only happens on Windows (can't test OS X)

[motorsep]

and I will test it for you as soon as you can give me patch ! :)

[motorsep]

No luck with this issue yet ?

[andre-d]

I have a hunch about it, when I hit F12 the cursor becomes visible.

[motorsep]

well, it becomes visible on Linux too, but on Linux view doesn't move like on Windows

[andre-d]

Basically its an SDL bug that unhiding the cursor is causing a movement event (IMO).

[motorsep]

why wouldn't it move the view on Linux ?

[andre-d]

Because SDL has different code on X11 than on windows.

[motorsep]

ahh, gotcha. Well, if you have a patch, I can test it.

[andre-d]

Not exactly, the best solution would be to correct the functionality in SDL imo.

[motorsep]

hmm.. DarkPlaces uses SDL 1.2.14 and has no issues with screenshots. Btw, I am not using dhewm3 builds with SDL2, I am using a build prior to that. So I am not convinced it's SDL's issue.

[andre-d]

Darkplaces likely doesnt show/hide the cursor while a screenshot is taken. If you want to work around the bug you can dig into whatever is hiding the cursor and change that.

[motorsep]

So basically you are saying the issue is not solvable in the engine?

[andre-d]

I am saying it is solvable by a workaround.

[motorsep]

ahh, ok. So, would you be able to make workaround patch by any chance, please? :)

[DanielGibson]

see #40