niksan29
About
- Username
- niksan29
- Joined
- Visits
- 442
- Last Active
- Roles
- Member
Comments
-
@Boss Hi! two questions: 1) where did you get this information? can you somehow confirm this? 2)why was the wrong altitude 9500ft calculated for the point WI103? --- P.S I wanted to say the addition of 50 feet(in FMS nav p…
-
@kroswynd one of the possible reasonable and convenient options, this is similar to how it is implemented with Fslabs Airbus: programmed a “Rudder Disconnect” keyboard command that allows you to use your rudder pedals like a tiller. By defaul…
-
@FraPre probably about what I was talking about at the very beginning of this topic? Or do you think that VNAV Dash should not calculate the heights of such/similar points? I have not found evidence of this...
-
we turn to this topic I would like to know will this be fixed? 1)vertical path is miscalculated since it starts with the Rwy height but should actually start with the Threshold Crossing Hight(rwy elevation+50ft) 2)missing just for one or m…
-
the joystick yaw axis controls the rudder whether it is possible to add a tiller to it?
-
great job, everyone should have it, thanks!
-
@ckovoor yes, unfortunately this does not work with P5, again something has changed... The XMLTools developer was last online on the forum on September 28, 2019, I don't think that now he can help us ...
-
patch for PRO v1.021 available separately?
-
no earlier than hot fix 2 for P3DV5
-
@vrouleau based on the messages in this topic, it works without problems in P5: http://majesticsoftware.com/forums/discussion/comment/2761/#Comment_2761 @airwolf +1 XML this method is future, now most of the new add-ons are released with s…
-
@ckovoor > I should point out that 2 distinct utilities have been referred to in this thread. I mean too, via XML Gauge: http://majesticsoftware.com/forums/discussion/245/v-speed-calculator-and-setter-xml-gauge Thx!
-
+1 great tool
-
@ha5mvo Now this is the newest version, enjoy! http://majesticsoftware.com/forums/discussion/245/v-speed-calculator-and-setter-xml-gauge#latest
-
> @ckovoor said: > Actually this extract says that Flaps 5 is intended for use on Approach but not on Landing, similarly it says that Flaps 35 is intended for use on Landing but not on Approach and again I was inattentive, thanks!
-
@ckovoor said: Looking at the T/O-Climb table for Vclimb, I realized that Vclimb for Approach-Landing can be obtained from the same table, because it is solely a function of Aircraft Mass Yes, it is, before v1.5 I just opened your tool a…
-
@ckovoor said: I have uploaded a new version 1.4 Very fast, thank you for this wonderful tool!
-
@ckovoor said: but was unable to access any ready Tables to simply compute Vclimb on Approach/Landing. probably because: http://majesticsoftware.com/forums/discussion/509/mjc8-q400-landing-speeds-card-incomplete-data#latest @cko…
-
@ckovoor said: Your observations about the position and colour of the Vref bug are not, of course, related to the V-speed gauge. Why? if possible, just swap these bugs. First Vref(filled\black triangle) and then Vapp. Your utility enters…
-
> @ckovoor said: > I have amended the code to include the new instruction: Thank you! But why 15 knots ?! It should be 20, everywhere it says 20, I don’t know where you got 15 knots from ... FCOM said: https://i.ibb.co/PgM669w/vref.j…
-
> @DCLAN said: > the FMC Fuel Page assumes the PAX weight to bei 11kg this value does not affect anything(PAX advisory value) , since in the end the main thing is that the calculation should be weight without fuel and the amount of fuel o…
-
use just only ZFM from plan PFPX and no problems;)
-
> @ckovoor said: > Thanks for pointing this out. thank you > @ckovoor said: > Now, the Majestic Landing Speeds Card says: > "When flying in icing conditions, Add 20 kts to Vapp, Vref, Vga for Flaps 10, 15 and …
-
noticed a small problem, does not add + 20 to Vref (only flap 35), when icing button pressed it would be great if you fixed it
-
@ckovoor said: But the LUA script (not my creation) does not do that; it works with the higher of the two values. Yes, in the screenshot above, we can just see it @ckovoor said: t is a pity that the original discussion thread wi…
-
@FraPre said: I read that differently in the FCTM. Where exactly did you read this? FCOM. the fact of the matter is that only the approach with V/S is allowed, not RNP landing because with RNP, in FAF high accuracy is needed which ca…
-
For example, in Boeing FCOM, you can not use V/S when RNP app: Use LNAV and VNAV or other pitch mode for initial descent. VNAV is required FAF inbound. And Airbus allows NAV + FPA guidance, but this mode(FPA:Flight Path Angle) is more accurate …
-
@FraPre said: Yes, in this case you descend with an conventional vertical mode, at the Dash VS Yes it is, I just indicated the differences in the charts, with our broken vnav, maybe VS is the best option. And I also wanted to clarify a…
-
@FraPre said: I did not change anything in the routings. understand @FraPre said: In the first flight I flew completely according to the specifications in the charts, ie the STAR and the approach from POGUX. With the 90 ° turn a…
-
@FraPre said: Our Dash would not have been allowed here, yes yes, I noticed it right away @FraPre said: So, the flight and the VNAV flown approach to ENFL went quite well. what you corrected in this route? what was the p…
-
@FraPre said: You can see that in comparison with the 737, that the Dash 50 ft is missing. (red circle) Incidentally, there is no height restriction for WI103 in the PMDG for the navigation data. What you see is a predicted altitude, just like…