Agreed, this would be extremely useful for a number of projects I'm working on too

Thanks for the info guys and wolf for the suggestions. Still haven't had any related crashes since removing the above software. So could close this on the assumption it was RivaTuner, MSI Afterburner, or some other related software issue

I uninstalled all the old c++ visual redistributables from the windows uninstall list and manually installed the 2015/2017 versions along with uninstalling MSI afterburner and Riva Tuner, also removing a load of old depricated software I found in that list (using windows force uninstaller debugger tool where they wouldn't remove properly). I have since launched ArmA through the stock launcher and A3 Launcher multiple times without a single crash!

Update: I have since had to rebuild my pc due to water damage, I now have a new motherboard z370a, processor i7-8700k, and new ram 16gb trident z 3200mhz cl14. This hasn't mitigated the issue. I also tried unplugging all my joysticks and uninstalling all software but still the same crashes everytime. I did however get a suggestion from another user, running without msi afterburner seems to improve the chances of a successful launch however its still very hit and miss (1/4 or 5 tries). And the crashes happen or don't regardless of making any other changes such as joysticks unplugged or not i.e. With msi disabled - when it does run, it can run with the joysticks connected. Can I ask where in the rpt you found where it says the crash occurs - like detecting joysticks etc. As I've looked through the rpt file, but there's no mention of the cause, it just says the memory address code and all the mods that were loaded?

Thanks for the info, I had wondered this as I'd read about driver issues before, and sometimes unplugging stuff from my pc seemed to get it working once or twice. I'll give this a try. Cheers

Reducing the currently unrealistically good signal to noise/contrast for FLIR would:

1. make it less over powered
2. make it more realistic