Hello all. My name is Erik and I have been flying flight sim since the Amiga days. I have very good experience in programing and also with aircraft config files along with the panel. I am able to add the guage to any 2d panel, but the 3d is a bit elusive right now. I have followed the instructions as outlined in the sdk, however, I find that I still cannot get it to show in the vc of my default aircraft (excluding the F/A-18 of course). I have read many post on here and none seems to give me what I am looking for.  :D  So what am I looking for?  :o I would like to see the configs not for just the F/A-18 but for some of the other aircraft that are default freom FSX and at least the Bell 206 that ships with FSX.  ::) With other examples it may be easier to solve the vc issues that I and others may be having.  :)
I understand that there are too many third party aircraft, but at least the default would be nice and we can take it from there. Thanks

Hi and welcome Erik.

If you have Acceleration, then you get the CS_FA-18 (which is really the Acceleration FA-18 anyway) with Weapon for FSX. This has the HUD already done in the VC.

The pane.cfg, in the [Vcockpit01] section, has this for the VC HUD:

gauge03=CSWeapon!hud3d, 526, 515, 550, 550
//gauge03=FA-18!MFD, 578, 579, 440, 440, 4 NOSCANLINES

In the CSweapon.xml, it shows, in the <AircraftInfo> section, this:

   <GaugeInfo>
       <!-- gau section -->
       <AntiAlias2d>1</AntiAlias2d>
       <!-- 2D HUD anti-aliasing. 1-yes, 0-no (1).  0 increases performance.  -->
       <AntiAlias3d>1</AntiAlias3d>
       <!-- VC HUD anti-aliasing. 1-yes, 0-no (1).  0 increases performance.  -->
       <HudFov2d>20.34</HudFov2d>
       <!-- 2d HUD field of view. Degrees -->
       <HudFov3d>17.00</HudFov3d>
       <!-- vc HUD field of view. Degrees -->
       <CollimationData>0.0,14.01,3.358,0.307</CollimationData>
       <!-- see SDK -->
       <EyePtDeltaRatio>0.8</EyePtDeltaRatio>
       <!-- hud acceleration sensetivity factor -->
       <Collimate>1</Collimate>
       <!-- VC HUD collimation. 1-yes, 0-no (1). -->
       <TestFrame>0</TestFrame>
       <!-- HUD test pattern. 1-yes, 0-no (0). -->
   </GaugeInfo>

I'm pretty sure the bold text is everything that deals with the VC HUD.

As far as I know, you can't put the VC HUD in the default Bell 206, because it doesn't have a VC HUD to begin with.

Take a look through this Topic -> USE WITH THIRD-PARTY AIRCRAFT - THE ONLY THREAD for examples of how it is done in other aircraft. I'm not that good at doing the VC HUD. :(

Ah....My Amiga 1000! I remember only too well, those days of Flight Simulator on the Amiga! ;D

Mark

Fair enough and thanks for the response. If I am correct collimation is the illusion that when you move from the center the HUD will dissapear. In other words, to see it you would need line of sight to it. Is this needed for the 3d gauge? If not, that would solve a lot of issues since this is a simulated enviorment and we can really control the hell out of it. The hud is built into the model of the aircraft correct? Or can I actually create one?  :o

Quote:

If I am correct collimation is the illusion that when you move from the center the HUD will dissapear. In other words, to see it you would need line of sight to it.

It depends on how it is done in the VC as to whether it disappears or not, but it follows your eyepoint across the screen. For example, in the FA-18, it disappears as you move left and right. Whereas in the another company F-16, it follows your eyepoint across the screen as you move left or right.


Quote:

Is this needed for the 3d gauge? If not, that would solve a lot of issues since this is a simulated enviorment and we can really control the hell out of it. The hud is built into the model of the aircraft correct? Or can I actually create one?

It is awkward to answer this one. You can't make a VC HUD without having the texture placement in the VC already. Adding the VC HUD into other 3rd party aircraft comes down to them already having the VC HUD so you can replace it with the Weapon for FSX HUD. This is where the collimation data in the CSWeapon.xml comes into play.

From memory, when I was trying to add the Weapon HUD to the AS F-16, it was placed on a transparent texture ahead of the the aircraft itself, so I had to mess with the <CollimationData> in the CSWeapon.xml file. I never got it done because someone else had already done it, but I didn't remember until after I had tried doing it myself! My next attempt will be at the Iris F-14.

Mark

I am starting to place 3D CS HUDs on some fighters. Everyhting else is clear - I think, but there is still one question.

For the CSWeapon 3D HUD gauge from where do I get the data 526, 515, 550, 550 (below) ?

gauge03=CSWeapon!hud3d, 526, 515, 550, 550 //where do I get these numbers?
//gauge03=FA-18!MFD, 578, 579, 440, 440, 4 NOSCANLINES //original gauge - different data - no use above

Is it a try, see and correct or is it allways the same one as FA-18's above or do I get it from somewhare (as the collimation data)?

Yes - I have read the SDK manual (a couple of times) and I know the meaning of that data (co-ordinates and the scale of the hud).

Pekka

As far as I can tell, you add the gauge03=CSWeapon!hud3d, 526, 515, 550, 550 like that, then you use the collimation data in the CSWeapon.xml file to get  the size right in the VC.

I changed the size of the CSWeapon!hud3d, 526, 515, 550, 550, to match the oe in the Iris F-14 gauge00=CSWeapon!hud3d, 13,12,1000,1000 and the CSWeapon 3D HUD was huge. That's why I came to the conclusion that the HUD size in the VC must stay the size that the SDK says it should, and the collimation data is what is used to adjust its size. FOV could come into play once I get the size right. But it isn't easy.

Hope this helps.

Mark

Let's try that.

Thanks!

Pekka

Thanks. Whabout he gaug showig up bakwards? I thouht I saw something about that but have been unable to locate it again. :)

captdylanhunt wrote on May 10^th, 2012 at 11:08am:

Thanks. Whabout he gaug showig up bakwards? I thouht I saw something about that but have been unable to locate it again. :)

I had that happen too. But that was when I was working out where to put it using the <Collimate>0</Collimate> аnd <TestFrame>1</TestFrame>. So it is only the TestFrame you are seeing, not the 3D HUD itself..
Once I turned those off, and started working with the <Collimate>1</Collimate>, <TestFrame>0</TestFrame> and the <CollimationData>xxxxx</CollimationData> itself, the 3D HUD was showing up correctly.

This is how it appears to be to me. I could be wrong. So far it is working for me. But I must admit that, at the moment, the 3D HUD is still too far away and too small in the Iris F-14A and F-14B. So I am still working on it. It isn't easy. :(

Mark

Markoz wrote on May 8^th, 2012 at 11:08am:

As far as I can tell, you add the gauge03=CSWeapon!hud3d, 526, 515, 550, 550 like that, then you use the collimation data in the CSWeapon.xml file to get  the size right in the VC. ... Mark

I tried that with Iris Mig-29 Navy (freeware) VC and those co-ordinates did put the HUD on the glass gauge in the middle right side of the VC (where there normally is some engine information).

Then I started from the Mig-29's original HUD's co-ordiantes and so I got the HUD aproximately on the right place. Quite a tedious job to get it on it's proper place (isn't quite there even yet but I can use that).

Pekka

PHo27 wrote on May 10^th, 2012 at 5:16pm:

Then I started from the Mig-29's original HUD's co-ordiantes and so I got the HUD aproximately on the right place. Quite a tedious job to get it on it's proper place (isn't quite there even yet but I can use that).

Definitely tedious. At least you got further than me. ;)