![What Is Fraps Has Been Known To Crash D3d11 What Is Fraps Has Been Known To Crash D3d11](http://i.imgur.com/QBXn3oq.png)
Our developer on this feature is currently out of office, so we'll have to wait on his return to get an answer as of exactly why this issue wasn't resolved in SP1, and should have been. In the meantime, I think you deserve a little more information regarding the problem, which I will attempt to explain (it's not my area of expertise). Between EE3 and EE4, we took a new drop of the screen capture SDK from our research group, which included bug fixes and much better performance by working more closely with the GPU. That SDK added a restriction that the resolution captured needs to be divisible by 4. Note that this restriction is also true of most video formats, so an output that has a width or a height that's not divisible by 4 will need to be either padded or cropped to fit in a XESC, WMV or MP4 file. Because some laptops or PC displays are using off resolution like 1050p or 945p, which are not divisible by 4, the 'full screen' screen capture fails because it's not following the assumption explained above.
Whenever I launch PUBG with Fraps it comes up with this message: 'Fraps has been known to crash d3d11 please use Microsoft Expression Encoder instead for capturing' It does not let me record with fraps. Is it something to do with Unreal Engine 4 or just not letting me record. Q: What can FRAPS record? A: FRAPS can record your desktop and games. To record your desktop, make sure to enable 'Aero Desktop' under the GENERAL tab. I personally still use Camtasia, I've had issues with FRAPS recording my desktop. Q: Why won't FRAPS record? A: There are two things that could be the problem.
The fix that was supposed to be implemented in the SP1 timeframe consisted in padding (or cropping) the frame with a few scanlines so the vertical resolution is divisible by 4. We'll look into why this wasn't fixed and will fix it for our next release. Sorry for the inconvenience on the matter. In the meantime, as we suggested before, there are many workarounds to this, including two very resonable ones: 1. Change your resolution to something that's divisible by 4 before starting your screen cap: 1600x900 works fine for example. Instead of fullscreen, capture in windowed mode and size it to 1680x944 (cropping one line in either the top or the bottom).
Finally, please note that Encoder 3 and Encoder 4 can be installed side by side with no interaction between each other if you would like to use EE3 instead of those workarounds. Aknittel: The registry key to clear the previous setting is: HKEY_CURRENT_USER Software Microsoft Expression Encoder 4.0 EEScreen You can delete the directory to clear the cache.
I don't know if that'll make any difference to your problem. A work around is to change the screen resolution to 1600X900 before we collect more information on this. 1680x945 is out there but it's an odd resolution. We do have 1400x1050 (also not dividable by 4) in house and all tests passed for a similar bug in the previous release (v4). Having said that, we would like to keep investigating into this problem and make sure everyone got covered. Can anyone affected please contact me at linyang at microsoft.com and we appreciate your help on this.
Lin Yang: I still get EE4 screen capture on my computer (Windows 7, 1680x945 resolution) after I installed the EE4 SP1. Here is the eventlog entries.
Hope it helps you fix the bug. Application: EEScreen.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. I will contact you this week emailign to. Meanwhile, here is event log dump: Application: EEScreen.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Did you not bother to read the bloody thread?
Specifically, my reply immediately previous to your post? To save you scrolling up, here it is: 'It was not. There was no 'coming release,' as the following month MS announced that it was ceasing development of the Expression products, and that what was already released (version 4) was it. At that point development was frozen. Note that this thread is FIVE YEARS old.' Now, to make he obvious explicit, the fix promised in the 'coming release' did not come.