It's no wonder about the negative sentiment from the community.
Among other issues, simply copying and backing up dlls and exes in the root folder - something I've done for years - triggers 4.14.1, and it refuses to start until said backup is removed. Mat Manger "finally" installed but then one day out of the blue 4.14.1 refused to accept any more changes made with the utility. I've never had this problem with Mat Manger with any other IL-2 installs (there are several of them including untouched vanilla installs and more backups), nor over the many years that I've used Mat Manager it since it was first introduced.
Not to mention that with 4.14.1 mods that require object file changes are unusable. That pretty much rules out, among many others, CY6's C2 mod, an essential tool for mission building IMO.
Fed up with its obstinate nature, I finally decided to permanently remove 4.14.1 once and for all - except it wouldn't let me, even after system restarts. Something was running in the folder and kept blocking the deletion. It wasn't il2fb.exe, dgen.exe, and no other residue showed up in the TM's Processes tab. Finally did a search in the Resource Manager's Associated Handles section to see what it was - something I didn't know to do until I learned about it. There was a run32.dll running persistently in the background and I had to end that process before I could delete 4.14.1.
Was really looking forward to using some of the new features of the patch, the new maps, the He-177 (and though it's beautifully modeled I frankly don't care about the MBR), and the remodeled atmosphere - thought the new barometric changes are in a way pointless with aircraft altimeters lacking working Kollsman windows.
Sorry if this seems like a pointless rant but I had to vent - 4.14.1 was becoming more a source of frustration than anything else. This is the first time I've ever backed away from an IL-2 update, going all the way back to the original version of the game.
Author
Topic: Ugh, I've Had It With 4.14.1 (Read 1847 times)
