No disrespect taken from your comments.I was going to try and put a 4 cylinder in it anyway but i was running short of polygons as the limit is only 20000.I have now updated the model to have a 4 cylinder da-200 and i am posting it now.I have tried to fix the flashing aswell but as i got no flashing in the first place i am relying on others to let me know if its fixed or not.rocketodd said:Mark,
Please understand that I mean no disrespect when I comment on your Python.
Or,
Hi Oxdeadbeef,Glad you like the model and is there any chance you could tweak the flight model as you seem to know what needs fixing in order to get it to fly properly.If you could it would be great as i am no good at physics modelling and have done the best i can.0xdeadbeef said:Is it just me or is the rudder quite a bit too effective (well, the elevator too)?
Indeed one of the latest fixes after the original 3.5 release made the control surfaces much more effective. Probably partly because the rework of the stall behaviour. Maybe also because the fuselage drag was changed.
Indeed I think a couple planes now turn too easily, but on the QQ Pitts Python (and the scale Python as well) this is especially pronounced.
I also feel the control surfaces stall too late and too little. Also the drag of the stalled surfaces seems to be too low.
This might be the main reason why the rudder efficiency is so visible on the Pitts. On other planes, the rudder is also very effective, but the stall of the control surface and the drag of the stalled surface stops the quick turning and slows the plane down. This is not the case on the Pitts however.
Anyway, the 3D model is great as all of Inky's. Though I personally like the scale version better
BTW: not texture flashing for me
opjose said:Wonderful plane...
Horrid texture flashing on my machine at any distance...
Inky00 this is the same problem as with the original Pitts Python you posted.
Is there any way to fix it?
There are several of the bigairplanes.com versions of the Python out there IRL, but if you want flight characteristics of the QQ, you'll have to ask Mr. Somenzini himself, as I understand the QQ Python is a one-of-a-kind aircraft at the moment.rjmanzuk said:I'd appreciate an evaluation by someone that owns a RL version of this bird to let us know whether 0xdeadbeef's edition, or inky00's is the more realistic performer of the two? If it's Ox's, then I'm still more a fan of the Ultimate for feel and performance, notwithstanding the Python's definite curb appeal, with or without QQ's CS.
Thx,
skiman21632 said:I Just downloaded the updated QQ Pitts Python, and Inky00 i no longer am having the flashing texture issues on this particular model seems to be fixed for me. Thank You Skiman <><
I will look into the flashing on the cowl and maybe update the EA again if i can fix it.opjose said:Still does it around the cowl for me...
However the flashing in the body is now gone.
I have updated the 3d model to hopefully stop all texture flashing in the cowl.Please could you download and let me know if this version is fixed so i can upload it to the swap pages.opjose said:Still does it around the cowl for me...
However the flashing in the body is now gone.
Hmmmm, will this further increase the performance differences between your EA and Oxdeadbeef's variant? Or, will this only impact imagery? Yours truly never experienced the texture flashing (whew! too old to recall how to deal with flashers ). So what should us non-flashers expect in our imagery now that you've made these changes? the only acceptable answer, of course, is "... nothing".inky00 said:I have updated the 3d model to hopefully stop all texture flashing in the cowl.Please could you download and let me know if this version is fixed so i can upload it to the swap pages.
The answer is nothing.Only people experiencing texture flashing should see any difference from the one on the swap pages.rjmanzuk said:Hmmmm, will this further increase the performance differences between your EA and Oxdeadbeef's variant? Or, will this only impact imagery? Yours truly never experienced the texture flashing (whew! too old to recall how to deal with flashers ). So what should us non-flashers expect in our imagery now that you've made these changes? the only acceptable answer, of course, is "... nothing".