Let me ask this Mark - I did do that by hand, but the "Panel" configuations that are dropped in by Loader, are we supposed to replace the Original Panel Configuration with that?  

If that's all that it is, I'll do it immediately.   I didn't think it was that difficult, and now feel kinda stupid if that's all it is.  

I will try in the morning because I just have not had a chance to yet tonight.

I really appreciate your help on this - thank you very much!

John

Thanks Man - I'll be letting you know momentarily - Going to go grab breakfast, coffee, and I'll keep you posted.

Hopefully it ISN'T something as simple as that, if you hear a loud Woohoo or scream from where ever you are, you know it's not or is...it's driving me crazy....

Thanks!

John

Hi John.

Hopefully someone who owns a copy of the AS F-16 can help you with putting it in the 3D VC HUD.

YoYo added a HUD to the 3D VC HUD in his jet (I can't remember what it was off hand:() and maybe he can give you  an idea of what to do.

Mark

I started tweaking FS for my personal use about 14 years ago and I hope to give you some hints tuning 3rd party aircraft and the CSWeapon.xml
...
<HudFov3d>17.00</HudFov3d>
This variable only changes the size of the FOV, not the position.
Looks like the position is linked to the aircrafts CG and can only be modified by changeing the eyepoint´s height (third variable, here 3.358) from the aircraft.cfg
Example:
[Views]
eyepoint = -17.0, 0.0, 3.358
But that means that the pilots seat position might not be correct anymore...

Now back to the weapons and HUD-aim
Example:
<CollimationData>0.0,14.01,3.358,0.307</CollimationData>
                            A  ,B     ,C      ,D
A - is actually equal to the second variable of your aircraft.cfg´s eyepoint
B - same as above, first variable (if you change the - to + or viseversa the HUD is mirrowed )
C -same as above, third variable
D - IS THE MOST IMPORTANT (and difficult to set up the right way). It changes the size of the HUD in VC. The HUD might be way to big at first installation or just as big as a few dots...I had to change this value very often. In some aircraft reducing this value increases the size, others react just the other way.

Next example taken from the gun section:
<Station name="Nose" params="0,9,0,0,-0.039,0,578" />
                                                A,B,C,D,E      ,F,G
A - adjusts weapons position IN METERS! Left negative, Right positive (here 0=straight on the nose)
B - same as above, Aft - negative, Forward - positive
C - Negative - lower, Positive - higher
D -
E - Weapons angle (the variable you all are looking for!!!) Negative - below Horizont, Positive above Horizont - in this example -0.039 means 3.9° above horizont. For the IRIS F-14 it would be 0.033 to match the original HUD´s aimpoint
F - Weapons angle Negative to the left, Positive to the right of the airvrafts longitudinal axis. Not sure but I think 0.1 equals 10°
G - Ammount of Ammo (here 578 bullets)

Whenever you want to adjust any part of the CSWeapon.xml, you must switch to another aircraft in FSX, since the xml is updated when leaving the aircraft. Otherwise, you don´t change anything at all.

I understand that CS is not able to support any 3rd party aircraft on their page but I´d love to see some kind of CONFIG DATABASE for those aircraft in this forum or on the product page.

Sorry for the bad language, but I´m writing this on an aircraft somewhere over europe with a lot of ATC...

Have a bandit day,

Marc

Still tweaking the another company F-16, it’s still not perfect but close enough for others to refine now, I’ve had enough. As this is a manual entry I accept no responsibility for stuff ups by end users.

I’ve only set this into the AS F-16A model:-

In the ‘another company 16A Panel’ Directory take a backup copy of the ‘Panel’ folder then in the original folder rename HUD.CAB to HUD_ORG.CAB or whatever.

Edit the Panel.cfg file to look like this

[Window Titles]
Window00=main
Window01=Engine_state
Window02=Weapon Control Panel
Window03=HUD
Window04=HUD Glass

Add these routines, they are not exactly the same as the default as I found a slight x axis bias during calibration:

[Window02]
Background_color=0,0,0
no_luminous=1
size_mm=1024, 170
position=7
visible=0
window_size=1.000, 0.170
ident=10901
zorder=2
gauge00=CSWeapon_panel!CSWeapon_panel, 0, 0, 1024, 170

[Window03]
Background_color=0,0,0
no_luminous=1
size_mm=400, 400
position=4
child_3d=0
visible=0
window_size=0.585, 0.585
ident=10902
zorder=1
gauge00=CSWeapon!hud2d, 2, 0, 400, 400

[Window04]
file=HUD_Glass.bmp
size_mm=1024, 768
no_luminous=1
position=7
visible=0
window_size=1.0, 1.0
ident=10903
zorder=0
alpha_blend=0.35

Now edit the first two gauge lines in the [Vcockpit01] routine to look like this.

//gauge00=HUD!HUD,            0,46,254,264
gauge00=CSWeapon!hud3d, 5, -20, 254, 400


Place a default copy of ‘csWeapons.xml’ into the ‘another company 16A 9’ Directory

Edit the Collimation Data line to look like this:
<CollimationData>0.0,31.5,-4.5,6.0</CollimationData>

You can copy this csWeapons file to the other two F-16A folders.

I haven’t had a go at the AM or C models yet but should imagine these figures will be close.

Good luck.

Ragtopjohnny wrote on Feb 13^th, 2011 at 3:34pm:

A great idea John. It has be where you post the mods ONLY! This Topic (that we are using right now) can be used for getting help with those mods. The last thing we need is for long discussions on one mod, interfering with other mods posted in there.

Ragtopjohnny wrote on Feb 14^th, 2011 at 1:46pm:

If you mean the 2D HUD? No. And I don't think you can.