Re: [Flightgear-devel] YASim update

2001-12-24 Thread Andrew Ross
David Megginson wrote: > It's committed to the CVS, and the DC-3 takes off fine now. For > anyone wanting to try it, the command is > > fgfs --aircraft=dc3-yasim > > I imagine that Wolfram has some 3D models linked from his site. Some > DC-3 sounds would also be nice. I found lots (!)

Re: [Flightgear-devel] YASim update

2001-12-24 Thread David Megginson
Andrew Ross writes: > Indeed. I failed to regression test a last minute change. The DC-3 > has propellers that are both counter rotating and variable speed -- > I'd never tried both together, so of course it didn't work. The right > side propeller governor was seeking in the wrong directio

Re: [Flightgear-devel] YASim update

2001-12-24 Thread Andrew Ross
David Megginson wrote: > Andrew Ross writes: > > Not having toe brakes, I had to map the braking to the "outer" > > ranger of the rudder. > > I'd recommend against hard-coding this mapping in the main config > file. Personally, I map toe brakes to a pair of joystick buttons; we > also have

re: [Flightgear-devel] YASim update

2001-12-24 Thread David Megginson
Andrew Ross writes: > OK, it's a week later than I would have liked, but I've finally > reached a good stopping place with YASim, and have a new release > ready. This is now all in the appropriate places in the CVS repositories; I renamed harrier-set.xml to harrier-yasim-set.xml and dc3-set.x

re: [Flightgear-devel] YASim update

2001-12-24 Thread David Megginson
Andrew Ross writes: > Not having toe brakes, I had to map the braking to the "outer" > ranger of the rudder. I'd recommend against hard-coding this mapping in the main config file. Personally, I map toe brakes to a pair of joystick buttons; we also have default keyboard bindings for each toe

[Flightgear-devel] YASim update

2001-12-24 Thread Andrew Ross
OK, it's a week later than I would have liked, but I've finally reached a good stopping place with YASim, and have a new release ready. Highlights: Engine glitz. The jets now spool slowly over time, rather than responding instantly to throttle input. They also report useful and correct values