FSAviator's Simulation Control Interface Tutorial: QUESTION

[katjaneway]

"Many / most 'panels' which claim flight simulation compatibility deliver nothing of the kind for want of a few lines of code. Remember during the enhanced realism harmonisation process depicted here I did not alter one pixel of Kazunori Ito's bitmaps or VC. They were not broken. I just bothered to calculate and write two lines of very simple panel code correctly and I bothered to correct the eyepoint in the original aircraft.cfg so that it now reads;

eyepoint=0.75, 0, 2.85

Bothering to calculate and write SIZE_Y=5700, view_forward_dir=9, and eyepoint= 0.75, 0, 2.85 is the difference between creating two flight simulation control interfaces that allow users to simulate the operation of an MC200, or bewildering them with random and different parallax cues which fail as user simulation control interfaces from either and both viewing modes, because they deliver false and differing flight path vector cues. There are other mathematical combinations of these three scenery projection variables that also project the scenery correctly and deliver the required vertical FoV in the VC, (because real pilots have different body sizes). What is required is that someone bothers to calculate and provide just one of those valid scenery projection solutions in every panel.cfg!"

(Excerpt from the tutorial)

QUESTION: What method (formula, mathematical combination etc.) does one utilize to correctly calculate each of the THREE allowable scenery projection variables, (VIEW_FORWARD_DIR + SIZE_Y + eyepoint) ??

Otherwise, it becomes a tedious "Trial-by-error" method that could lead to a worse simulation interface than before...

[Tom/CalClassic]

Hi,

While I would love to have such a formula myself, the tutorial describes the only way I know to get the proper results. Here is the important thing to remember - at a given value of SIZE_Y= there are only a few values in the eyepoint= line that will work properly. That will determine the VIEW_DIR value. And SIZE_Y= should be set at 6144, unless it's impossible to make that work.

My approach:

1. Set the zoom value according to my text at the end of the tutorial.
2. Set the SIZE_Y= value to 6144.
3. Adjust the eyepoint= line to a location in the VC where your head should be located. You may have to move it further back to get a reasonable view of the instruments. Follow the advice in the tutorial for this. I also set the VIEW_DIR= line to put the horizon approximately in the middle of the outside window view (this helps to determine the correct eyepoint= values). Then compare this to the 2D cockpit, if you fly there. If you fly using the 2D cockpit, make any changes to get that working properly instead.
4. If #3 proves impossible with SIZE_Y=6144, lower it until you can make it work.
5. Once you have the eyepoint values set, fine tune the VIEW_DIR value until the horizon is in the correct location, following the tutorial.

Hope this helps,

[Defender]

Hi,

I'm not sure whether you're trying to create your own panel or just to check out another one but here's a test I use to check view alignment.

