David Megginson wrote:
I've been doing a little more work on the 172p interior. When this
plane gets well enough along, I'm going to suggest making it the
default startup plane (in the 3D version):
Wow, very nice!
I agree this could (should) be the default model.
Erik
David Megginson wrote:
Note also that making this the default means switching from the
c172r.xml JSBSim file, which Tony maintains, to the c172p.xml JSBSim
file, which I maintain. It's not really that big a jump, since mine
is plagerized 99.8% from Tony's, and Tony is welcome to take over
Erik Hofman writes:
Note also that making this the default means switching from the
c172r.xml JSBSim file, which Tony maintains, to the c172p.xml JSBSim
file, which I maintain. It's not really that big a jump, since mine
is plagerized 99.8% from Tony's, and Tony is welcome to take
David Megginson [EMAIL PROTECTED] said:
I've been doing a little more work on the 172p interior. When this
plane gets well enough along, I'm going to suggest making it the
default startup plane (in the 3D version):
The other day I was thinking we were coming to this. :-) That would be a
David Megginson writes:
Thanks. I'm testing it in both 16bpp and 32bpp (which is really
24bpp). In 16bpp, you cannot see the propeller disk any more when the
prop is spinning -- it just turns transparent -- but that still looks
OK.
With a 16 bit color buffer you get 4 bits each for R, G, B,
Curtis L. Olson writes:
With a 16 bit color buffer you get 4 bits each for R, G, B, and
Alpha. This turns out to be pretty poor resolution, and for things
like clouds, you can get a lot of banding. For the prop disk which is
mostly solid you shouldn't have to worry about banding.
I've been doing a little more work on the 172p interior. When this
plane gets well enough along, I'm going to suggest making it the
default startup plane (in the 3D version):
http://www.megginson.com/flightsim/c172p-int-01.png
http://www.megginson.com/flightsim/c172p-int-02.png
