Hello BUFF-Pilots  8-)

As it is an known problem that the radar doesn't work with P3D, I made a replacement gauge for this.

After the MOD it should look like this:

http://i.imgur.com/fHNtv35.jpg

Looks cool, right?  8-) - this is the "F35_HUD_VC" from the Default F35A, so you don't need any extra files for this mod.

And here you get it in your B-52 VC:

1. Copy the subfolder from

...\F35A\panel\F-35_HUD_VC

to

...\CS_B52\panel\

It's important that the Folder "F-35_HUD_VC" is in the \panel folder of the B-52.

2. Open the panel.cfg of the B-52 and locate the following entry in the [VCockpit02] Section:

gauge48=Captain_Sim.b520.terrain!main,   0,550,1024,730

This is the problematic Terrain Radar Gauge we want to replace.

Now edit the entry that it should look like this:

gauge48=F-35_HUD_VC!F-35_HUD_VC, 160,460,700,580

3. Save the panel.cfg and get in the B-52!

An Alternative would be to use the "Multiple Moving Map"-Gauge - this is a known Freeware-Gauge that shows different variants of the InGame Map. But I think the F35-Variant is the better solution.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

One important word of saving CS-Planes Scenarios:

If you get the error with the "no title" and "no description", it is not possible to load a saved flight with a CS-Plane. This could also happend to the Default-Flight.

This is because all CS-Planes writes the Gauge-Switch-States to the Savefile. Since the Saveformat has changed since FSX, there is no longer a *.flt File in which the CS-Planes can write the Gauge-States.

P3D only have 2 Savefiles, a *.fxml file and a *.wx file for the weather. The FXML File needs ALWAYS at the end this entry:

</SimBase.Document>

If any entry is BELOW this, the Savegame will be corrupt and produces the know errors. Unfortunately all CS-Planes writes the Gauge-States BELOW this entry  :-/

So you have to manually move all the Gauge-State Entrys ABOVE the </SimBase.Document> Entry, Save it and then the Savegame will load properly.

Here are two examples how it is wrong and right:

WRONG:
       </Flight.Sections>
</SimBase.Document>
[CaptainSim]
PF000=10
PF001=0
PF002=1.580000
PF003=99.422592
PF004=0
PF005=0.0000
...

RIGHT:

       </Flight.Sections>
[CaptainSim]
PF000=10
PF001=0
PF002=1.580000
PF003=99.422592
PF004=0
PF005=0.0000
...
</SimBase.Document>

You can do this with the normal Windows-Editor. You can also add the missing "Title" and "Description" at the beginning:

<Section Name="Main">
            <Property Name="Title" Value="YOUR TITLE" />
            <Property Name="Description" Value="YOUR DESCRIPTION" />

So I hope you like my Mod and have a better flying with CS-Planes in P3D  :)

Hi, possibily I'm the most unfortunate man on this Earth, but I had to uninstall this wonder since, after evr'y flight and closing of P3D v3.4, at its re-opening I was warned by this message - before the opening main page - "Your pc had ran out available memory. Change your etc. etc.". I made several tests, but eventually the culprit was - sigh sigh -, the B-52.

Greetings,

Occurs this with my MOD or without? If without, this is a general problem and you should open an own thread for this.

Generally you have lesser (no) problems/crashes if you disable the factory-builtin radar if you use the B-52 in P3D.

Hi, thanks for the answer.
  I simply don't open the radar at all. Or is it necessary some more action, such as disable/delete something in the panel folder or somwhere else?
  regards,
       Fulvio

To disables the terrain radar, just put a ; (semi colon) in front of the gauge48=Captain_Sim.b520.terrain!main,   0,550,1024,730 line in the [VCockpit02] section like this:

;gauge48=Captain_Sim.b520.terrain!main,   0,550,1024,730

Thanks Mark; done it. But I must confess, I'm frightened to reinstall it since I might be forced to reinstall all P3D in case that fatal message appears again ("Your pc has ran out of memory etc. etc.).  :(

In addition, can I delete the "Captain_Sim.b520.terrain.dll" file just to be completely sure?
   Fulvio

farman wrote on Apr 24^th, 2017 at 8:52am:

Thanks Mark; done it. But I must confess, I'm frightened to reinstall it since I might be forced to reinstall all P3D in case that fatal message appears again ("Your pc has ran out of memory etc. etc.).  :( In addition, can I delete the "Captain_Sim.b520.terrain.dll" file just to be completely sure?    Fulvio

I can't see any harm in deleting the "Captain_Sim.b520.terrain.dll" file.

Note. If the changes have been made with the B-52 uninstalled, then when you reinstall it in P3D, everything will changed back to the way it's supposed to be, and you will have to do it all again.

Hi Mark, well, I definately give up. Yesterday I flew with the new gauge from the F-35 as suggested. Closed P3D and, while reopening, again popped up the fatal message "Your pc has ran out etc. etc..". I know that any single pc has some weird behavior of its own; I experienced this reading about issues, in different forums, that never occurred to me. So, in this case, I accept that for some mysterius reason, some parameter of this beautiful B-52 causes this damage to my sim. I'll wait for an update, even if I fear long awaitings; I really don't know what else to do. Thanks for your help, Mark.

Hey hello,

Occurs this only with the B-52? I can't imagine any other problems except the thing with the radar.

The B-52 is not very VAS-intesive, so I don't have any idea whats the problem at our side  :-?

Have you also tried different locations? So that you can exlude problems with the scenery.

Oh, and one last question: Is this your only CS-Plane?

Hi, having switched to P3D v3.4.22, and having purchased nearly all CS planes, the only one native FSX working 90% properly is the C-130 (some trouble with the exterior lights); the 707 is a FPS eater (of course some compatibility issue between FSX and P3D)  and both the 757 & 767 works very bad, so I left them in the hangar waiting for some update that, I fear, we simmers will get very late. My B-52 issue lies somewhere inside some parameter. While flying it (the first time I installed it), both the scenery and the plane are very smooth, reaching the 30 FPS I chose as frame limit. But as soon as I exit from P3D, I can't fly anymore if not "repairing" it after deleting even all the LM folders in the Users path ("Roaming" and "Local") . I simply copy all the folders inside the P3D root folder to an external one and re-copy them again to P3D; so the waste of time is some hour only, just to reinstall FTX Global, Vector, and a couple of planes and sceneries that need to be reinstalled again. Who knows what or where is or lies the darn trick  that causes this mess.   

Hello,

Sorry for the Tech-Problems you have with CS-planes. What are your System Specs?

I don't have serious problems with my CS-planes with P3D. The most of the (crash)problems I've fixed myself. The 707 runs great with the doppler-fix and uses not more fps than the 767 on my system.

You should also pay attention about this save-bug with cs-planes caused. How to fix this I've wrote at the beginning of this topic

Hi Mustang, right now I can but thank you a thousand times for the suggestion regarding the 707; now it flies without any single issue, after fixing the problem in the VC panel; I'm truly glad. it remains a mistery why the B-52, without any apparent problem during its flight (smooth etc.), causes the P3D unmanageable after its closing and reopening. I NEVER faced a similar problem; my OP is a normal W7 professional, I fly all the planes - even the ones from FSX, twicked if the case -. Absolutely weird.