Re: [Flightgear-devel] README.todo (was: Re: Magnetic Compass)

2004-11-23 Thread Roy Vegard Ovesen
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 (was: Re: Magnetic Compass)

2004-11-23 Thread Boris Koenig
Roy Vegard Ovesen wrote:
On Tuesday 23 November 2004 16:30, Melchior FRANZ wrote:
Should have tried the FA-18A. Completely unusable there. You immediately
end up between the pilot's legs and there's no way to get back up. But can
go further down and watch the scenery through the open front wheel bay.
Resetting fgfs doesn't help either. But once fixed this feature will be
very useful.

Yes, that's what happened in the Airbus too, and it should also happen to any 
large aircraft. You can easily fix this by making the min and max values in 
mice.xml greater. I set them to -10 and 10 meters respectively for both x and 
y axes, I guess that should be enough for most aircraft.
Setting these limits to reasonable values (inside the cockpit) for every 
aircraft would be, as you can imagine, quite a labourous job.
I haven't yet really played with 3D cockpits: what exactly would be
involved in adding such support ? What exactly would it make so
complex ?
Maybe someone over on the users list would be willing to have a go at it? 
> Every so often I see users that ask how to contribute.
Yes, exactly: that's why I suggested yesterday to add another
README file to the base package that contains such todos and ideas,
something like:
README.todo
or
README.contributing
Would probably already be sufficient.
Too many of the ideas and "todos" here, seem to get "lost":
A couple of weeks ago when we were talking about the ATC idea,
David Luff mentioned that numerous of such ideas had already
been discussed on the mailing list: 2 years ago ;-)
While I did manage to find some of the said postings, not everything
seemed to be archived...
So it would definitely be nice to have such a standard file within
the base package: whenever there's something that really needs
attention or is at least worth to be archived, anybody could easily
send a corresponding diff patch to any of the code maintainers.
There were various such things that would really fit well into such
a file: Curt himself mentioned the lack of glass cockpit software
support, the need to revamp the 3D clouds code ...
Such a file could be easily maintained and could even serve as a
template for the "contibute" section on flightgear.org.
-
Boris

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d