Josh wrote
> Perhaps  we  should track each aircraft's maintainer and more
> importantly, whether they are active or planning to be active with that
> AC soon. I think if we did that it would encourage people to step in and
> adopt planes. Even if a maintainer doesn't have a huge amount of extra
> time, they could still be an advocate and coordinate the work of other
> people on that AC.
>
> As it is now, I think there may be a reluctance to step on people's
> toes, so instead of finishing off an existing plane, people go out and
> start a new one which may or may not get completed. Meanwhile, planes
> that are in need of completion or updating to take advantage of new
> features become hangar queens.
>
> Additionally, this will also highlight planes that no one really cares
> about. That way instead of ditching the incomplete planes, we can
> instead ditch the ones that are incomplete and unwanted, then help bring
> along the ones that people do want to fly.
>
> Josh
>
> PS, I'm still working on the B29 and Canberra, but having trouble
> getting FG to compile and run right. As soon as that happens I can make
> the final sprint to a v1.0 B29.
Thanks for your efforts on these planes. I enjoyed having a circuit or two in 
the B-29 last night. Not the easiest beast to handle but I think it will be 
fun when complete.
 Problems I noticed included:
the nose wheel retracts but the main gear stays down

ground handling was unpredictable - sometimes no matter what I tried it would 
just go round clockwise like only the port engines were running - other times 
it was fine - diff braking helped but only slightly

props don't turn - so I couldn't visually check which engines were running - 
all gauges and throttle positions seemed to suggest I had all 4 OK though.

I havent much experience at this but if there is any help I can offer, please 
say.

Regards
Willie Fleming


_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to