Create an AI version of the same aircraft model (don't change anything other than the title=AI.............) and slew yourself right up directly head on nose to nose with it, right close up to the AI aircraft's windshield. When you (pilot) look straight ahead though the centre of the windshield with no hatswitch or keyboard adjustment, are you looking at exactly the same area of the other aircraft's screen? You should be eyeballing the other co-pilot if there is one, dead level with his eyes. The horizon/background shouldn't move when you switch between 2D and VC (flicking numberpad 0 is the easiest way to switch). If that works then everything is probably OK, no further adjustments needed. 

Now I'm not sure I follow this panel.cfg "y" factor either, and whether it is so critical. I do notice that Tom's DC-7C is set at X=8180/Y=5400 whereas Manfred's L1049G uses X=8193/Y=6143 but both aircraft pass the above test perfectly. I can only conclude that the aircraft.cfg eyepoint can be adjusted to suit either setting?

The VIEW_FORWARD_EYE and VIEW_FORWARD_ DIR default settings seem to be much less critical and really a matter of personal preference, particularly for VC fans. You can have the panel.cfg default eyepoint further forward or back, up or down (but don't use it to correct the wrong aircraft.cfg eyepoint!) or looking slightly downwards or even to the right in order to see the essential gauges, without upsetting the outside view.

Bill



   

[katjaneway]

May 11, 2015 13:20:29 GMT -5 Defender said:

You can have the panel.cfg default eyepoint further forward or back, up or down (but don't use it to correct the wrong aircraft.cfg eyepoint!)
Bill



Thanks for your insights.

My interest here is to check out existing panels of freeware user aircraft, and "mend" them according to the broken interfaces tutorial.
Your idea of creating an AI model to check viewpoint alignment is excellent !
I have used a similar tactic when wishing to correct the "Tower View" in some afcad. 
Usually, the Tower View in FS9 does not really reflect the ACTUAL location of the Tower scenery object itself...

But where is the "aircraft.cfg eyepoint" ??
I know about the "panel.cfg eyepoint" parameter. Yet I've never noticed an "eyepoint" parameter in the "aircraft.cfg" file...
Would you care to explain, please?
 

[katjaneway]

May 11, 2015 11:05:45 GMT -5 Tom/CalClassic said:

My approach:
1. ....
2......
3. Adjust the eyepoint= line to a location in the VC where your head should be located.


Nice of you to take time to enlighten me further, Mr. Gibson.
Here are a few queries that might enable me to experiment successfully with broken interfaces of freeware aircraft panels...

When you say "eyepoint=line"......are you referring to the parameter "VIEW_FORWARD_EYE = ..."  ?

In the broken interfaces tutorial, the eyepoint value is printed as:

eyepoint=0.75, 0, 2.85

Is THAT the correct way or should it be "VIEW_FORWARD_EYE = 0.75, 0, 2.85  

Unless I write it EXACTLY, then FS9 would NOT understand the parameter and ignore it (hence my query).

One other query:   eyepoint= A, B, C ......what values do A,B,C represent here ?


If you're wondering, Mr. Gibson....
I am interested in pursuing FS9 (FS2004) as a hobby for the rest of my life,
even though many simmers are migrating from sim to sim (FS9-FSX-P3D-FSX Steam Edition).
Hence, I also reckon on tackling any broken simulation interface and mending it, as in the tutorial.
If other simmers wish to be led astray by the "latest" simulation program that are edging us ever closer to mere online "gaming", that's their affair.
Me...I'm sticking to FS9 for the duration.
Consequently, I wish to learn about every aspect of FS9...including repairing broken panels.

Does that make any sense?

[Tom/CalClassic]

Hi,

Makes perfect sense to me.

The line:

eyepoint=0.75, 0, 2.85

is in the aircraft.cfg file and should remain in that format.

The line:

VIEW_FORWARD_EYE = ...

is in the panel.cfg file and should remain in that format. They normally would NOT have the same number values. In my panels the VIEW_FORWARD_EYE = line is usually all zeros, or missing (same result).

The three numbers represent forward/back, left/right, and up/down (in feet from the reference point of the aircraft). The order of the three numbers in the eyepoint= line is as I list them according to the SDK (i.e. forward/back is listed first), and I assume the same for the VIEW_FORWARD_EYE = line (but FS is definitely not consistent). The reference point is determined by the airplane's builder, but is often at the center of gravity - about 1/3 back along the wing (forward/back), at the centerline (left/right), and at the center of lift (up/down).

Hope this helps,

[katjaneway]

Your explanation is most helpful, Mr. Gibson.

Until you pointed it out, I was searching for the "eyepoint=" parameter in the "panel.cfg" file, but could NOT find it.
Thanks to you, I know why!!

I have been unable to move the eyepoint "BACK", but with your invaluable advice, I think I can tweak the cockpit panel views successfully.
Without guys like you...simmers like me would be stymied and at a loss how to solve some of the more intricate problems and obstacles encountered within FS9.

Always in your debt,
Ronald

Island of Malta

[Tom/CalClassic]

Glad to help.