Gerhard Wesp wrote:
So, one would really need to define a corresponding network
interface.
This does already exist and is specified in the ``400/500 Series Flight
Sim ICD.'', a proprietary Garmin document. It describes the RS232
interface of their _hardware_ simulator units. I guess Bill Stone
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
Roy Vegard Ovesen wrote:
On Tuesday 23 November 2004 18:05, Melchior FRANZ wrote:
No, I take that back. Mouse properties are (like kbd * js bindings)
fixed at the beginning. min/max can't easily be changed afterwards,
and I don't feel like re-writing the whole input module. Better set
the default
Durk Talsma wrote:
[...]
For this and other reasons, I'm currently leaning toward favoring having a
separate set of low-polygon count models for AI aircraft. The basic idea
would then be to have a directory looking like this:
data/Aircraft/AI/
I like the idea of having such a low-polygon
201 - 204 of 204 matches
Mail list logo
