Version 2.5:
F5 - short key to emulate FF screenshot when you press it. It will create provided .bmp file to show you what FF will get if it decide to screenshot you at that moment. This is because many people spam with questions about screenshot features, so now dont ask, just press F5 and will emulate FF ss and see provided bmp and now you should know with setting you use what picture FF will get if decide to snap you right now.
Version 2.6:
small interface improvement Auto Clean SS Timer is in seconds, not milliseconds
yujiaqi's fix for ESP disappear when you get in vehicle
Version 2.7:
New feature - You can remap all keys. Open the file with saved settings (if you have not created it yet, get into game press F12 and file will generate) scroll to section called KEYS BINDINGS and change the key number value you like. What number to put? Open Virtual-Key Codes.htm file (located into project dir) or google for "MSDN Virtual-Key Codes". From the table select key name you want, take the value next to it, convert it from hex to decimal, and put that number in imgui.ini
bugfix in F5 feature to work on dual monitors PC
Version 2.7.1:
small bugfix in F5 ss benchmark, was unstable sometimes.
Version 2.8:
F6 - shortkey to emulate FF screenshot through CopyResource, whilst F5 (ver.2.5) feature emulate same through BitBlt. F6 and F5 do the same thing but behind is different functions. F5 and F6 are only for benchmark purposes, if you are curious what FF will get if decide to screenshot you now, press F5 or F6 and look for .bmp file called "provided", that is the ss which FF will receive with current settings you are using at the moment. And the names of the others created .bmp ss are also same described in F5 feature (ver.2.5) blocked, spoofed, taken. Keep in mind, if you have not selected one of both options for clean ss, then the hack will just block FF to take ss and will generate blocked .bmp in which you can see what screenshot FF tried to pull out from your computer.
BF1 use few functions to steal screenshots from your PC, all they are spoofed/blocked. That's why the names of the generated ss .bmp files are little different containing name of functions that FF used to steal screenshots. And same is valid for ss notifications you see on the screen, they will tell you and name of the function that FF attempt.
For devs who look in my code: in this update most interesting parts of my code are catching the ss from DirectX texture, extracting a bitmap into HBITMAP and convert to a .bmp and save into a file. The other interesting part is C++11 lock_guard mutex and multi-thread synchronization, necessary when call DirectX device functions from different threads, need thread synchronization, otherwise will cause beautiful crash. Hope you find something useful.
Version 2.9:
Aim at Vehicles - you can aim tanks, planes, trains etc. Optional feature. Choose spot for aim: Top, Center, Bottom
Aim at Horses - separate from vehicles, you can aim only horses. Optional feature. Choose spot for aim: Top, Center, Bottom
Aim with Weapon 2,5,6,7 - optional, you can select which additional weapon to be engaged with auto aim. This feature make sense when you enable "Aim at Vehicles" and aim at tanks with AT Rocket Gun for example. Which weapon what number is? Look at the menu bottom, there is an indicator showing the weapon number.
fixed bug ESP disappear on enemy close than 1m
Version 2.9.3:
Aim prediction works on vehicles, so you can aim fast moving planes, horses, motorcycles etc. And some essential bugfixes
version 3.0:
bigfix in ss, some people experience such bug it makes black box in the ss. This must fix the ss glitch, so please test: spawn in the game, press F5, wait 30 sec, press F6 and look the bmp files. Also when play keep eye on bmp that ff generate.
version 3.1: fixed glitch in screenshot features which some people experienced on their PC. Dont use earlier versions if you have that bug. Sorry for the late fix, I was not able to reproduce that bug on my PC, so I had to beg unknown people to help me testing, so all this took many days time frame. Thanks to all people from that forum who helped me to make v3.1
version 3.1.1:fixed small memory leak I forgot, better stability
