Hello.I just would like to know why there's no little variations in engines parameters in the JS4100 like in the previous titles (MD-11 and B744) ??Not a big deal but... just like to know if there's some kind of limitation or you just simply didn't modeled it in the JS41 as well. All the best !

Fritz,What do you mean by "little variations"?

Instead of having L and R engine showing exactly 72.0% RPM... 71.8% and 72.1% could be shown for example...

Fritz,Part of engine management in this airplane is to match the RPMs. In a turboprop, vibration is a constant issue, and matching RPMs is an important part of syncronizing the props...which, in turn, is essential to passenger comfort.If you use a multi-engine throttle quadrant controller, you will absolutely have to manage the engines separately and perform RPM and torque matching.

Instead of having L and R engine showing exactly 72.0% RPM... 71.8% and 72.1% could be shown for example...

I agree with Epikk. Somehow it feels less 'sim-like', when you scan your engine dials and not a single pair is exactly the same value.

I have the complete opposite experience.I'm using a hardware throttle (Saitek), and I am CONSTANTLY fiddling with the power levers to match torque. I almost never see the same values between engines for torque, EGT, or FF. If I do, it's only for a fleeting moment, as TAT is usally changing, or I'm climbing/decending and the values are constantly changing.It's easily one of the most realistic experiences I've had.I think the intentionally biased values found in the MD-11, etc, are very useful for those using a single throttle, and provides a realistic experience for those users. But it's unneccesary (maybe even unwanted?) for those with hardware quadrants.

I have the complete opposite experience.I'm using a hardware throttle (Saitek), and I am CONSTANTLY fiddling with the power levers to match torque. I almost never see the same values between engines for torque, EGT, or FF. If I do, it's only for a fleeting moment, as TAT is usally changing, or I'm climbing/decending and the values are constantly changing.It's easily one of the most realistic experiences I've had.I think the intentionally biased values found in the MD-11, etc, are very useful for those using a single throttle, and provides a realistic experience for those users. But it's unneccesary (maybe even unwanted?) for those with hardware quadrants.

That's the thing. If you are using F2/F3 to control your throttles, you are essentially moving them together in an identical way, and as such, you will get perfectly synched engine readings. If you want the full experience of adjusting your two engines, you need to control each throttle lever independantly, either using a throttle controller, or using your mouse in the VC.

Ok. Thanks guys.