Hi Phil,

You must have a really long runway on your single-engine test, and must be pushing beyond 100% N1/N2.

I tested the single-engine take-off when I first got the model, and did not have enough runway to get to V1, but if I'd had double length runway I think I would have been able to get to VR, but would not have been able to maintain V2.

How are you determining 8500 fpm climb out?  The 727 is able to climb very steep angles and very quickly IRL... but maybe not that kind of performance.

The reverse thrust does seem a bit too much, I am able to come to a stop in maybe 100 ft with 3x reversers alone... but I've never flown the real thing except as a passenger, so I'm not sure.  I do remember the reverser engaged will throw you forward as a passenger.

The VSI is included in the next SP, per what CS has told me in my tickets.  Flying is not impossible without a VSI.  Take a Cub up for a spin.

I have successfully flown 10+ hops in my 727-100 with the VSI fault.  It's simply this... if it takes 1 minute to climb/descent 1000 ft on the altimeter, you are going at a rate of 1000 fpm.  If it takes 30 seconds, then it's 2000 fpm.  if it takes 15 seconds, a rate of 4000 fpm.  Anything faster than that, and you are exceeding good sense for the aircraft.

As I fly with FSPassengers-X, they will yell at me and I will get bad points if I exceed about 5000 fpm.  Thus far, this only happened on one unrecorded flight, when I was verifying the behavior of the VSI.

So yeah, to answer your question about holding a steady 2000 fpm climbout, set your chronograph and count how many seconds it takes to go 1000 ft.  If it's 30, then you're doing exactly 2000 fpm.

Perhaps you're right that a failure of VSI would warrant an emergency and immediate alternate landing... but then again, when this happens, pilots must use the method I described above to determine their climb/descent rates when doing so.

A good lot of things are being fixed in the next SP, which would be available fairly soon.

And one should qualify your "legally" statement, as there are many types of aircraft which do not include a VSI at all.

Also, I've not seen the issue you report about the ASI...  my ASI agrees within a few knots of what the raw data display shows.  True to life, the ASI is not 100% accurate... this is called realism.

phil, I certainly see your point of view... don't mistake that...

Can you confirm that something is wrong with the VSI's static source?  Obviously the all three altimeters still function, and I'd think at least the standby gauge would use a different static source than the primaries left and right, but I would also assume that the VSIs would be tied to separate static sources as well, so that if one failed due to a static air issue the other would still function.  But I'm no expert on the subject.

If I recall, FSP is more concerned about descent rates than climb rates, but again I don't know if it alters its passengers perceptions based on type of aircraft.  This isn't the place really to talk about FSP's perceptions of my flying though... I just included it as an example to state my point that I am able to get up and get down without crossing it's threshold of what the virtual passengers consider unsafe.

CS *is* addressing the issue, at least it's been confirmed for the VSI, and I know the EPR issue has been reported as well, so I'd assume thrust to be addressed with EPR.  While I share your assessment that the engines are overpowered (based entirely on subjective information on my end) I do have to note that I find it impossible in many cases to maintain a climb speed much in excess of 260 knots unless I pin the throttles to the limit, which would surely cause the engines to detonate in real life.  I tend to never go much over 90% N1, which may or may not be accurate for these engines, but I never push them even to the yellow band, or let the EGT rise to the threshold.

I'll tell you something that I mentioned in another thread... not long ago I paid a premium for a brand new operating system from microsoft... and it was not usable for some days/weeks/etc after purchase because I either had to download updates immediately from microsoft, wait for microsoft to write patches, and/or wait for hardware vendors to get on the ball and release their updates.  

Yes, I was upset about that, and yes I'm a little upset that I paid good money for a plane that should have had these issues resolved before release.   But no software is perfect on release day, and if it is, that's an extreme rarity.  Our SP to fix the issues which have been reported will be available soon, and CS are working on it.

I'm not associated with CS in any way other than as a customer, and I use the same channels to communicate with them as we all do, and they've assured me the SP will be available soon, and it addresses quite a few (if not all) of the issues that everyone has reported to them.

So, until that time, I'm choosing not to be mad about it, and enjoying the plane as it is today.  It's still far better and more enjoyable to fly than the old FS9 converted to FSX freeware 727's I've used for years.  

As have I, friend.  But also being from an IT/Development background myself, I also understand that sometime the biggest irritating factors are indeed the easiest to fix... but they must wait for a greater release because of testing or other issues which may or may not be a factor with that smaller issue.  So I really think this is a good thing, to have one big patch than having to install 1000 small patches, which if installed in the wrong order (or if one is skipped) could cause a major nightmare for the end user (and for CS support!)

For the record, the VSI on the 727 doesn't read direct from the static ports, like it would in a light aircraft.  It does read from the static system, but according to the systems manual also:

Quote:


I think the issue is not necessarily in the static reading, but in the code that emulates those accelerometers.  My suspicion is that the code is accidentally working against the static air, and not with it, but I don't have the code to compare, and really don't care to violate the "reverse engineering" clause of every license agreement in existence to find out.

It will come.  They're under serious pressure from users like us to make it happen.  Just sit tight and make believe that you have less thrust than you do and that your VSI works.  The rest of the plane is still quite accurate in most regards.