This has been bugging me for some time, especially every time I go fly a Mudhen or an Eagle or a Raptor, etc..... (you get the picture!)
So this is what I have found out so far. The F4Browse/LPBrowse doesn't have the capability to address a new field created by LP in the Falcon4.VCD file which resides in the objects directory under the terrdata folder. Here's a series of pictures to show what I mean:
This is the .VCD file opened up in notepad. This particular view is looking at one of the entries for the F-16C-40:
![Image](http://img224.imageshack.us/img224/3039/f16c40zg3.jpg)
This view is looking at one of the entries for the F-16C-50:
![Image](http://img224.imageshack.us/img224/1223/f16c50qt8.jpg)
And this view is looking at one of the entries for the F-16A-MLU:
![Image](http://img224.imageshack.us/img224/6475/f16mlued2.jpg)
Notice the "ddd2ddd" entry and then the "dd@sF16C50" towards the end of the F-16C-50 record? It's that "dd@sF16C50" which is the new field information inserted into the VCD file which F4Browse/LPBrowse cannot read or write (because it doesn't have that functionality programmed into it). Yes, the old F4Browse/LPBrowse does have what's called a NCTR field to identify the cockpit type but evidently LP rewrote the exe to not read that portion of the .VCD anymore and instead use the new field they created (or at least that is my theory).
To test my theory I hexedited that portion of the VCD file record for the F/A-22A Raptor and put the text "dd@F22" into the F/A-22A record in the missing area. I then created a folder in the
\Lead Pursuit\Battlefield Operations\art\ckptart\Res_1024
folder and I called the folder "F22".
I then edited the "ckpittypes.dat" file residing under the \Lead Pursuit\Battlefield Operations\art\ckptart\Common folder to include the following line: "1024 768 Default F22" using the format provided in that file.
Here's what the .VCD file looked like after my hexedit:
![Image](http://img224.imageshack.us/img224/69/f22addedviahexeditzj8.jpg)
Note that I was doing this for a 1024x768 resolution screen and cockpit.
I then copied the F-16C-40 cockpit into the "F22" folder I had created.
I then built a TE using the F/A-22A Raptor. Now we all know that the F-16C-50/52 cockpit is the default cockpit. So my thought was that if this didn't work then I would see the 50/52 cockpit. But I got the Block 40 cockpit when I entered the 3D world! So it works and it works good!
Note that you cannot edit the .VCD file in notepad! You will screw up your .VCD file and your installation will not work!
Now if someone could just figure out the following files:
bcockpit.dat
bpadlock.dat
Hope this helps!