Recently purchased this product, and with some difficulty installed it. It runs fine but there after P3D V3.4 does not. Apparently this aircraft somehow corrupts the files in C:\Users\Tom B. Headley\AppData\Local\Lockheed Martin\Prepar3Dv3. Unless I delete the two or three files, P3D will no longer run with messages of corrupted files and scenarios. No other aircraft, and I have plenty, performs this wonderful feat. Any suggestions? Oh, I use VR Oculus, but I think it does the same if I don't.

The only problems I have encountered with the CS B-52, in P3Dv3.4.22 are:

1. That when I exit P3Dv3, it modifies my Prepar3d.cfg file - Specifically, it removes the default flight line, so that when I restart P3Dv3, it says that my default flight file is corrupt, and it resets to the flight with the F-22 Raptor ready for takeoff at KVPS, instead of the C-172 @ YMML (in a cold-n-dark setting), that I had set it to. The file is not corrupt, and it loads fine if I select it, but I suspect that this is not the file it saying is corrupt, but I can't figure out which one is, if any. Reselecting the C-172 @ YMML, and setting it as the default flight, P3Dv3 returns to normal, as if nothing was wrong in the first place, and continues that way until the next time I use the CS B-52. :-/

2. I can't use the terrain radar, or P3Dv3 will CTD, which is a pitty, because I love the terrain radar in the B-52. :(

I've uninstalled v3.4 for now, might reinstall it again later. Even better if CS could release an v4.x update (hell, I'd buy the B-52 again in a P3Dv4.x version).

The radar display is kinda annoying yeah. There was this mod that uses the F-35 HUD symbology for that screen, that worked reasonably well, but I can't remember where I found it. I used that, and it was better than staring at a blank screen...
EDIT: It was Mustang1977's mod, further down the B-52 pages: https://www.captainsim.org/forum/csf.pl?num=1487607209

I had the same issues after every B-52 flight, that it modified some files that made v3.4 not start up again afterwards. Don't remember the exact files here and now, but I made a shortcut to the relevant folder, and made a habit of deleting the offending files after every B-52 flight. That worked like a charm.

But once again, CS needs to update the B-52 for v4.x...  :-/

Yess, exactly endl3ss  :). I've explained in detail how to fix the problem with the corrupted files.

It is important to move the "</SimBase.Document>" entry AFTER EACH Save of the flight/exiting PD3, to the end of your *.fxml File.

So for example, if you have save your B-52 Flight under "B-52 USAF" two files will be generated:

B-52 USAF.fxml
B-52 USAF.wx

So you have to edit the "B-52 USAF.fxml" how stated above and all runs fine.