Screenshot Issue
 

I have been using ScreenHunter Free to take screenshots for several years. After moving IL-2 from WIN XP to WIN 8.1, I now have an issue.

When I attempt to take a screenshot from my IL-2 gameplay, the only shots I get are from the IL-2 start-up screen (see screenshot).

This is very strange. I am already in the game flying my plane, but when I take a screenshot, it comes back showing the start-up screen at 10%.

Any ideas of what may be causing this?

Aviar

Use the default screenshot key in IL2 it works perfect with 8.1 and all previous Windows OS's

Under setup misc setting in the gui you can set the screenshots to jpg or tga

A new folder is created called screenshots in the root directory.

Pardon me, but which root directory?

IL2 1946 installation folder.

EG:S:\IL2 1946 4.12\Screenshots

Can I have my thread back, please? Thanks.

I am not looking for a workaround. I know how to take screenshots within IL-2. I prefer to use this particular program.

So, if anyone may have some insight into my dilemma, I would appreciate your feedback.

Aviar

Only Pro supports gaming screen shots according to their compare list.

http://www.wisdom-soft.com/sh/sh_compare.htm

The problem isn't with IL2 1946 or Win 8.1 but a piece of software outside of the native program this forum supports.

If the company advertises compatibility with Win 8.1 take issue with them.

Good Luck.

Edit looking at the associated problems with it I wouldn't touch it with a barge pole.
Special download to remove the mess.

ScreenHunter Free 6.0.203 is corrupt or is not working properly.


http://www.windowsuninstaller.org/wi...ller-info.html

PS:
My guess would be its reading screen shots from the memory buffers hence the delay.

Although I alluded to it, maybe I wasn't quite specific enough. While running IL-2 in WIN XP, I have taken hundreds of in-game screenshots with ScreenHunter.

Now that I have migrated IL-2 to a WIN 8.1 computer, this issue has risen. I'm assuming it has something to do with WIN 8.1.

We'll see if there is some kind of fix. I did report the issue on the ScreenHunter site.


*I just want to make one thing clear, Mr. Alpha. I am not trying to "...take issue..." with anyone or anything on this forum, or WIN 8.1 or even IL-2.

I simply posted a very specific problem that I encountered in hopes of possibly getting some positive feedback. I have been a part of the IL-2 community since day one and this is what we do...try and help eachother.

Aviar

Read the post I made ......... its nothing but being helpful ...... Mr Aviar.

And whats how long you have been around got to do with anything everyone gets the same help there's no preference.

Have a nice day and I hope you get help soon.

:)

Aviar, Alpha tried to help you by tracking down the problem. He obviously doesn't have ScreenHunter, so he made a web search to be able to say something useful. His conclusion ('My guess would be its reading screen shots from the memory buffers hence the delay') seems to be plausible.

You haven't mentioned, but I suppose you updated your copy of ScreenHunter when you changed op system. If ScreenHunter has 8.1 support, and is working correctly with other apps and games, then your problem has something to do with Il2. Otherwise not.

Anyway, migrating from a 32 bit system to a 64 bit system is a big jump; I myself had to say farewell to many of my favourite old utilities, even when an updated version was available. One has to live with it.

Seeing as it is an old Windows XP application it's probably relying on GDI+ and it grabs the screen shot from the buffer there. After XP, everything went over to WDDM for the composting and I'm guessing there is still some sort of fall back and that's what your screen shot program is pulling from the buffer.

It's working from the outside in whereas IL-2's built in screen shot application probably pulls from the render pipeline itself so it's no big problem there even when IL-2 is ages old.

Probably too many guesses in there to make any real sense (apologies Windows software architects) but I can say with some certainty that the way that Windows renders stuff on screen made a big change from XP to Vista and both 7 and 8/8.1 still use the WDDM.

If they have an updated utility then that will probably be aware of the newer environment and should work. Otherwise your options are FRAPS or use the built in one - which, IMHO, works just fine these days.