Re: [Flightgear-devel] README.todo
Roy Vegard Ovesen wrote:
On Tuesday 23 November 2004 17:31, Boris Koenig wrote:
I haven't yet really played with 3D cockpits: what exactly would be
involved in adding such support ?
The support is already there: it is possible to set the view position at
runtime through the /sim/current-view/{x,y,z}-offset-m properties.
You can apply the patch to $FG_ROOT/mice.xml attached to this posting.
http://baron.flightgear.org/pipermail/flightgear-devel/2004-November/032316.html
What exactly would it make so
complex ?
Actually it is not complex at all, assuming that it is possible to configure
the mouse bindings individually for every aircraft. Then it would simply be a
matter of
* Run FlightGear
* Change the /sim/current-view/{x,y,z}-offset-m properties to find reasonable
values for the limits that the view should be allowed to move.
* Add a mouse binding to the aircraft *-set.xml (I assume) file with the found
min and max values.
* Repeat for every aircraft model. ;-)
Ach. That would screw with any changes that people made to customize their own
mice.xml files. Might it be better to invent some properties that are set in
the *-set.xml file that could be used by bindings in the mice.xml file? That
way, every plane could define these dimensions independently without making
changes to config files that really have nothing to do with that specific aircraft.
Josh
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] README.todo (was: Re: Magnetic Compass)
On Tuesday 23 November 2004 17:31, Boris Koenig wrote:
I haven't yet really played with 3D cockpits: what exactly would be
involved in adding such support ?
The support is already there: it is possible to set the view position at
runtime through the /sim/current-view/{x,y,z}-offset-m properties.
You can apply the patch to $FG_ROOT/mice.xml attached to this posting.
http://baron.flightgear.org/pipermail/flightgear-devel/2004-November/032316.html
What exactly would it make so
complex ?
Actually it is not complex at all, assuming that it is possible to configure
the mouse bindings individually for every aircraft. Then it would simply be a
matter of
* Run FlightGear
* Change the /sim/current-view/{x,y,z}-offset-m properties to find reasonable
values for the limits that the view should be allowed to move.
* Add a mouse binding to the aircraft *-set.xml (I assume) file with the found
min and max values.
* Repeat for every aircraft model. ;-)
--
Roy Vegard Ovesen
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] README.todo
Roy Vegard Ovesen wrote:
On Tuesday 23 November 2004 17:31, Boris Koenig wrote:
I haven't yet really played with 3D cockpits: what exactly would be
involved in adding such support ?
The support is already there: it is possible to set the view position at
runtime through the /sim/current-view/{x,y,z}-offset-m properties.
You can apply the patch to $FG_ROOT/mice.xml attached to this posting.
http://baron.flightgear.org/pipermail/flightgear-devel/2004-November/032316.html
Ya, thanks - I know, I did follow that discussion, I was merely
wondering where exactly the complexity comes in ;-)
So, whether it would require any significant code changes or whether
it would come down to time-consuming manual trial error means ;-)
What exactly would it make so
complex ?
Actually it is not complex at all, assuming that it is possible to configure
the mouse bindings individually for every aircraft. Then it would simply be a
matter of
* Run FlightGear
* Change the /sim/current-view/{x,y,z}-offset-m properties to find reasonable
values for the limits that the view should be allowed to move.
* Add a mouse binding to the aircraft *-set.xml (I assume) file with the found
min and max values.
* Repeat for every aircraft model. ;-)
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 ...
Maybe I am making things too simple, though ;-)
--
Boris
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] README.todo
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=ytrue/internal config x-offset-m archive=y-0.18/x-offset-m y-offset-m archive=y0.30/y-offset-m z-offset-m archive=y0.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
