On Tuesday 23 November 2004 19:46, Boris Koenig wrote:
> I think it was Melchior who mentioned that the min/max values are
> specific to certain aircrafts or rather cockpits ?
>
> Taking into consideration that the a3c files are plain text and hence
> readable for simple shell scripting, I wonder now whether suitable
> min/max values can be derived from any *general* data that's preferably
> available in most *.ac files: that way one could use a shell script:
>
> - read in the corresponding data
> - determine suitable min/max values
> - automatically put the binding stuff into *-set.xml
>
> Again: I don't know anything about cockpit design or 3D design in
> general, I would simply *guess* that it should be possible to determine
> the dimensions of a cockpit based on the *.ac file ...
The object names inside the *.ac files could be anything, so I guess it would
be very hard to determine what objects and also what vertices that is
supposed to be the cockpit.
I think that a better approach is to look at the default position of the
viewpoint. This is defined in the *-set.xml file like this:
<!-- position the pilot viewpoint and angle -->
<view>
<internal archive="y">true</internal>
<config>
<x-offset-m archive="y">-0.18</x-offset-m>
<y-offset-m archive="y">0.30</y-offset-m>
<z-offset-m archive="y">0.36</z-offset-m>
<pitch-offset-deg>-12</pitch-offset-deg>
</config>
</view>
Now if we assume that a pilot is able to move his head say 0.5 meters in every
direction, we simply add and subtract 0.5 to the default position, and there
you have your limits.
Of course you could argue that a pilot with his/her but on the seat is not
able to move her/his head very much it the up direction.
>
> Maybe I am making things too simple, though ;-)
Or too hard ;-)
--
Roy Vegard Ovesen
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
